TCP stack corrupted

I applied the latest round of Windows updates to a whole bunch of my
Windows 2003 Web servers last night.
I had previously tested the updates on a dev server as usual so I knew
they were ok?

One of my servers however, suffered a partial corruption of it's tcp
stack causing it to lose it's external IP.
Each of the servers has 2 NIC, one for the external (public facing)
traffic and one for internal database connectivity and management.
Strangely, I was still able to remote in to the machine using the
management LAN, although
it had stopped responding to ping or anything else on the external
interface.

Doing an ipconfig returned an error, trying to view the property
sheets for the NIC in Network Connections also failed, and in Task
Manager, on the Networks tab - it said "There are no active network
adapters" which I though a trifle strange as I was talking to it over
one of them!!

I issued a tcp reset using netsh int ip reset reset.txt and did a
reboot. Oops! that broke both network connections of course.
So I had to get onto the tech support at the data centre to go and
physically log on and restore the management LAN settings so I could
connect again.

That fixed it, and having re-entered the external NIC settings we are
back up and running again.

Nothing in the error logs, as usual.

So the point of all this - has anyone else suffered any tcp problems
with the latest SMB update that was released on tuesday? or is this an
act of dog as usual.

Alister

Thank you for sharing your experience with us. We did receive some report
regarding the Tuesday update as such taking long time to install or slowing
down the system after installation.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Alister" <(E-Mail Removed)> wrote in message
news:444f813c-6fd2-4097-8e51-(E-Mail Removed)...
>I applied the latest round of Windows updates to a whole bunch of my
> Windows 2003 Web servers last night.
> I had previously tested the updates on a dev server as usual so I knew
> they were ok?
>
> One of my servers however, suffered a partial corruption of it's tcp
> stack causing it to lose it's external IP.
> Each of the servers has 2 NIC, one for the external (public facing)
> traffic and one for internal database connectivity and management.
> Strangely, I was still able to remote in to the machine using the
> management LAN, although
> it had stopped responding to ping or anything else on the external
> interface.
>
> Doing an ipconfig returned an error, trying to view the property
> sheets for the NIC in Network Connections also failed, and in Task
> Manager, on the Networks tab - it said "There are no active network
> adapters" which I though a trifle strange as I was talking to it over
> one of them!!
>
> I issued a tcp reset using netsh int ip reset reset.txt and did a
> reboot. Oops! that broke both network connections of course.
> So I had to get onto the tech support at the data centre to go and
> physically log on and restore the management LAN settings so I could
> connect again.
>
> That fixed it, and having re-entered the external NIC settings we are
> back up and running again.
>
> Nothing in the error logs, as usual.
>
> So the point of all this - has anyone else suffered any tcp problems
> with the latest SMB update that was released on tuesday? or is this an
> act of dog as usual.
>
> Alister