ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual Server 2005

Recent Virtual Server 2005 posts

* PAE switch
* VMRC doesn"t connect to guest
* I can to install a cluster with 4 nodes with virtual server 2005 R2 with iscsi?
* Can"t access DVD Drive
* VS2005: Color depth (install), CPUID, Solaris & HP-IA64, and other questions
* 64 bit OS
* MOre Performance
* VMRC Negotiate Authentication
* Virtual Server access
* Virtual Server and VB.NET
* Seeking an MCT for a VS delivery
* how to connect VS by Remote Desktop Connection?
* Documentation for DEC/Intel 21140 advanced settings
* Support drivers
* Migrate physical XP computer?
* VM Not Starting Automatically
* Fixed v. Dynamic sized disks
* Virtual Server DC
* Virtual Server 2005 R2 Sp1 bata
* no option to use "external network adapter"

Add Solution

DNS and DHCP work on first VM only an related wierdness

Source: microsoft.public.virtualserver
Sent: 04/17/2007
From: Michael Kleinpaste
Message:

I have two VMs on VS2005 right now. The VM1 works without a hitch, but VM2 is
flaky.

I checked the switch and it is allowing multiple MAC addresses per port. In
fact both the Physical MAC address and the Virtual MAC addresses show up.

On VM2, when I assign a static I can ping a node on the physical network via
the target system's IP Address, but I can't ping it by hostname to the
physical network. I receive the error, "Ping request could not find host
HOSTNAME. Please check the name and try again." When I set DHCP it recieves
a self-assigned address (169.254.x.x). With the static address set the only
systems I can ping by the HOSTNAME are the VS2005 host system AND the first
VM in the same VS2005 instance.

Here's the really wierd part. The hostname of the Host OS and the other VM
are being served by the DC on the physical network.

Any help with this would be great, since I'd like all the VM's to be on the
same domain.

Thanks

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: DNS and DHCP work on first VM only an related wierdness

Sent: 04/17/2007
From: Steve Jain <(email address - cut out)>
Message:

On Tue, 17 Apr 2007 15:42:00 -0700, Michael Kleinpaste
<(email address - cut out)> wrote:

Do both VMs have a unique MAC and SID?

----------- ---- --- -- - - - -
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/

Show quoted text

>I have two VMs on VS2005 right now. The VM1 works without a hitch, but VM2 is
>flaky.
>
>I checked the switch and it is allowing multiple MAC addresses per port. In
>fact both the Physical MAC address and the Virtual MAC addresses show up.
>
>On VM2, when I assign a static I can ping a node on the physical network via
>the target system's IP Address, but I can't ping it by hostname to the
>physical network. I receive the error, "Ping request could not find host
>HOSTNAME. Please check the name and try again." When I set DHCP it recieves
>a self-assigned address (169.254.x.x). With the static address set the only
>systems I can ping by the HOSTNAME are the VS2005 host system AND the first
>VM in the same VS2005 instance.
>
>Here's the really wierd part. The hostname of the Host OS and the other VM
>are being served by the DC on the physical network.
>
>Any help with this would be great, since I'd like all the VM's to be on the
>same domain.
>
>Thanks

Re: DNS and DHCP work on first VM only an related wierdness

Sent: 04/18/2007
From: Michael Kleinpaste
Message:

Each has it's own static MAC. 00-03-FF-1C-15-91 for VM1 and
00-03-FF-1C-15-90 for VM 2. As far as the SID, I don't know how to view it,
and I can't find anywhere in the VS2005 Admin site that shows it either.
Unless I'm over looking something.

"Steve Jain" wrote:

Show quoted text

