I'm having issues RDPing to a vmware server after rebooting it. After rebooting the server it takes 15-20 mins to remote to the server. This issue been going on for sometime now in my environment, and i need to resolve this issue soon as possible. HELP!!!!!!!!
Are you RDPing using server name, FQDN or IP? If RDP using IP is taking less time than using server name, check DNS records for that server on DC and DNS settings on the server itself.
What OS are you connecting to? Can you ping the server during that 15-20 min? Try watching it from the console and see what the vm thinks it's doing during that time.
Maybe try run ipconfig /registerdns in command prompt and then run ipconfig /flushdns on your host machine and see if this clears up the problem as it sounds like a dns error. If you ping it by ip and then by FQDN what is the reply times for each?
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
Gregg Robertson, MCSE, MCSA, MCTS,MCITP
WIN2k3 enterprise edition. Roger that! will do.
ok, thnks
It's on all the servers, and it's more like a delay following the reboot of any server in vmware.
What are the response times to the pings via ip address and fqdn?
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
Gregg Robertson, MCSE, MCSA, MCTS,MCITP
Is it the same using the ip address compared to the name when you try rdp?
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
Gregg Robertson, MCSE, MCSA, MCTS,MCITP
Are you having problem connecting to the W2K3 host with VMware Server or to W2K3 guest servers?
no, its more like a delay rpding to a any server in the console after rebooting.
So once you reboot one machine you are battling to connect to any machines via the console in vi client? Or is it just remote desktoping to the specific machine you rebooted?
Sorry just trying to work out the exact problem you have as seem to be getting confused
If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".
Gregg Robertson, MCSE, MCSA, MCTS,MCITP
If you are running RDP 6 client from Vista, you can run this from the command line on it:
netsh interface tcp set global rss=disabled autotuninglevel=disabled
Vista has by default some advanced features in the RDP client that make the best use of your network environment. It is possible that the server is under resourced at startup and can delay an RDP connection.
Dave
Hello,
Which virtualization product are you using? Fusion, WOrkstation, Server, ESX, or ESXi?
Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, Virtualization Practice Analyst[/url]
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]
sorry for the delay, but we're using ESX.
let me give you more info on this issue. I'm not having problems rdping to a server, but whenever i reboot a vm server it's like to delay in rdping to the server after rebooting it and that the issue.
Pls create DNS entry for your windows server.Sometime RDP is slow if the windows server has not been in updated in DNS console.
Hello,
Moved to Virtual Machine and Guest OS forum.
Best regards,
Edward L. Haletky VMware Communities User Moderator, VMware vExpert 2009, Virtualization Practice Analyst[/url]
Now Available: 'VMware vSphere(TM) and Virtual Infrastructure Security: Securing the Virtual Environment'[/url]
Also available 'VMWare ESX Server in the Enterprise'[/url]
[url=http://www.astroarch.com/wiki/index.php/Blog_Roll]SearchVMware Pro[/url]|Blue Gears[/url]|Top Virtualization Security Links[/url]|Virtualization Security Round Table Podcast[/url]