PHWinfo - Afficher un message - Networking with Virtual Servers

14/02/2008, 19h48

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.

14/02/2008, 19h48	#5
Steve Jain Messages: n/a Hébergeur:	Re: Networking with Virtual Servers - IP Addresses 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.