Hi.
I am the Anonymous who wrote the first article.
First of all, the "possible fix" from bink.nu is not working. Sorry guys.
I just received an email from the MS-guy. He told me that the limitation is implemented in the TCP/IP stack and you would need to rewrite the tcpip.sys to switch it off. So a simple registry mod won`t do it.
This doesn`t surprise me much cause it`s no deal for any worm to just modify the registry and spread around like before.
I just tried the tcpip.sys from XPSP1a but as you can think, it ended with WinXP refused to boot....
Sorry for the bad news but I think we have to see if it is still present in the final XPSP2.
I have the bad feeling it will be cause the first time i discovered this was in Build 20XX so they should have had enough time to realise the heavy slowdown of some programs (mainly P2P)...
Benny
I am the Anonymous who wrote the first article.
First of all, the "possible fix" from bink.nu is not working. Sorry guys.
I just received an email from the MS-guy. He told me that the limitation is implemented in the TCP/IP stack and you would need to rewrite the tcpip.sys to switch it off. So a simple registry mod won`t do it.
This doesn`t surprise me much cause it`s no deal for any worm to just modify the registry and spread around like before.
I just tried the tcpip.sys from XPSP1a but as you can think, it ended with WinXP refused to boot....
Sorry for the bad news but I think we have to see if it is still present in the final XPSP2.
I have the bad feeling it will be cause the first time i discovered this was in Build 20XX so they should have had enough time to realise the heavy slowdown of some programs (mainly P2P)...
Benny
