Hi,
I have set up a virtual server to use as a test server and a loopback
adapter is installed on the host machine. I can see the server whne using an
ip range which is used on our intranet.

As we have limitations on how many IPadresses we have, is it possible to use
a 192.168 address for the Virtual server and port forward to the Virtual
server through the Phsical Servers IP in a similar way to how VMWare allows
you to do this. e.g. have a server with dhcp 192.168.xxx address be accessed
by clients on intranet or is the only way to do this to use IP's in our
intranets range e.g. 10.xxx.xxx.xxx

I don't know how vmware handles it, but I always run the vms in a
different IP subnet from the host's.

You don't need to rely on anything in Virtual Server to handle that. You
do it using RRAS, either on the host or in a vm.

"kurtz" <kurtz@discussions.microsoft.com> wrote in message
news:3C520710-DB9C-4016-8473-B286C0F8211E@microsoft.com...
> Hi,
> I have set up a virtual server to use as a test server and a loopback
> adapter is installed on the host machine. I can see the server whne using
> an
> ip range which is used on our intranet.
>
> As we have limitations on how many IPadresses we have, is it possible to
> use
> a 192.168 address for the Virtual server and port forward to the Virtual
> server through the Phsical Servers IP in a similar way to how VMWare
> allows
> you to do this. e.g. have a server with dhcp 192.168.xxx address be
> accessed
> by clients on intranet or is the only way to do this to use IP's in our
> intranets range e.g. 10.xxx.xxx.xxx

Is it possible to have an ip on the Virtual machine as a diffrerent range
from your network and have the Virtual machine still visible to your network,
e.g. have clients connect to it.

In Vmware you can use 192.168.xx for the machine and the host machine
passess any traffic to this on specified ports directly to the correct
virtual machine ?

"Bill Grant" wrote:

> I don't know how vmware handles it, but I always run the vms in a
> different IP subnet from the host's.
>
> You don't need to rely on anything in Virtual Server to handle that. You
> do it using RRAS, either on the host or in a vm.
>
> "kurtz" <kurtz@discussions.microsoft.com> wrote in message
> news:3C520710-DB9C-4016-8473-B286C0F8211E@microsoft.com...
> > Hi,
> > I have set up a virtual server to use as a test server and a loopback
> > adapter is installed on the host machine. I can see the server whne using
> > an
> > ip range which is used on our intranet.
> >
> > As we have limitations on how many IPadresses we have, is it possible to
> > use
> > a 192.168 address for the Virtual server and port forward to the Virtual
> > server through the Phsical Servers IP in a similar way to how VMWare
> > allows
> > you to do this. e.g. have a server with dhcp 192.168.xxx address be
> > accessed
> > by clients on intranet or is the only way to do this to use IP's in our
> > intranets range e.g. 10.xxx.xxx.xxx
>
>

In VMware you can use a 192.168 address range which are locally generated by
the VMwAre dhcp and still have the server visible over the network and have
network users connect to it. This uses port forwarding so that the clients
try to connect to the hosts IP e.g. sql or http/https which then forwards
the traffic to the appropiate VMware machine. You can set what traffic goes
to which virtual machine, but you cannot forward a traffic to more than one
machine, e.g. http to 2 machines, etc.
This does not require the use of adresses from the phyical networks range to
be used up and is good for when IP addresses are limited.

The only way I can get clients, from the physical network, to connect to the
Virtual Server is to use up one of our subnets IPs which are limited, using
192.168 will not work as there does not appear to be any way to port forward
traffic to them.

Is there any way that clients can connect to the Vrtual machine without
using up one of the networks range of ip's ?

"Bill Grant" wrote:

> I don't know how vmware handles it, but I always run the vms in a
> different IP subnet from the host's.
>
> You don't need to rely on anything in Virtual Server to handle that. You
> do it using RRAS, either on the host or in a vm.
>
> "kurtz" <kurtz@discussions.microsoft.com> wrote in message
> news:3C520710-DB9C-4016-8473-B286C0F8211E@microsoft.com...
> > Hi,
> > I have set up a virtual server to use as a test server and a loopback
> > adapter is installed on the host machine. I can see the server whne using
> > an
> > ip range which is used on our intranet.
> >
> > As we have limitations on how many IPadresses we have, is it possible to
> > use
> > a 192.168 address for the Virtual server and port forward to the Virtual
> > server through the Phsical Servers IP in a similar way to how VMWare
> > allows
> > you to do this. e.g. have a server with dhcp 192.168.xxx address be
> > accessed
> > by clients on intranet or is the only way to do this to use IP's in our
> > intranets range e.g. 10.xxx.xxx.xxx
>
>

On Thu, 14 Feb 2008 04:23:00 -0800, kurtz
<kurtz@discussions.microsoft.com> wrote:

>In VMware you can use a 192.168 address range which are locally generated by
>the VMwAre dhcp and still have the server visible over the network and have
>network users connect to it. This uses port forwarding so that the clients
>try to connect to the hosts IP e.g. sql or http/https which then forwards
>the traffic to the appropiate VMware machine. You can set what traffic goes
>to which virtual machine, but you cannot forward a traffic to more than one
>machine, e.g. http to 2 machines, etc.
>This does not require the use of adresses from the phyical networks range to
>be used up and is good for when IP addresses are limited.
>
>The only way I can get clients, from the physical network, to connect to the
>Virtual Server is to use up one of our subnets IPs which are limited, using
>192.168 will not work as there does not appear to be any way to port forward
>traffic to them.
>
>Is there any way that clients can connect to the Vrtual machine without
>using up one of the networks range of ip's ?
>

There's nothing built into VS, but Windows server OSes have everything
you need.
Here's a how-to for VS2005:
http://blogs.msdn.com/virtual_pc_guy...04/477195.aspx

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