B
BD
Hi, all.
I have a PC which had XP SP2 installed, along with several post-SP2
updates.
I applied SP3.
Once SP3 was applied, I noticed that TCP/IP functionality was
extremely flaky - even after shutting down and disabling the Windows
Firewall (I use a 3rd party firewall).
Internet apps fail to connect - no DNS resolution, no nothing.
I did an ipconfig, and I see a valid internal address for the NIC (I'm
running DHCP internally off a D-Link 504 router).
I ping the router's IP, and I get a couple of timeouts - and then a
couple of valid ping responses.
After that point, my client apps can connect.
I let the machine sit idle for a few minutes, and my client apps fail
again.
I ping the router once more - timeouts followed by responses, after
which the apps can connect.
I updated my NIC driver (on-board NForce4 NIC) - behavior is the same.
-just curious if folks have seen similar behavior after applying
SP3...
Thanks!!
BD
I have a PC which had XP SP2 installed, along with several post-SP2
updates.
I applied SP3.
Once SP3 was applied, I noticed that TCP/IP functionality was
extremely flaky - even after shutting down and disabling the Windows
Firewall (I use a 3rd party firewall).
Internet apps fail to connect - no DNS resolution, no nothing.
I did an ipconfig, and I see a valid internal address for the NIC (I'm
running DHCP internally off a D-Link 504 router).
I ping the router's IP, and I get a couple of timeouts - and then a
couple of valid ping responses.
After that point, my client apps can connect.
I let the machine sit idle for a few minutes, and my client apps fail
again.
I ping the router once more - timeouts followed by responses, after
which the apps can connect.
I updated my NIC driver (on-board NForce4 NIC) - behavior is the same.
-just curious if folks have seen similar behavior after applying
SP3...
Thanks!!
BD