Originally posted by: GimpyOne
Well, it turns out I'm a dumba** and I'm not. The main problem I'm was having with SP2 was becuase while I shut down the new Security Center, I forgot to disable it in the services manager...so when I rebooted, the firewall started back up on me and I didn't notice. That fixed and I can now see my instruments.
On the other side of things, there still are issues with my software and SP2, but it isn't with the network support. It turns out they built their software on a client/server database system, and I am running both locally on the same computer. Some of the new bug "fixes" that SP2 has implemented render some of the 9001 certification capabilities they have put into the software unusable. Evidently if you are running them on multiple computers there isn't this problem, I'm not really sure why and of course, they won't tell me. Thankfully I'd don't use them so it isn't a problem for me, but may be for some people in industry.
Well, that could be an instance of the localhost support that changed in XP SP2. MS restricted localhost loopback to only the single 127.0.0.1 IP address, any others in the 127.x.x.x block are totally blocked. The RFC on this could be considered unclear, and MS probably thought that they were erring on the side of security by doing this, although I personally suspect this to be a single code bug, because if the network stack is performing ingress filtering of source-IP-spoofed packets on all interfaces, then this shouldn't even be an issue. I'm guessing that they (mistakenly or intentionally) changed the subnet on the loopback adaptor from 127.0.0.0/255.0.0.0 to 127.0.0.1/255.255.255.255.
So what happens is, some 3rd-party applications that use local network sockets to "talk" between components, that don't use 127.0.0.1 exactly, are probibited from communicating. MS does have a hotfix available, but you need to call their PSS to get it, it's not publically-available on their web site.
Here are some links to investigate that issue (Google "XP SP2 127.0.0.1"):
http://support.microsoft.com/d...x?scid=kb;EN-US;884020
http://forums.devshed.com/archive/t-174587
Interestingly, the second link seems to indicate that someone attempted to obtain the hotfix from MS for this, and it is no longer available, I would like to find out if that's true. I really can't fathom why this isn't available to the public for download yet, or that there isn't some registry-based workaround.
Edit: The plot thickens!
http://support.microsoft.com/default.aspx?kbid=817293
http://www.webservertalk.com/message357981.html
That second link has a reference to KB844020, which when I attempt to access, doesn't come up.
Is this a secret, internal, KB article, or was it pulled? What is contained within?
A Google search for the mysterous 844020 KB article turns up nothing, and no cached entry either.
Edit 2: Nevermind, the "missing" KB article is really 884020, the same one linked above, the referenced thread just typo'ed it. Sorry for the confusion. Doh!