• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 585
  • Last Modified:

WinXP SP2 VMs Dropping IP Addresses and/or Not Renewing IP Upon Reboot

We have about 250 VMs running Windows XP SP2 on one of our clusters experiencing the same issue whereby the VMs will either lose the IP address if left alone over the weekend and/or they do not renew their IP address. The only fix we have is to (a) completely power off the VM or remove/re-add the Virtual NIC. All the VMs are running the latest VMware Tools, and our network engineering people say their investigation reveals no issues with respect to the networking infrastructure. Has anyone seen this problem? It started with just a few VMs (8 to 10) but now it's becoming a more serious issue. I'm waiting to get the Event Viewer logs, but this is one error we've seen:

TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

I do know about the various TCPIP.SYS patches / hex editor hacks out there, but as this is a corporate cluster I'm trying to stay on the conservative side with respect to my troubleshooting approaches- for now. Any input would be greatly appreciated!
  • 2
1 Solution
Paul SolovyovskyCommented:
how large are your vswitches?  I would check them first since 8 ports per vswitch are used by vmware.  I'm not sure if the connections are per vswitch, host, or cluster but breaking them out to more vswitches is worth a try if you have the physical ports to support them.

I would give VMWare a support call as well since this is a production environment they may have a simple solution.
I would recommend doing a netstat on one of the xp machines and try to see what the machine is listening/talking to. With XP SP2, they built in some type of security thing to kill the connection once it passes a certain number of tcp connections. This was to prevent the outbreak of viruses and worms.

I would assume you have some type of worm floating around or an innocent type of application that is just making alot of noise on the network. Either way you should have a better understanding of why the machines are losing connectivity.

Hope that helps.
Darth_SidiousAuthor Commented:
paulsolov / philtpaik,

Thank you both for your excellent suggestions- I opened the SR with VMWare and we are talking with the SAs to have them commence the netstat. Will update soon.
Darth_SidiousAuthor Commented:
Issue was related to a DNS update made by the DNS team which did not fully replicate across.

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now