|
|
|
|
||||||
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
This setup is for taking a laptop to client site to demo Outlook/Exchange
functionality Laptop host is running XP Pro, guest is Windows Server 2003 VM. I have loopback adapter that is fixed to 192.169.0.1 and my NIC IP is 192.10.0.116. ICS is enabled on the NIC and I can connect out from guest and connect into guest from host. However, I cannot ping guest from anywhere else on the external network presumably because it's on a different subnet. Is there something I can do on the host to enable me to connect to the guest from machines other than the host? tx |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
Not really. ICS is just a cut-down version of NAT, and that is how NAT
works. It is a one-way address translation. Machines on the private side can see out, but machines on the public side cannot see in. "js" <js@b.com> wrote in message news:OFeefFiaIHA.1208@TK2MSFTNGP05.phx.gbl... > This setup is for taking a laptop to client site to demo Outlook/Exchange > functionality > > Laptop host is running XP Pro, guest is Windows Server 2003 VM. I have > loopback adapter that is fixed to 192.169.0.1 and my NIC IP is > 192.10.0.116. ICS is enabled on the NIC and I can connect out from guest > and connect into guest from host. > > However, I cannot ping guest from anywhere else on the external network > presumably because it's on a different subnet. Is there something I can > do on the host to enable me to connect to the guest from machines other > than the host? > > tx > > |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Bill, Thanks - is there a Virtual Server configuration like the bridged
networking that VMServer uses ? "Bill Grant" <not.available@online> wrote in message news:OxgZa$iaIHA.5208@TK2MSFTNGP04.phx.gbl... > Not really. ICS is just a cut-down version of NAT, and that is how NAT > works. It is a one-way address translation. Machines on the private side > can see out, but machines on the public side cannot see in. > > "js" <js@b.com> wrote in message > news:OFeefFiaIHA.1208@TK2MSFTNGP05.phx.gbl... >> This setup is for taking a laptop to client site to demo Outlook/Exchange >> functionality >> >> Laptop host is running XP Pro, guest is Windows Server 2003 VM. I have >> loopback adapter that is fixed to 192.169.0.1 and my NIC IP is >> 192.10.0.116. ICS is enabled on the NIC and I can connect out from guest >> and connect into guest from host. >> >> However, I cannot ping guest from anywhere else on the external network >> presumably because it's on a different subnet. Is there something I can >> do on the host to enable me to connect to the guest from machines other >> than the host? >> >> tx >> >> > |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
On Fri, 8 Feb 2008 08:12:43 -0800, "js" <js@b.com> wrote:
>Bill, Thanks - is there a Virtual Server configuration like the bridged >networking that VMServer uses ? > Just set the NIC in the guest to point to the physical NIC on the host. Then it will get the same capabilities as the host has. It will act as a second NIC but sharing the same TP cable. Bo Berglund |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
Bo, Thanks - if the guest and the host have the same IP address and I remote
to that IP, which do I hit? Did I misunderstand your advice? "Bo Berglund" <boberglund@home.se> wrote in message news:cmepq355gndesvi79jgnmhteigu6791kim@4ax.com... > On Fri, 8 Feb 2008 08:12:43 -0800, "js" <js@b.com> wrote: > >>Bill, Thanks - is there a Virtual Server configuration like the bridged >>networking that VMServer uses ? >> > > Just set the NIC in the guest to point to the physical NIC on the > host. > Then it will get the same capabilities as the host has. It will act as > a second NIC but sharing the same TP cable. > > > Bo Berglund |
|
|
|
#6 |
|
Messages: n/a
Hébergeur: |
They will not have the same IP address. Each NIC has its own hardware MAC
address and its own IP address, just like multiple machines on the same LAN. "js" <js@b.com> wrote in message news:eWyKKJtaIHA.4144@TK2MSFTNGP05.phx.gbl... > Bo, Thanks - if the guest and the host have the same IP address and I > remote to that IP, which do I hit? Did I misunderstand your advice? > > > "Bo Berglund" <boberglund@home.se> wrote in message > news:cmepq355gndesvi79jgnmhteigu6791kim@4ax.com... >> On Fri, 8 Feb 2008 08:12:43 -0800, "js" <js@b.com> wrote: >> >>>Bill, Thanks - is there a Virtual Server configuration like the bridged >>>networking that VMServer uses ? >>> >> >> Just set the NIC in the guest to point to the physical NIC on the >> host. >> Then it will get the same capabilities as the host has. It will act as >> a second NIC but sharing the same TP cable. >> >> >> Bo Berglund > > |
|
|
|
#7 |
|
Messages: n/a
Hébergeur: |
Sorry if I'm being dim but what does "point the NIC on the guest to the
physical NIC on the host" mean? "Bill Grant" <not.available@online> wrote in message news:uotV7BuaIHA.1188@TK2MSFTNGP04.phx.gbl... > They will not have the same IP address. Each NIC has its own hardware MAC > address and its own IP address, just like multiple machines on the same > LAN. > > "js" <js@b.com> wrote in message > news:eWyKKJtaIHA.4144@TK2MSFTNGP05.phx.gbl... >> Bo, Thanks - if the guest and the host have the same IP address and I >> remote to that IP, which do I hit? Did I misunderstand your advice? >> >> >> "Bo Berglund" <boberglund@home.se> wrote in message >> news:cmepq355gndesvi79jgnmhteigu6791kim@4ax.com... >>> On Fri, 8 Feb 2008 08:12:43 -0800, "js" <js@b.com> wrote: >>> >>>>Bill, Thanks - is there a Virtual Server configuration like the bridged >>>>networking that VMServer uses ? >>>> >>> >>> Just set the NIC in the guest to point to the physical NIC on the >>> host. >>> Then it will get the same capabilities as the host has. It will act as >>> a second NIC but sharing the same TP cable. >>> >>> >>> Bo Berglund >> >> > |
|
|
|
#8 |
|
Messages: n/a
Hébergeur: |
On Fri, 8 Feb 2008 22:05:08 -0800, "js" <js@b.com> wrote:
>Sorry if I'm being dim but what does "point the NIC on the guest to the >physical NIC on the host" mean? > 1) Inside the VPC2007 console, select the thumbnail image that represents your guest machine. 2) Click the Settings button with the guest shut down 3) Click the networking item in the list to the left 4) For Adapter 1 to the right drop down the combobox 5) In this box there should be at least 4 items: Not Connected Local only <The name of your network card in the host> Shared networking (NAT) 6) Of these you select the name of your host NIC 7) Click the OK button and start the guest machine Now VirtualPC will use the Virtual Machine Network Service on the host to create a new "logical" network card using the hardware of the host network card but with a different MAC address. This new NIC (different from the host logical NIC) will appear on your external network and when the operating system starts it will have the IP address you define inside the guest operating system. If you have set the guest NIC for "Automatically get IP address" then it will ask for a DHCP server on the *external* network and get its address from that server. It will be a different IP address from the one your host has because these are different network cards (different MAC addresses). Now you have two compters on the external network (host and guest) and they can communicate exactly the same so they will be able both to go to the Internet and talk to each other. Notice that the presence of an external network router with a DHCP server is needed for this. But that is what most people have these days (the ADSL/DSL modem/router box usually has a DHCP server so you can connect multiple PC:s to the same internet connection). If you connect the Internet directly to your PC then you need to get a hardware router to put in between the Internet and your host PC. Bo Berglund |
|
|
|
#9 |
|
Messages: n/a
Hébergeur: |
Bo,
Thank you so much for the detailed explanation. Very generous of you. "Bo Berglund" <boberglund@home.se> wrote in message news:qflqq3948s7i0vgcqquc4ulqn0smi00kda@4ax.com... > On Fri, 8 Feb 2008 22:05:08 -0800, "js" <js@b.com> wrote: > >>Sorry if I'm being dim but what does "point the NIC on the guest to the >>physical NIC on the host" mean? >> > > 1) Inside the VPC2007 console, select the thumbnail image that > represents your guest machine. > > 2) Click the Settings button with the guest shut down > > 3) Click the networking item in the list to the left > > 4) For Adapter 1 to the right drop down the combobox > > 5) In this box there should be at least 4 items: > Not Connected > Local only > <The name of your network card in the host> > Shared networking (NAT) > > 6) Of these you select the name of your host NIC > > 7) Click the OK button and start the guest machine > > Now VirtualPC will use the Virtual Machine Network Service on the host > to create a new "logical" network card using the hardware of the host > network card but with a different MAC address. > This new NIC (different from the host logical NIC) will appear on your > external network and when the operating system starts it will have the > IP address you define inside the guest operating system. > > If you have set the guest NIC for "Automatically get IP address" then > it will ask for a DHCP server on the *external* network and get its > address from that server. It will be a different IP address from the > one your host has because these are different network cards (different > MAC addresses). > Now you have two compters on the external network (host and guest) and > they can communicate exactly the same so they will be able both to go > to the Internet and talk to each other. > > Notice that the presence of an external network router with a DHCP > server is needed for this. But that is what most people have these > days (the ADSL/DSL modem/router box usually has a DHCP server so you > can connect multiple PC:s to the same internet connection). > If you connect the Internet directly to your PC then you need to get a > hardware router to put in between the Internet and your host PC. > > > Bo Berglund |
|
![]() |
| Outils de la discussion | |
|
|