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 PC

Recent Virtual PC posts

* Network Connections
* Terminal Service connection to a Virtual Machine
* Graphics
* Virtual Server R2 Additions for Linux... anyluck on VPC2004?
* problems with shared folder access
* VPC on WinXP SP2
* recovery of data from a virtual hard disk?
* Internet Access - Is this possible?
* Network drive connection
* Intel Mac Book Pro Virtual PC
* miffed by internet connection
* Can I get there from here?
* Virtual Server goes free, can VPC be far behind?
* virtual pc is not running on windows xp sp2
* c|net confirming Virtual Server R2 Enterprise, a free download
* debugging guest
* zeroing in DOS
* Relocate VirtualDisks to different drive
* Can"t Print To Shared Printer
* Limited acces from the internet

Add Solution

Server sees client with different IP address than DHCP assigned it

Source: microsoft.public.virtualpc
Sent: 04/05/2006
From: chris seiter
Message:

I have set up a network (using the trial version of VPC), with the trial
version of 2003 R2 on the server and XP as the client. DHCP, DNS, AD, and
IIS (I wanted to test the WSUS also) are all loaded on the server. The
server goes to our network to get DNS resolution, and the client goes to the
virtual server. The client is receiving a DHCP address from the virtual
server, which is 192.168.56.175 and can connect to the internet and can map a
shared drive from the server. The server, 192.168.56.80, sees the client as
208.48.34.132 when pinging with the client name. When I ping -a with
192.168.56.175, it sees the client and returns the name
"test-XP-client.test.com", which is correct. When I use our regular network
to ping the server with the name, I get 208.48.34.132 as the IP and a request
time out. I ping the client and get the same number as the server. When I
ping using ping -a and the IP addresses assigned to the virtual machines, I
get a response. It looks like the DNS on the regular network doesn't
recongnise the VPC address, but where would I go to change that setting?

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Server sees client with different IP address than DHCP assigned it

Sent: 04/05/2006
From: "Ben Armstrong [MSFT]" <(email address - cut out)>
Message:

Are you using a wireless or a wired network card on the physical computer?
--
Cheers,
Benjamin Armstrong
===============================
Virtual machine Program Manager

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.

chris seiter wrote:

Show quoted text

> I have set up a network (using the trial version of VPC), with the trial
> version of 2003 R2 on the server and XP as the client. DHCP, DNS, AD, and
> IIS (I wanted to test the WSUS also) are all loaded on the server. The
> server goes to our network to get DNS resolution, and the client goes to the
> virtual server. The client is receiving a DHCP address from the virtual
> server, which is 192.168.56.175 and can connect to the internet and can map a
> shared drive from the server. The server, 192.168.56.80, sees the client as
> 208.48.34.132 when pinging with the client name. When I ping -a with
> 192.168.56.175, it sees the client and returns the name
> "test-XP-client.test.com", which is correct. When I use our regular network
> to ping the server with the name, I get 208.48.34.132 as the IP and a request
> time out. I ping the client and get the same number as the server. When I
> ping using ping -a and the IP addresses assigned to the virtual machines, I
> get a response. It looks like the DNS on the regular network doesn't
> recongnise the VPC address, but where would I go to change that setting?

Re: Server sees client with different IP address than DHCP assigne

Sent: 04/10/2006
From: chris seiter
Message:

Sorry for the late reply; I forgot to make it notify me. No, everything is
wired, but now my client cannot connect to the test server. I am receiving a
DHCP-assigned IP adress from it, confirmed with ipconfig /all, and I can ping
it using the 192 number, but I cannot connect to it any other way. WSUS had
detected it as a client, but know it won't; the mapped drive is now not
connecting either.

"Ben Armstrong [MSFT]" wrote:

Show quoted text

