<div>
&quot;nslookup sql2005vs2008&quot; gives me two public ip addresses that are not mine. I should get private ip's. <br />
<br />
When I do &quot;nslookup reg12&quot; I get the private ip of that machine.
</div>


"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.

<div>
Seems the problem was bogus domain names in the dns forwarder. I changed it to local and it works now.<br />
<br />
Thank you.
</div>


Seems the problem was bogus domain names in the dns forwarder. I changed it to local and it works now.

Thank you.

<div>
<div class="content wysiwyg-content">
Hello,<br />
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.<br />
<br />
For example, when connecting with Remote desktop, I have used &quot;sql2005vs2008 /admin&quot; to connect to the console session for years. Now it doesn't connect. However, if I use &quot;192.168.0.50 /admin&quot; I can connect with no problem. <br />
<br />
To muddy the waters, I have other machines on the same host that still answer to their machine name.<br />
<br />
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?
</div>
</div>


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?

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

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

DHCP

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.