winmx beta crashing or not able to connect to the wpn

[icedragon aka bughunter]

this problem effects win2k and xp and is a windows issue with how failed dns quieries are handled.....due to vladd and pies utter stupidty in allowing RIAA to conect to the wpn and therefore flood the network and over load primaries nt5 machines tie them selves up in knotts trying to connect .......1 st solution is in settins host name resolution instead of using winmx to resolve host names choose the option to use a external source, here simply enter in your isp primary dns server on port 53.....
second solution is to go to this web site http://www.speedguide.net/downloads.php
and download this patch  winxp_dnscache.zip
this will fix this issue.

Description: Patch Windows 2k/XP not to cache failed DNS entries. By default, when a DNS lookup fails (due to temporary DNS problems), Windows still caches the unsuccessful DNS query, and in turn fails to connect to a host regardless of the fact that the DNS server might be able to handle your lookup seconds later This patch fixes the problem by configuring the DNS client to continue sending queries to an unresponsive network.

 i have successfully tested this on my beta which has now been online for days with no problems at all,,,,,note it also seems to help with dl and up load timeouts.......long live winmx  down with the pie fa****s

[InTheMx]

I've been using this patch, winxp_dnscache.zip, for years and it works quite well. Never even thought about the benefits it would have in connection with WinMX. Good   !

[KM]

shouldn't be any real differences with that registry entry, the only case where it should make a difference is if there is a temporary failure of multiple DNS servers then DNS resolution could be hampered a little, but winmx only uses DNS lookups when it first connects to find peer caches so shouldn't be effected anywhere else

[icedragon aka bughunter]

im not sure what to tell you km....all i did was look at packet captures as winmx beta tries to connect to the network.....like a great majority of users i was either getting  a crash of the beta thru ntdll.dll or it would sit in a endless loop trying to connect......after researching the problem i tried the registry patch as i have described....and not only did it stop the ntdll.dll from crashing but it connected to the wpn even as a secondry i get over 1700 rooms listing and as for files it has improved things so well on that side of the ledger i now have to run mxmonie......its gone from a transfer success rate of less then 30% to better then 95% .....what you say is normally perfectly true as far as dns is concerned....but i feel in light of the current tactics being employed by riaa and associates sometimes we have to think out side the square for a solution....