MUDEC_00044
The client isn’t ready yet
This warning message indicates that the DHCP client of your OS wasn't sending IP request with DHCP protocol. Normally this could happen if the firewall of OS blocks DHCP request to TAP-Win32 adapter v9 network device.
MUDEC_00045
The client doesn’t response with DHCP protocol
This error comes out after some times if your OS doesn't send IP request with DHCP protocol to TAP-Win32 adapter v9. So with this error, Mudfish would not work properly because there is no assigned IP address for internal purpose.
- If you're enabled the windows firewall feature or using anti-virus programs, please retry after disabling that features temporarilly.
- Try with enabling or disabling TAP-Win32 adapter v9 device itself at Control Panel.
- Please mark sure that your TAP-Win32 adapter v9 device is DHCP enabled.
MUDEC_00179
Path MTU is wrong.
In my personal opinion, if it doesn't affect your game connection, it doesn't require to be fixed. However if it affects, it could be little complicated:
First please read about what Path MTU (http://en.wikipedia.org/wiki/Path_MTU_Discovery) means. For a short description, it points that your network's pipeline is little bit narrow to send a big packet.
However, this issue could be caused by the false positive of Mudfish tool. Using mtupath(http://www.iea-software.com/products/mtupath.cfm) tool, you can check your real Path MTU.
To address this issue, you can check the following items:
- Check your default MTU set on your network device driver. For example, if you tried or used a fast-pick kind of utilities before, these sometimes changed your MTU value forcibly without notificiation. With visiting the advanced option of each network drivier, you can check it.
- Or tried to change the MTU value of TAP-Win32 adapter with smaller value. Its default value is 1500 (bytes). However it can try with small value (e.g. 1450, 1400, 1300 or a value you'd like to try).