> On Tue, 17 Apr 2007 15:42:00 -0700, Michael Kleinpaste
> <(email address - cut out)> wrote:
>
> >I have two VMs on VS2005 right now. The VM1 works without a hitch, but VM2 is
> >flaky.
> >
> >I checked the switch and it is allowing multiple MAC addresses per port. In
> >fact both the Physical MAC address and the Virtual MAC addresses show up.
> >
> >On VM2, when I assign a static I can ping a node on the physical network via
> >the target system's IP Address, but I can't ping it by hostname to the
> >physical network. I receive the error, "Ping request could not find host
> >HOSTNAME. Please check the name and try again." When I set DHCP it recieves
> >a self-assigned address (169.254.x.x). With the static address set the only
> >systems I can ping by the HOSTNAME are the VS2005 host system AND the first
> >VM in the same VS2005 instance.
> >
> >Here's the really wierd part. The hostname of the Host OS and the other VM
> >are being served by the DC on the physical network.
> >
> >Any help with this would be great, since I'd like all the VM's to be on the
> >same domain.
> >
> >Thanks
>
> Do both VMs have a unique MAC and SID?
>
> ----------- ---- --- -- - - - -
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/
>

Re: DNS and DHCP work on first VM only an related wierdness

Sent: 04/18/2007
From: Michael Kleinpaste
Message:

That's where the wierdness comes in. It has had a static address with the
correct gateway and DNS server address since the beginning. FYI - I changed
the MAC addresses and still no go.

Here's the ipconfig of VM1:
Windows IP Configuration

Host Name . . . . . . . . . . . . : Contoso1
Primary Dns Suffix . . . . . . . : XXXXxxxxxx.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : XXXXxxxxxx.local

Ethernet adapter Inside Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-03-FF-11-15-91
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.96
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.250
DNS Servers . . . . . . . . . . . : 192.168.0.1
192.168.0.202

Here's the ipconfig of VM2:
Windows IP Configuration

Host Name . . . . . . . . . . . . : IM
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-03-FF-1C-23-90
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.44
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.250
DNS Servers . . . . . . . . . . . : 192.168.0.1

Here's the specifics of the wierd part with VM2 (remember VM1 works without
issue as though it was not virtualized):

FROM VM2
1. Pinging the IP address of a real system returns 4 successful replies.
2. Pinging the VS by either IP or hostname returns 4 successful replies.
3. Pinging a VM on the hosting VS by either IP or hostname returns 4
successful replies.
4. Pinging the hostname of a real system returns a reply of "Ping request
could not find host thomas. Please check the name and try again."

So from these results, what I am seeing is that it CAN reach the real
systems over the network (1), it DOES receive DNS information (2 and 3) from
the same DNS server as VM1 uses. However, it is NOT able to use this
information when it comes to a real system other than the hosting VS(4).

"Bill Grant" wrote:

Show quoted text

> If it is getting an APIPA address (169.254.x.y) it is not getting its
> network config from DHCP as it should. If you give it a static IP address
> and netmask you will also need to give it the correct DNS address to contact
> other machines by name. You will also need to give it the correct default
> gateway address to contact any machines in a different IP subnet.
>
>
>

Re: DNS and DHCP work on first VM only an related wierdness

Sent: 04/18/2007
From: "Bill Grant" <not.available@online>
Message:

"Steve Jain" <(email address - cut out)> wrote in message
news:(email address - cut out)...

If it is getting an APIPA address (169.254.x.y) it is not getting its
network config from DHCP as it should. If you give it a static IP address
and netmask you will also need to give it the correct DNS address to contact
other machines by name. You will also need to give it the correct default
gateway address to contact any machines in a different IP subnet.

Show quoted text

> On Tue, 17 Apr 2007 15:42:00 -0700, Michael Kleinpaste
> <(email address - cut out)> wrote:
>
>>I have two VMs on VS2005 right now. The VM1 works without a hitch, but VM2
>>is
>>flaky.
>>
>>I checked the switch and it is allowing multiple MAC addresses per port.
>>In
>>fact both the Physical MAC address and the Virtual MAC addresses show up.
>>
>>On VM2, when I assign a static I can ping a node on the physical network
>>via
>>the target system's IP Address, but I can't ping it by hostname to the
>>physical network. I receive the error, "Ping request could not find host
>>HOSTNAME. Please check the name and try again." When I set DHCP it
>>recieves
>>a self-assigned address (169.254.x.x). With the static address set the
>>only
>>systems I can ping by the HOSTNAME are the VS2005 host system AND the
>>first
>>VM in the same VS2005 instance.
>>
>>Here's the really wierd part. The hostname of the Host OS and the other
>>VM
>>are being served by the DC on the physical network.
>>
>>Any help with this would be great, since I'd like all the VM's to be on
>>the
>>same domain.
>>
>>Thanks
>
> Do both VMs have a unique MAC and SID?
>
> ----------- ---- --- -- - - - -
> Cheers,
> Steve Jain, Virtual Machine MVP
> http://vpc.essjae.com/

