Windows 7: Virtual Machines on can't see each other

lilbird1981 · 16 Mar 2010

Hello,

I am just setting up a scenario, which I need for testing.
The scenario requires one Virtual Windows Server 2003 and one Virtual Exchange Server 2007.

I am using Virtual PC 2007 on Windows 7 to set this up.

The win2003 server has internet connection and local connection, so in the settings for this server, I added 2 networking adapters -
adapter 1 - local only
adapter 2 - wireless lan

The exchange server only needs a local connection to the win2003 server, so in the settings of the exchange server I added 1 networking adapter -
adapter 1 - local only

As far as I understood from various tutorials on the internet, the two virtual machines should be on the same local network automatically, however, here are the results when I run "ipconfig" for both machines:

Here are the results for the Server 2003:

Code:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : lan
   IP Address. . . . . . . . . . . . : 192.168.1.70
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Autoconfiguration IP Address. . . : 169.254.142.126
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :

C:\Documents and Settings\Administrator>

The results from the exchange server are:

Code:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 10.0.1.18
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.0.1.1

C:\Documents and Settings\Administrator>

In order for the exchange server to see the server 2003, they should be on the same network, but it appears that they are not. Does anyone know how to set this up correctly?

Thanks,
Lil.

nekkidtruth · 16 Mar 2010

You'll need to change the network adapter settings on the Exchange server to match those of the local adapter settings on 2003 server.

lilbird1981 · 16 Mar 2010

Quote:

You'll need to change the network adapter settings on the Exchange server to match those of the local adapter settings on 2003 server.

Yes, this is what I have done, and now I get the following for the exchange server:

Code:

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 192.168.1.25
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 10.0.1.18
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.0.1.1

C:\Documents and Settings\Administrator>

However, when I ping this now from my server 2003, then I still cannot see it:

Code:

C:\Documents and Settings\Administrator>ping 192.168.1.25

Pinging 192.168.1.25 with 32 bytes of data:

Request timed out.
Request timed out.

Did I misunderstand what you meant?
Thanks,
Lil.

nekkidtruth · 16 Mar 2010

You'll have to bear with me as I've never used an Exchange server. I have however had extensive practice with networking. Your default gateway on the exchange server does not match the gateway of your 2003 server. They're not going to communicate until you've changed that information on the Exchange server.

If you're unsure of how to do that (from what I do understand, it's not the same as regular Windows where you just go into the control panel and right click on the local area connection), you'll have to figure that out.

I did find this tidbit, but I can't guarantee it'll work:

With Netsh.exe, you can easily configure your computer's IP address and other TCP/IP related settings. For example:
The following command configures the interface named Local Area Connection with the static IP address 192.168.0.100, the subnet mask of 255.255.255.0, and a default gateway of 192.168.0.1:

netsh interface ip set address name="Local Area Connection" static 192.168.0.100 255.255.255.0 192.168.0.1 1

The above is one line. So for your settings, it would be:

netsh interface ip set address name="Local Area Connection" static 192.168.1.(any number) 255.255.255.0 192.168.1.254 1

This is of course assuming it's feasible to do this on an Exchange server.

Kari · 16 Mar 2010

Can not add anything to what nekkidtruth already said, just one recommendation: upgrade you Virtual PC! The latest version is especially designed to work with Windows 7, migrating your existing vhd's is easy.

More information and free download: Windows Virtual PC: Home Page

Kari

lilbird1981 · 16 Mar 2010

Thanks Nekkidtruth! However, I do think that they both see the same default gateway. I will paste the ipconfig information here.
This is the one from the Windows Server2003, you can also see that I cannot ping the Exchange server.

Code:

C:\Documents and Settings\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : lan
   IP Address. . . . . . . . . . . . : 192.168.1.72
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 192.168.131.66
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.131.254

C:\Documents and Settings\Administrator>ping 192.168.1.25

Pinging 192.168.1.25 with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.1.25:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

This is the ipconfig information for the exchange server, and you can also see that I can ping the windows server:

Code:

C:\Documents and Settings\Administrator>ipconfig

Windows IP Configuration


Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 192.168.1.25
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 10.0.1.18
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.0.1.1

C:\Documents and Settings\Administrator>ping 192.168.1.72

Pinging 192.168.1.72 with 32 bytes of data:

Reply from 192.168.1.72: bytes=32 time=1ms TTL=128
Reply from 192.168.1.72: bytes=32 time<1ms TTL=128
Reply from 192.168.1.72: bytes=32 time<1ms TTL=128
Reply from 192.168.1.72: bytes=32 time<1ms TTL=128

Ping statistics for 192.168.1.72:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms

So, the default gateway for both my servers is 192.168.1.254, or is this incorrect?
Do you know why in my exchange server I have an IP address of the format 10.0.1.18?

Thanks!
Lil.

lilbird1981 · 16 Mar 2010

@Kari: Unfortunately I cannot upgrade to the latest Virtual PC version, as I am only running Windows 7 Home Premium.

nekkidtruth · 16 Mar 2010

I think part of the issue is confusing the 2 machines. Can you do me a quick favor...

Try posting the 2 like this:

Windows Server 2003:

Code:

Information here

Exchange Server:

Code:

Information here

Just so we're not confusing the 2. Because you've also get more than one adapter I'm starting to get dizzy

lilbird1981 · 16 Mar 2010

OK, let's try it again. Oh, before I post, the reason why I have 2 adapters per VM is because one of them is local and the other is the internet connection. ...or don't I need the local connection.

The scenario I have to produce is:

Windows Exchange Server has a local connection, but no internet connection.
Windows Server 2003 has a local connection (to be able to talk to Exchange Server), and an internet connection.

In the ipconfig of Exchange Server you can now see 2 adapters, because I was told to have the same network adapters on Exchange and the Server, so now the Exchange server also has a local and an internet connection. ...does this make sense? Otherwise, do you know how I can set up this scenario in a better way?

Here is the code again:
Windows Server 2003:

Code:

Windows IP Configuration


Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : lan
   IP Address. . . . . . . . . . . . : 192.168.1.72
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 192.168.131.66
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.131.254

Windows Exchange Server:

Code:

Windows IP Configuration


Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 192.168.1.25
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.254

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   IP Address. . . . . . . . . . . . : 10.0.1.18
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 10.0.1.1

Thanks!
Lil.

nekkidtruth · 16 Mar 2010

On the Exchange server, you only need local connectivity. So remove local area connection. Leave the second one as that has the information you need for the local network. Or transfer the information from LAC2 to LAC and remove LAC2.

The first thing we need to do is get them to communicate with each other.

Windows 7: Virtual Machines on can't see each other

Virtual Machines on can't see each other problems?