Vista - Virtual OS can't connect to internet

Hi

My PC :
Windows vista ultimate SP1
4GB Ram
Direct Cable internet connection
Virtual Server R2 SP1 installed

Virtual OS :
Windows 2003 Server enterprise

Everything is installed correctly (I think), I can access the Admin web page
and I can
start my virtual OS but I can't have access to internet in my virtual OS.

I did many search on web but I can't find a clear way to fix that with clear
steps
on how to fix the issue ? I have installed a Loopback adapter on my vista
but I
don't really know if I have to set some stuff in it (like IP, gateway, dns
....) ? I have also created a virtual network
that connect to the Loopback adapter (But I don't know if I have to make any
setting in virtual server
for that virtual network like DHCP ???). I'm not an expert on network stuff.

Anybody can help ??? Please

Thank you very much !

Richard Martin

"Richard Martin" <martinr0829@xxxxxx> wrote in message
news:eFvp5gVFJHA.2508@xxxxxxInstalling the loopback adapter is a good start. Now you need to install
ICS on the host. Type "share internet connection" into Help and Support for
details of how to do that in Vista. Your cable connection is the one you
want to share and the loopback adapter is the private interface.

Now connect the NIC in the vm to the loopback network (from the settings
option in the VPC console). When you boot the vm it will get its network
config from ICS (it has a built-in mini-DHCP service) and will connect to
the Internet by sharing the host's connection. ICS is a cut-down version of
NAT.

There is another problem which may occur because your guest is running
Server 2003. The server might try to use its own IP address for DNS. If this
happens you need to manually set it to use 192.168.0.1 (which is the
loopback adapter address).

Hi Bill

Thank you very much for the help. It worked like a charm.

I'm sooo happy now

Richard Martin

"Bill Grant" <not.available@xxxxxx> wrote in message
news:#a$Hi3VFJHA.5224@xxxxxx

Is this configuration going to work if there're multiple VMs on the same
host?

Gilgamesh

"Bill Grant" <not.available@xxxxxx> wrote in message
news:%23a$Hi3VFJHA.5224@xxxxxx

Why not? Each machine on the virtual network is sharing the network
connection of the host. The only limit would be the number of IP addresses
available from ICS, which is over 250!

"Gilgamesh" <Gilgamesh4Ever@xxxxxx> wrote in message
news:e1swBXpFJHA.224@xxxxxx

I had Virtual PC installed on Windows 2003 SP2, and I was able to connect an
XP pro VPC to internet. I then installed VIrtual Server 2005 because I
wanted to have Windows Server 2008 also hosted on this machine. Now if I
bring up XP within Virtual Server, it doesn't connect to internet even
thourgh I select loop back adaptor. So, somthing within Virtual server isn't
consistant with VPC and they don't function the same way.

Bottom line, after installing Windows server 2008 as virtual server, I can
neither have XP connected to internet no server 2008.

-G



"Bill Grant" <not.available@xxxxxx> wrote in message
news:%239MIK%23sFJHA.4304@xxxxxx

On Mon, 15 Sep 2008 08:36:38 -0700, "Gilgamesh"
<Gilgamesh4Ever@xxxxxx> wrote:
Not to change the subject, but you know you can install Windows 2008
Server in VPC? You don't need to use Virtual Server to install a
server OS.

--
Cheers,
Steve Jain, Virtual Machine MVP
http://vpc.essjae.com/
I do not work for Microsoft.

Good point. I was able to start server 2008 from VPC but still can't connect
to Internet. The issue seems to be related to DNS queries, however XP
doesn't have this problem.

-G



"Steve Jain" <noreply.-@-.essjae.com> wrote in message
news:414tc4pvv26c1dqch002coltb9kgcr47tv@xxxxxx

As a general rule, a server OS does not work well as an ICS client. Ben
Armstrong has discussed this before in his blog for Server 2003 client and
shared networking.

http://blogs.msdn.com/virtual_pc_guy...06/347965.aspx

Try manually configuring the DNS setting in the vm to point to the
loopback adapter's IP address.


"Gilgamesh" <Gilgamesh4Ever@xxxxxx> wrote in message
news:eWoma34FJHA.1456@xxxxxx

Great article. Changing DNS to 192.168.131.254 fixed the problem.
-G



"Bill Grant" <not.available@xxxxxx> wrote in message
news:%23UM1fW5FJHA.1280@xxxxxx