VMware Cloud Community
glassin
Enthusiast
Enthusiast

network issues after tools update 10.2

I have an issue with one of my servers, a secondary exchange server.  After updating the vmtools last week I have some difficult to troubleshoot network issues.  To start with the webpage to manage exchange does not load, eventually times out locally too.  Similarly just attempting to RDP(can ping and telnet fine).  If i console to the server i can login but many things seem to take a very long time like 'applying user settings'.  Since i wanted to look at the network i try to open network and sharing from control panel and it just hangs i can only end process for explorer.exe and restart it.

I have uninstalled and re-installed vmtools.  The upgrade was the only change i made before my weekend reboots anyway.

Un-related / sort of related.  My VDI image had issues with this tools version as well, after upgrade users reported mouse and screen issues so i had rolled back to previous version and haven't been able to revisit that yet.

Tags (1)
Reply
0 Kudos
4 Replies
myounus2008
VMware Employee
VMware Employee

Hope the following KB article helps

VMware Knowledge Base

Issue has been resolved in 10.2.5

Release notes VMware Tools 10.2.5 Release Notes

Hope this helps.

Thank You
Mohammed Younus

Reply
0 Kudos
glassin
Enthusiast
Enthusiast

I mis-typed i am already on 10.2.5.  I should probably edit the title.   but thank you this does similarly describe the behavior i'm seeing.  'port exhaustion'   I removed this from the domain as it was another thing to try and now can't re-join.  I get 'network cannot be found to 'domainname.com'   I am able to join other machines so it only exists here, not a DNS issue although that is the thing that shows the most on MS forums.  Also windows FW is off so something causing network issues.

Reply
0 Kudos
msripada
Virtuoso
Virtuoso

May be it is similar to the issue with July ms patches as described in below url

July 10, 2018 Windows updates cause SQL startup issues due to “TCP port is already in use” errors – ...

Reply
0 Kudos
glassin
Enthusiast
Enthusiast

One thing that became apparent on this server after i removed it from the domain to rejoin (was a recommendation) is that i could not.   'no network path'   I came to find i could not telnet to port 445 to the DC where as all other machine can in order to join.   Windows FW was off as well i disabled the service all together and no AV in the way, so why does this port not work for this one machine?   I have since shut this exchange down to build another, and in that site was easily able to join new pc to domain.

Reply
0 Kudos