Re: DNS and DHCP work on first VM only an related wierdness

Sent: 04/19/2007
From: "Bill Grant" <not.available@online>
Message:

VM2 does not have a DNS suffix configured. So even if it gets the
correct DNS server address it will not be able to ping machines on the
physical network using just computer names. You would need to use the full
name including the suffix (ie the FQDN). If you add the suffix to the server
it should be able to do it with just the name. The dns suffix will be added
to the name to form the FQDN.

"Michael Kleinpaste" <(email address - cut out)> wrote in
message news:(email address - cut out)...

Show quoted text

> That's where the wierdness comes in. It has had a static address with the
> correct gateway and DNS server address since the beginning. FYI - I
> changed
> the MAC addresses and still no go.
>
> Here's the ipconfig of VM1:
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : Contoso1
> Primary Dns Suffix . . . . . . . : XXXXxxxxxx.local
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : XXXXxxxxxx.local
>
> Ethernet adapter Inside Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
> Adapter (Generic)
> Physical Address. . . . . . . . . : 00-03-FF-11-15-91
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.10.96
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.10.250
> DNS Servers . . . . . . . . . . . : 192.168.0.1
> 192.168.0.202
>
> Here's the ipconfig of VM2:
> Windows IP Configuration
>
> Host Name . . . . . . . . . . . . : IM
> Primary Dns Suffix . . . . . . . :
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
>
> Ethernet adapter Local Area Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
> Adapter (Generic)
> Physical Address. . . . . . . . . : 00-03-FF-1C-23-90
> DHCP Enabled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 192.168.10.44
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.10.250
> DNS Servers . . . . . . . . . . . : 192.168.0.1
>
> Here's the specifics of the wierd part with VM2 (remember VM1 works
> without
> issue as though it was not virtualized):
>
> FROM VM2
> 1. Pinging the IP address of a real system returns 4 successful replies.
> 2. Pinging the VS by either IP or hostname returns 4 successful replies.
> 3. Pinging a VM on the hosting VS by either IP or hostname returns 4
> successful replies.
> 4. Pinging the hostname of a real system returns a reply of "Ping request
> could not find host thomas. Please check the name and try again."
>
> So from these results, what I am seeing is that it CAN reach the real
> systems over the network (1), it DOES receive DNS information (2 and 3)
> from
> the same DNS server as VM1 uses. However, it is NOT able to use this
> information when it comes to a real system other than the hosting VS(4).
>
> "Bill Grant" wrote:
>
>> If it is getting an APIPA address (169.254.x.y) it is not getting its
>> network config from DHCP as it should. If you give it a static IP address
>> and netmask you will also need to give it the correct DNS address to
>> contact
>> other machines by name. You will also need to give it the correct default
>> gateway address to contact any machines in a different IP subnet.
>>
>>
>>

Re: DNS and DHCP work on first VM only an related wierdness

Sent: 04/20/2007
From: Michael Kleinpaste
Message:

Thanks, Bill!

That was the issue. I added our internal domain to the default suffix under
Computer Name and blam. I'm able to connect to the domain and register the
computer.

"Bill Grant" wrote:

Show quoted text

> VM2 does not have a DNS suffix configured. So even if it gets the
> correct DNS server address it will not be able to ping machines on the
> physical network using just computer names. You would need to use the full
> name including the suffix (ie the FQDN). If you add the suffix to the server
> it should be able to do it with just the name. The dns suffix will be added
> to the name to form the FQDN.

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: