Hello,
Some weeks ago i updated a server of a customer from 4.0 to v5.5. This was a mistake anyway, but that's another topic...
Did the update because we have to run a Win2012 machine on it.
Soon i recognized that i have troubles accessing the freshly installed machine by RDP. Some times it works, but mostly it doesn't. It simply times out. All other VMs on the host (Win2008) seem to work just fine (Haven't heard anything else from the users).
From another VM on the same host i started to ping the W2012 machine:
Ping wird ausgeführt für 172.30.50.135 mit 32 Bytes Daten:
Antwort von 172.30.50.135: Bytes=32 Zeit<1ms TTL=128
Zeitüberschreitung der Anforderung.
Antwort von 172.30.50.135: Bytes=32 Zeit=1ms TTL=254
Antwort von 172.30.50.135: Bytes=32 Zeit=1ms TTL=254
Antwort von 172.30.50.135: Bytes=32 Zeit=1ms TTL=254
Huh?? One ping with TTL 128, one timed out, then all further ones with TTL 254, can't access the machine...
After around three minutes the TTL jumps back to 128, and I'm able to access the machine again.
If i disconnect and wait for some minutes, the same happens again... Very strange...
Haven't tried to use a E1000 network adapter instead of vmxnet3 yet, but would like to prevent that if possible.
Any ideas what i could try?
Thank you
Urs