Problem with windows 2003 AD in vSphere

[Maykol]

Hello

everybody, I have a problem with windows 2003 on vSphere, I have an AD

running on the windows, and almost every day in the morning the machines

can not access the AD, I open the virtual machine AD, and perform a

refresh in the NIC of AD and the same back to running.

I have

this problem on three different companies.

Thanks....

[Rumple]

Many of us are running multiple different versions of Active directory on vmware without any issues.

what is the commonality between the environment hardware wise? Are you using managed switches or unmanaged?

Are you using the flexible nic or the e1000 in these machines?

[Maykol]

Don't have any commonality between the environment hardware, and I use e1000 driver for the NIC, and the switches are unmanaged. Thanks.

[Rumple]

so if you setup monitoring of the servers, are you seeing the VM actually drop off the network (ie, it stops responding to ping's).

What kind of events are you seeing in the event logs on those serverswhen the problem starts?

Any commonality with backups (ie, are you using something like a vranger or other product for image level backups and backups finish at the time the machines drop off?

[Maykol]

I do not use any

backup software on that server, and the ping don't stop, only AD not respond and the events are normal Thanks

[Rumple]

Well, AD isn't a service but an actual core component of the operating system so it doesn't appear it’s a network problem per se.

Enabling and disabling the nic can force other components to re-kicking.

When its not responding, have you tried doing an nslookup on the server to see if it responds to dns?

Another thing to try is to restart the netlogon service.

Any Active directory event logs being generated?

Is there any commonality in the timing between the 3 environments that you can find. Typically when I setup systems I do them the same everytime (including setting up scheduled backup tasks in the operating system) and patching,etc

[Maykol]

I will

analyze it and I will post as soon as get the error again, thank you very much for

now