> Are you using a wireless or a wired network card on the physical computer?
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
>
> chris seiter wrote:
> > I have set up a network (using the trial version of VPC), with the trial
> > version of 2003 R2 on the server and XP as the client. DHCP, DNS, AD, and
> > IIS (I wanted to test the WSUS also) are all loaded on the server. The
> > server goes to our network to get DNS resolution, and the client goes to the
> > virtual server. The client is receiving a DHCP address from the virtual
> > server, which is 192.168.56.175 and can connect to the internet and can map a
> > shared drive from the server. The server, 192.168.56.80, sees the client as
> > 208.48.34.132 when pinging with the client name. When I ping -a with
> > 192.168.56.175, it sees the client and returns the name
> > "test-XP-client.test.com", which is correct. When I use our regular network
> > to ping the server with the name, I get 208.48.34.132 as the IP and a request
> > time out. I ping the client and get the same number as the server. When I
> > ping using ping -a and the IP addresses assigned to the virtual machines, I
> > get a response. It looks like the DNS on the regular network doesn't
> > recongnise the VPC address, but where would I go to change that setting?
>

Re: Server sees client with different IP address than DHCP assigne

Sent: 04/10/2006
From: "Ben Armstrong [MSFT]" <(email address - cut out)>
Message:

Have you checked to see if any firewalls are in the way?
--
Cheers,
Benjamin Armstrong
===============================
Virtual machine Program Manager

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.

chris seiter wrote:

Show quoted text

> Sorry for the late reply; I forgot to make it notify me. No, everything is
> wired, but now my client cannot connect to the test server. I am receiving a
> DHCP-assigned IP adress from it, confirmed with ipconfig /all, and I can ping
> it using the 192 number, but I cannot connect to it any other way. WSUS had
> detected it as a client, but know it won't; the mapped drive is now not
> connecting either.
>
> "Ben Armstrong [MSFT]" wrote:
>
>> Are you using a wireless or a wired network card on the physical computer?
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> You assume all risk for your use.
>>
>> chris seiter wrote:
>>> I have set up a network (using the trial version of VPC), with the trial
>>> version of 2003 R2 on the server and XP as the client. DHCP, DNS, AD, and
>>> IIS (I wanted to test the WSUS also) are all loaded on the server. The
>>> server goes to our network to get DNS resolution, and the client goes to the
>>> virtual server. The client is receiving a DHCP address from the virtual
>>> server, which is 192.168.56.175 and can connect to the internet and can map a
>>> shared drive from the server. The server, 192.168.56.80, sees the client as
>>> 208.48.34.132 when pinging with the client name. When I ping -a with
>>> 192.168.56.175, it sees the client and returns the name
>>> "test-XP-client.test.com", which is correct. When I use our regular network
>>> to ping the server with the name, I get 208.48.34.132 as the IP and a request
>>> time out. I ping the client and get the same number as the server. When I
>>> ping using ping -a and the IP addresses assigned to the virtual machines, I
>>> get a response. It looks like the DNS on the regular network doesn't
>>> recongnise the VPC address, but where would I go to change that setting?

Re: Server sees client with different IP address than DHCP assigne

Sent: 04/12/2006
From: chris seiter
Message:

All firewalls are off in the test network. I tried connecting to the shared
folder on the test server again with no luck. I am, however, able to map to
a shared folder from the test client to the real network outside the test
environment completely. Am I missing something like giving a virtual NIC two
IP addresses?

"Ben Armstrong [MSFT]" wrote:

Show quoted text

