Roel Niesen Posted December 14, 2021 Share Posted December 14, 2021 Hello, We use VM Tools 9.2.1 on hypervisor 8.0. I got today a problem that some vm's couldn't contact the active directory. After some testing I found out that the network settings weren't complet. (ipconfig /all) When I go to ncpa.cpl and setup the ipv4 settings for the network card, the manuel settings are change to automaticly after save. The settings are ok, but the screen is not correct: I asked for chat support but that was denied, so I created a ticket. Does someone knows: - is this normal (nope because on 1 of the 4 servers it's working like expicted) - how to fix this (netsh int ipv4 reset en netsh winsock reset didn't do the trick) Thanks. Link to comment
0 Sjoerd Van den Nieuwenhof Posted December 15, 2021 Share Posted December 15, 2021 Hi, Take a look if there are Ghost nics present. https://support.citrix.com/article/CTX221733 This is an old article and for VMWare, but it's the same for XenServer. You can also remove all Citrix NIC software and drivers, and then install them as clean install. Link to comment
0 Alan Lantz Posted December 15, 2021 Share Posted December 15, 2021 Yep, that is what I would do. Remove all of the nics and hidden nics and see if it will look right next time. I've fought this a few times myself over the years. --Alan-- Link to comment
0 Boby John1709155536 Posted December 16, 2021 Share Posted December 16, 2021 This can happen at times - check this : https://support.citrix.com/article/CTX292687 Link to comment
Question
Roel Niesen
Hello,
We use VM Tools 9.2.1 on hypervisor 8.0.
I got today a problem that some vm's couldn't contact the active directory.
After some testing I found out that the network settings weren't complet.
(ipconfig /all)
When I go to ncpa.cpl and setup the ipv4 settings for the network card, the manuel settings are change to automaticly after save.
The settings are ok, but the screen is not correct:
I asked for chat support but that was denied, so I created a ticket.
Does someone knows:
- is this normal (nope because on 1 of the 4 servers it's working like expicted)
- how to fix this (netsh int ipv4 reset en netsh winsock reset didn't do the trick)
Thanks.
Link to comment
3 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now