• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 382
  • Last Modified:

Virtual Server VMs stopped responding to machine name, but ip works

Hello,
I have a windows server 2003 machine running virtual server 2005. It has several virtual machines on it and they had been responding fine for years now. All of sudden, with no apparent reason I know of, some have stopped answer to the machine name. They answer fine to the ip.

For example, when connecting with Remote desktop, I have used "sql2005vs2008 /admin" to connect to the console session for years. Now it doesn't connect. However, if I use "192.168.0.50 /admin" I can connect with no problem.

To muddy the waters, I have other machines on the same host that still answer to their machine name.

I have rebooted my firewall / dhcp server several times as well as the vm's. The host has been rebooted as well. Any other ideas?
0
dgerler
Asked:
dgerler
  • 2
1 Solution
 
dave_itCommented:
Do you get the host name if you do an nslookup?
0
 
dgerlerAuthor Commented:
"nslookup sql2005vs2008" gives me two public ip addresses that are not mine. I should get private ip's.

When I do "nslookup reg12" I get the private ip of that machine.
0
 
dgerlerAuthor Commented:
Seems the problem was bogus domain names in the dns forwarder. I changed it to local and it works now.

Thank you.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

How do you know if your security is working?

Protecting your business doesn’t have to mean sifting through endless alerts and notifications. With WatchGuard Total Security Suite, you can feel confident that your business is secure, meaning you can get back to the things that have been sitting on your to-do list.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now