Re: Windows 2K3 and Virtual Server 2005 guests NAT problem

On Apr 24, 1:23 pm, "Bill Grant" <not.available@online> wrote:
"Ace Fekay [MVP]" <PleaseAs...@xxxxxxxxxxxxxx> wrote in messagenews:%23xCWT7ihHHA.4588@xxxxxxxxxxxxxxxxxxxxxxx

Innews:1177348459.319478.301190@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
lazyll...@xxxxxxxxx <lazyll...@xxxxxxxxx> typed:
Hi everyone,
I am forced to post on not finding a suitable applicable solution from
the various permutations of the same issue.
we are developing some test applications on guest machines that run on
Virtual Server. However, these machines are not able to connect to our
corporate LAN. I had enabled the Loopback adapter to form a virtual
internal network.

The server is essentially connected to a 'public' network and a
private network.

Server --> NIC1 --> (LAN)
--> NIC2(LoopbackAdapter) --> Guest OS

Notes :
1. The client is able to ping the internal address of the server
"192.168.1.55" ..
2. Pinging any external address, or name resolution does not happen on
the client.
3. The NAT/Firewall setting on the server is configured to provide
both DHCP and DNS. But only DHCP seems to be working.

Configurations on the server side (fake ip's)
---------------------------------:

Ethernet adapter "Corporate LAN"

Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection #2
Physical Address. . . . . . . . . : 00-43-12-D6-2E-4F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 62.186.122.103
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 62.96.122.4
DHCP Server . . . . . . . . . . . : 62.96.193.4
DNS Servers . . . . . . . . . . . : 62.96.192.44
62.96.192.4
Primary WINS Server . . . . . . . : 62.96.192.4

Ethernet adapter "MS Loopback Adapter" :

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.55
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Configurations received on the client side (through DHCP from RRAS)
---------------------------------:

Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network
Connection #2
Physical Address. . . . . . . . . : 00-03-FF-D6-2E-4F
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 62.186.122.103
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 192.168.1.55
DHCP Server . . . . . . . . . . . : 192.168.1.55
DNS Servers . . . . . . . . . . . : 192.168.1.55
Primary WINS Server . . . . . . . :

Can you give me any clues as to how I can get the client to connect to
ip addresses on the corporate LAN ?

Regards,
CP

I don't think you will get the loopback adapter to work in such a
configuration. That was designed to provide network connectivity for
testing if you do not have a physical NIC. Therefore I do not think it
will work this way. Matter of fact this is the first time I've ever heard
of such a scenario with it. IF you get it to work, I would be interested
in seeing the actual configuration and what your settings are.

Nonetheless, I would just put everything on the actual physical NICs in
each VM properties. If you want to have the two or three VMs on a private
192.168.1.x network, you will have to pick one of the VMs to be your NAT
device. All the other VMs will use this guy as their gateway.

If you can't get NAT to work and only DHCP works, NAT is probably
conflicting with the ICS service, and if that is not on, then I would
imagine RRAS is not setup correctly, but then again, that could be the VM
properties for NAT conflicting, and can be the root of the whole problem.

Also ensure that eacy VM NIC has a unique MAC.

--
Regards,
Ace

Innovative IT Concepts, Inc (IITCI)
Willow Grove, PA

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Instead of the website you're using, try using OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. Anonymous access. It's free - no username or password
required nor do you need a Newsgroup Usenet account with your ISP. It
connects directly to the Microsoft Public Newsgroups. OEx allows you
o easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject. It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

"Quitting smoking is easy. I've done it a thousand times." - Mark Twain

It will work OK like that, Ace. The loopback network is just a virtual
network which can access the host machine through the host's loopback
adapter. If you put the private LAN on an internal virtual network you have
to run the router on a virtual machine (with one NIC in the virtual network
and one linked to the physical network) If you use the loopback adapter you
can route through the host machine.

Back to the OP. I presume you want to give the private LAN access to the
public LAN without changing the routing on the public network? The best way
to do that is to set up the machine as a NAT router in RRAS (with the 62.
NIC as the public interface and the loopback adapter as the private
interface). However it won't work with the config you have given in DHCP.
The vms must use private IPs from the 192.168.1.0/24 subnet. eg

Public network
|
62.186.122.103 dg 62.96.122.4
host RRAS/NAT
192.1681.55/24 dg blank
|
guests
192.168.1.x/24 dg 192.168.1.55

If you have configured DNS on the host and have set your vms to use this
DNS you will need to set it up to forward to to your 62.96 DNS server(s) if
you want these machines to be able to resolve names of the LAN machines. You
will also need to set them up with the correct DNS suffix if you want them
to resolve these names using simple names, not FQDNs. I would just give the
machines in the private LAN the DNS addresses of your 62.96 DNS servers from
DHCP, but give them 192.168.1.x IP addresses and 192.168.1.55 as default
gateway address..

Thanks for the inputs !
I just realized that i had made a terrible mistake in posting the
guest side configuration, while copying it.
Bill, the set up was working exactly as you mentioned, with the guests
nicely getting a 192.168.1.x/24 address from the DHCP set up on RRAS.
Forgetting the DNS part for now, i was not able to get even a ping
response from the external ip addresses i had tried.
Somehow, the gateway "192.168.1.55" was not routing the requests to
the external network.

One more troubleshooting tip is that from the host machine command
prompt, i am not able to ping the internal 192.168.1.x/24 address of
the host either.

Any clues as to why this would happen ?

Thanks again ..

.

Relevant Pages

  • Re: Windows 2K3 and Virtual Server 2005 guests NAT problem
    ... these machines are not able to connect to our ... internal network. ... Ethernet adapter "MS Loopback Adapter": ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.networking)
  • Re: [opensuse] Have a separate resolv.conf per interface
    ... I'm at a client and need to be on their network to access their ... but I want to be able to resolve machine names on their ... Can you not then specify just the DNS of the client? ... Their DNS boxes only serve to resolve names for internally hosted machines. ...
    (SuSE)
  • Re: Big problem....Big Question
    ... One primary difference is that in going into the DNS Server settings on ... > the machines that work and those that don't. ... Cannot login to the Network Domain after having added the ...
    (microsoft.public.win2000.dns)
  • Re: Not connecting to Domain
    ... The machines are all running windows XP Professional with service pack 2. ... The odd thing is this has suddenly happened on two machines in a network of 30, with no other PCs reporting the same problem. ... is your DNS configured properly? ...
    (microsoft.public.windowsxp.network_web)
  • Re: DNS on multihomed server
    ... > is connected to public network and other is on private ... > public network but not the private. ... Through DNS ... > to the private network for security reasons. ...
    (microsoft.public.windows.server.dns)