> Have you checked to see if any firewalls are in the way?
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
>
> chris seiter wrote:
> > Sorry for the late reply; I forgot to make it notify me. No, everything is
> > wired, but now my client cannot connect to the test server. I am receiving a
> > DHCP-assigned IP adress from it, confirmed with ipconfig /all, and I can ping
> > it using the 192 number, but I cannot connect to it any other way. WSUS had
> > detected it as a client, but know it won't; the mapped drive is now not
> > connecting either.
> >
> > "Ben Armstrong [MSFT]" wrote:
> >
> >> Are you using a wireless or a wired network card on the physical computer?
> >> --
> >> Cheers,
> >> Benjamin Armstrong
> >> ===============================
> >> Virtual machine Program Manager
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no rights.
> >> You assume all risk for your use.
> >>
> >> chris seiter wrote:
> >>> I have set up a network (using the trial version of VPC), with the trial
> >>> version of 2003 R2 on the server and XP as the client. DHCP, DNS, AD, and
> >>> IIS (I wanted to test the WSUS also) are all loaded on the server. The
> >>> server goes to our network to get DNS resolution, and the client goes to the
> >>> virtual server. The client is receiving a DHCP address from the virtual
> >>> server, which is 192.168.56.175 and can connect to the internet and can map a
> >>> shared drive from the server. The server, 192.168.56.80, sees the client as
> >>> 208.48.34.132 when pinging with the client name. When I ping -a with
> >>> 192.168.56.175, it sees the client and returns the name
> >>> "test-XP-client.test.com", which is correct. When I use our regular network
> >>> to ping the server with the name, I get 208.48.34.132 as the IP and a request
> >>> time out. I ping the client and get the same number as the server. When I
> >>> ping using ping -a and the IP addresses assigned to the virtual machines, I
> >>> get a response. It looks like the DNS on the regular network doesn't
> >>> recongnise the VPC address, but where would I go to change that setting?
>

Re: Server sees client with different IP address than DHCP assigne

Sent: 04/12/2006
From: "Ben Armstrong [MSFT]" <(email address - cut out)>
Message:

Something strange appears to be happening with name resolution. Does
anything work (like file share mapping) if you use IP addresses instead
of names?
--
Cheers,
Benjamin Armstrong
===============================
Virtual machine Program Manager

This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use.

chris seiter wrote:

Show quoted text

> All firewalls are off in the test network. I tried connecting to the shared
> folder on the test server again with no luck. I am, however, able to map to
> a shared folder from the test client to the real network outside the test
> environment completely. Am I missing something like giving a virtual NIC two
> IP addresses?
>
> "Ben Armstrong [MSFT]" wrote:
>
>> Have you checked to see if any firewalls are in the way?
>> --
>> Cheers,
>> Benjamin Armstrong
>> ===============================
>> Virtual machine Program Manager
>>
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>> You assume all risk for your use.
>>
>> chris seiter wrote:
>>> Sorry for the late reply; I forgot to make it notify me. No, everything is
>>> wired, but now my client cannot connect to the test server. I am receiving a
>>> DHCP-assigned IP adress from it, confirmed with ipconfig /all, and I can ping
>>> it using the 192 number, but I cannot connect to it any other way. WSUS had
>>> detected it as a client, but know it won't; the mapped drive is now not
>>> connecting either.
>>>
>>> "Ben Armstrong [MSFT]" wrote:
>>>
>>>> Are you using a wireless or a wired network card on the physical computer?
>>>> --
>>>> Cheers,
>>>> Benjamin Armstrong
>>>> ===============================
>>>> Virtual machine Program Manager
>>>>
>>>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>>> You assume all risk for your use.
>>>>
>>>> chris seiter wrote:
>>>>> I have set up a network (using the trial version of VPC), with the trial
>>>>> version of 2003 R2 on the server and XP as the client. DHCP, DNS, AD, and
>>>>> IIS (I wanted to test the WSUS also) are all loaded on the server. The
>>>>> server goes to our network to get DNS resolution, and the client goes to the
>>>>> virtual server. The client is receiving a DHCP address from the virtual
>>>>> server, which is 192.168.56.175 and can connect to the internet and can map a
>>>>> shared drive from the server. The server, 192.168.56.80, sees the client as
>>>>> 208.48.34.132 when pinging with the client name. When I ping -a with
>>>>> 192.168.56.175, it sees the client and returns the name
>>>>> "test-XP-client.test.com", which is correct. When I use our regular network
>>>>> to ping the server with the name, I get 208.48.34.132 as the IP and a request
>>>>> time out. I ping the client and get the same number as the server. When I
>>>>> ping using ping -a and the IP addresses assigned to the virtual machines, I
>>>>> get a response. It looks like the DNS on the regular network doesn't
>>>>> recongnise the VPC address, but where would I go to change that setting?

