I’m stuck at “Connecting” after character selection whenever I change any server, stays the same. I can not completely connect to the server. Please help
Please confirm that How to check the basic functionality works fine on your environment. It’s a first thing you should test.
it gives me this error http://i.imgur.com/gLBO56W.png
what I found is TAP Win32 is Indentifying and stuck at this phase. in the past, it was giving me a window of confirmation that says there’s a new network device being installed but now it doesnt. and still giving me error 045. I did the -I thingy, I disabled IPV6 as shown in the picture but still… http://i.imgur.com/Tc54ln7.png I also added mudrun.exe into allowed role in the firewall to make sure but still.
and this is what it shows on log: [2.633445] [INFO] TAP-Win32 Driver TcpNoDelay diabled
[2.633445] [INFO] TAP-Win32 Driver TcpAckFrequency 1
[2.633445] [INFO] TAP-Win32 Driver TCPNoDelay 1
[2.645479] [INFO] Fetching new static node SID 437…
[3.741650] [INFO] re267: Associating with ip 45.77.64.185 port 10008
[3.742654] [INFO] re267: Connected to 45.77.64.185:10008 (UDP)
[3.744657] [INFO] Setting the default gateway as 10.229.144.1 (437 (null))
[3.746164] [INFO] Ready
[3.845934] [INFO] Listening the management console at 127.0.0.1:58211
[6.754646] [INFO] Waiting until the client’s ready to handle the routing path list.
[9.755065] [INFO] Waiting until the client’s ready to handle the routing path list.
[12.756085] [INFO] Waiting until the client’s ready to handle the routing path list.
[15.757123] [INFO] Waiting until the client’s ready to handle the routing path list.
[18.758026] [INFO] Waiting until the client’s ready to handle the routing path list.
[21.758619] [INFO] Waiting until the client’s ready to handle the routing path list.
[24.759544] [INFO] Waiting until the client’s ready to handle the routing path list.
[27.760291] [INFO] Waiting until the client’s ready to handle the routing path list.
[30.761121] [INFO] Waiting until the client’s ready to handle the routing path list.
[33.762011] [INFO] Waiting until the client’s ready to handle the routing path list.
[36.762683] [WARN] MUDEC_00044: The client isn’t ready yet
[36.762683] [INFO] Waiting until the client’s ready to handle the routing path list.
[39.764155] [INFO] Waiting until the client’s ready to handle the routing path list.
[42.764844] [INFO] Waiting until the client’s ready to handle the routing path list.
[45.766441] [INFO] Waiting until the client’s ready to handle the routing path list.
[48.767469] [INFO] Waiting until the client’s ready to handle the routing path list.
[51.768191] [INFO] Waiting until the client’s ready to handle the routing path list.
[54.769217] [INFO] Waiting until the client’s ready to handle the routing path list.
[57.770765] [INFO] Waiting until the client’s ready to handle the routing path list.
[60.771610] [INFO] Waiting until the client’s ready to handle the routing path list.
[63.772363] [INFO] Waiting until the client’s ready to handle the routing path list.
[66.773184] [ERROR] MUDEC_00045: The client doesn’t response with DHCP protocol
[66.773682] [INFO] Waiting until the client’s ready to handle the routing path list.
[69.774241] [INFO] Waiting until the client’s ready to handle the routing path list.
[72.774894] [INFO] Waiting until the client’s ready to handle the routing path list.
[75.775719] [INFO] Waiting until the client’s ready to handle the routing path list.
[78.776448] [INFO] Waiting until the client’s ready to handle the routing path list.
[81.777134] [INFO] Waiting until the client’s ready to handle the routing path list.
[84.778321] [INFO] Waiting until the client’s ready to handle the routing path list.
[87.779082] [INFO] Waiting until the client’s ready to handle the routing path list.
[90.779646] [INFO] Waiting until the client’s ready to handle the routing path list.
[93.780239] [INFO] Waiting until the client’s ready to handle the routing path list.
[96.781001] [INFO] Waiting until the client’s ready to handle the routing path list.
[99.781479] [INFO] Waiting until the client’s ready to handle the routing path list.
[102.781904] [INFO] Waiting until the client’s ready to handle the routing path list.
[105.783374] [INFO] Waiting until the client’s ready to handle the routing path list.
[108.784403] [INFO] Waiting until the client’s ready to handle the routing path list.
[111.785977] [INFO] Waiting until the client’s ready to handle the routing path list.
[114.787606] [INFO] Waiting until the client’s ready to handle the routing path list.
[117.788345] [INFO] Waiting until the client’s ready to handle the routing path list.
[120.788975] [INFO] Waiting until the client’s ready to
Did you try to use -I option? If your answer is yes and you still saw above MUDEC_0044 and MUDEC_00045 errors, then it doesn’t make sense at all. When it turns on its function goes to completely different path so it should not show these errors. Please re-check it again whether -I option is applied correctly.