Windows XP SP2 Kills Internet Connections! ⇒ News ⇒ CPG Dragonfly™ CMS
Have you noticed that inexplicably, after applying XP SP2 that certain web pages seem to load slower? Are you experiencing slower/different ftp connection issues? Dropped ftp connections? If you have any of these symptoms and/or other 'out of the blue' issues with performance where multiple TCP connections are needed, you MUST read on! Billy Gates strikes again, apparently continuing to believe that MS knows better than you what your system needs are :GRRRRR:! For a resolution to these issues see this article at Raven's site
absolutely no problems since SP2 installed
Same here, no problems what so ever.
No problems here either... it actually sped up my system substantially... but then again... I don't use IE at all cause it crashes... go figure.
Just for clarification, this is not IE, per se, related. It is the TCP stack that is affected and 100% of all XP SP2 unstallations are affected. You may not need/use multiple connections, but the connections used to be settable in SP1 and were, by default, unlimited. Now they are not settable (without intervention) and are defaulted to 4. If you are using an ftp client that tries to open up multiple connections to speed up transfers and you are perhaps viewing a site with 100 images to display (this is just an example), you will not have the speed that you once had. Obviously these fixes would not be available (nor needed) if things had not changed, and for the worse. Your mileage may very, but make no mistake that everyone is affected.
My understanding of the new settings are in reference to finally establishing limits for RAW IP sockets. Given that your programs would not be using a Raw IP Socket but rather TCP and/or UDP, you and everyone else are unaffected.. RAW Sockets are primarily used in protocol analysis and security tools.... Your FTP program should be using stream or datagram for performance anyway. Sure, if you have 500 screens open to "Ping" people, you'll be affected, but let's be real here. <p>
On the contrary, ftp clients and other P2P communications use various lowlevel and TCP socket communications. This change by MS hinders these and in my particular case nearly brought me to a stand-still as it has countless others. Instead of trying to discredit this post and fix, either use it or don't. I don't really care. As I said before, if it wasn't an issue, there wouldn't be a fix. If you're not affected, then great. Many are and this is the only recourse available. BTW, PHP has built in support for RAW SOCKET communications so it is a part of the core PHP support for serious developers. This not only a common way to write communication applications but is the fastest way also.
Yes, PHP has raw socket communications abilities, but you need to understand that these are intended for INTERNAL server use, thus you don't need to cross the TCP or UDP layers. I mean, why would you need to validate already permissioned internal server communications?
I could no longer reliably load my own web page into my PC regardless of which browser I used. Apache opens as many child processes as it needs and for whatever the reason it was feeding more connections (4 is the new default) than what I could reliably receive. And, so far, 100% of the people who were telling me my page was suddenly loading slower have all said after applying this fix, all is well again. I even saw improvement when I bumped th4 up to 10. I rely on my virus scanning applications to handle the viruses and trojans. I am not going to have my resources blocked by MS simply because they do not know how to write secured software. I do not play any games. As I said, I had problems immediately when only using a browser!
And it even screwed it up when running on my own PC from my local server! The fix FIXED it all - 100%.
Average Score: 3.90
Please take a second and vote for this article:
News last 5 articles