Re: Server sees client with different IP address than DHCP assigne

Sent: 04/14/2006
From: chris seiter
Message:

I'm not sure why it works, but I can connect to the server now. The IP
addresses are still different, though. I pinged the domain test.com and got
192.168.10.1, which is our wireless router. Why it got that I have no clue.
So I decided let's take out the reason it can't see other addresses that have
different network numbers: the subnet. I turned the test.com network to a
class B network, and viola, there's everything. The servers don't show up in
the drop-down boxes when I map or connect through network connections, but if
I type it in manually it will connect. I am able to connect to all folders
that are mapped across both networks, the test and our real one perfectly.
Thanks for all your help.

"Ben Armstrong [MSFT]" wrote:

Show quoted text

> Something strange appears to be happening with name resolution. Does
> anything work (like file share mapping) if you use IP addresses instead
> of names?
> --
> Cheers,
> Benjamin Armstrong
> ===============================
> Virtual machine Program Manager
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
> You assume all risk for your use.
>
> chris seiter wrote:
> > All firewalls are off in the test network. I tried connecting to the shared
> > folder on the test server again with no luck. I am, however, able to map to
> > a shared folder from the test client to the real network outside the test
> > environment completely. Am I missing something like giving a virtual NIC two
> > IP addresses?
> >
> > "Ben Armstrong [MSFT]" wrote:
> >
> >> Have you checked to see if any firewalls are in the way?
> >> --
> >> Cheers,
> >> Benjamin Armstrong
> >> ===============================
> >> Virtual machine Program Manager
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no rights.
> >> You assume all risk for your use.
> >>
> >> chris seiter wrote:
> >>> Sorry for the late reply; I forgot to make it notify me. No, everything is
> >>> wired, but now my client cannot connect to the test server. I am receiving a
> >>> DHCP-assigned IP adress from it, confirmed with ipconfig /all, and I can ping
> >>> it using the 192 number, but I cannot connect to it any other way. WSUS had
> >>> detected it as a client, but know it won't; the mapped drive is now not
> >>> connecting either.
> >>>
> >>> "Ben Armstrong [MSFT]" wrote:
> >>>
> >>>> Are you using a wireless or a wired network card on the physical computer?
> >>>> --
> >>>> Cheers,
> >>>> Benjamin Armstrong
> >>>> ===============================
> >>>> Virtual machine Program Manager
> >>>>
> >>>> This posting is provided "AS IS" with no warranties, and confers no rights.
> >>>> You assume all risk for your use.
> >>>>
> >>>> chris seiter wrote:
> >>>>> I have set up a network (using the trial version of VPC), with the trial
> >>>>> version of 2003 R2 on the server and XP as the client. DHCP, DNS, AD, and
> >>>>> IIS (I wanted to test the WSUS also) are all loaded on the server. The
> >>>>> server goes to our network to get DNS resolution, and the client goes to the
> >>>>> virtual server. The client is receiving a DHCP address from the virtual
> >>>>> server, which is 192.168.56.175 and can connect to the internet and can map a
> >>>>> shared drive from the server. The server, 192.168.56.80, sees the client as
> >>>>> 208.48.34.132 when pinging with the client name. When I ping -a with
> >>>>> 192.168.56.175, it sees the client and returns the name
> >>>>> "test-XP-client.test.com", which is correct. When I use our regular network
> >>>>> to ping the server with the name, I get 208.48.34.132 as the IP and a request
> >>>>> time out. I ping the client and get the same number as the server. When I
> >>>>> ping using ping -a and the IP addresses assigned to the virtual machines, I
> >>>>> get a response. It looks like the DNS on the regular network doesn't
> >>>>> recongnise the VPC address, but where would I go to change that setting?
>

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: