Solved

How do I get Virtual session to access both the Internet and local area network at the same time?

Posted on 2008-10-30
5
256 Views
Last Modified: 2013-11-22
While experimenting with MS Virtual PC 2007, I encountered an issue that I've been unable to figure out.  

My attempts to solve it have shown me that I still lack some basic understanding of TCP/IP data communications and the 7 layer OSI model.

I'm hoping that one of you more knowledgeable members of Experts Exchange can help me figure this one out so I can learn how to solve problems of this type in the future.

The problem is that I'm unable to open any website using Internet Explorer from a copy of Windows 2000
running in Virtual PC when the virtual session has been setup to use the (actual) NIC I have installed
in my Windows XP computer.  

The TCP/IP settings in the Virtual PC (Windows 2000) session is using DHCP hosted from my Netgear router.  The "ipconfig /all" shows an IP address has been issued and that an active lease for it is in effect.

I am able to ping the router, my ISP's DNS Server and yahoo.com, but IE is unable to open either the router's administration window or any websites.  The status line at the bottom of IE appears to show the page is being accessed, but IE always times out with "The Page Cannot Be Displayed" message.

However, the Windows 2000 session is able to browse my local area network when running in this mode.

Condition 1:

Here is a copy of the IP configuration and active route list when running Virtual PC using my computer's NIC for the virtual LAN adapter...

  [ Virtual PC 2007 - with NETGEAR WG311v3 802.11g Wireless PCI Adapter ]


C:\>ipconfig /all

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : ga.at.cox.net
        Description . . . . . . . . . . . :               Intel 21140 Based PCI Fast Ethernet Adapter
        Physical Address. . . . . . . . . :          00-03-FF-2F-78-1A
        DHCP Enabled. . . . . . . . . . . :            Yes
        Autoconfiguration Enabled . . . . :     Yes
        IP Address. . . . . . . . . . . . :               192.168.1.106
        Subnet Mask . . . . . . . . . . . :              255.255.255.0
        Default Gateway . . . . . . . . . :           192.168.1.1
        DHCP Server . . . . . . . . . . . :             192.168.1.1
        DNS Servers . . . . . . . . . . . :              68.105.28.11
                                                                   68.105.29.11
                                                                   68.105.28.12

C:\>route print
=============================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2000003 ...00 03 ff 2f 78 1a ...... Intel DC21140 PCI Fast Ethernet Adapter
=============================================================================
=============================================================================
Active Routes:
Network Destination     Netmask               Gateway              Interface           Metric
        0.0.0.0                    0.0.0.0               192.168.1.1      192.168.1.106            1
    127.0.0.0                 255.0.0.0               127.0.0.1             127.0.0.1                1
   192.168.1.0          255.255.255.0        192.168.1.106    192.168.1.106            1
  192.168.1.106       255.255.255.255       127.0.0.1             127.0.0.1                1
  192.168.1.255       255.255.255.255    192.168.1.106    192.168.1.106            1
    224.0.0.0                 224.0.0.0            192.168.1.106    192.168.1.106            1
 255.255.255.255     255.255.255.255   192.168.1.106    192.168.1.106            1

Default Gateway:    192.168.1.1
=============================================================================
Persistent Routes:
  None

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Condition 2:

When I set the Virtual PC's NIC to "Shared Networking (NAT)" mode, I can access websites using Internet Explorer.   However, in this setting my virtual session is running on a different subnet which prevents it from being able to browse my local area network.

Another thing that adds to my confusion is the list of active routes doesn't show any links to my router or the ISP's DNS server.  Dispite this I am able to successfully ping the router and ISP's DNS Server address.

Here is the IP configuration and routes setup in the Windows 2000 session when the Virtual PC NIC is setup in "Shared Networking (NAT)" mode...


  [ Virtual PC 2007 - with Shared Networking (NAT) ]

C:\>ipconfig /all

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : ga.at.cox.net
        Description . . . . . . . . . . . :                Intel 21140 Based PCI Fast Ethernet Adapter
        Physical Address. . . . . . . . . :          00-03-FF-2E-78-1A
        DHCP Enabled. . . . . . . . . . . :            Yes
        Autoconfiguration Enabled . . . . :     Yes
        IP Address. . . . . . . . . . . . :               192.168.131.67
        Subnet Mask . . . . . . . . . . . :             255.255.255.0
        Default Gateway . . . . . . . . . :          192.168.131.254
        DHCP Server . . . . . . . . . . . :            192.168.131.254
        DNS Servers . . . . . . . . . . . :            68.105.28.11
                                                                 68.105.29.11
                                                                 68.105.28.12

C:\>route print
=============================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2000003 ...00 03 ff 2f 78 1a ...... Intel DC21140 PCI Fast Ethernet Adapter
=============================================================================
=============================================================================
Active Routes:
Network Destination       Netmask               Gateway                         Interface           Metric
        0.0.0.0                       0.0.0.0          192.168.131.254            192.168.131.67           1
    127.0.0.0                   255.0.0.0               127.0.0.1                         127.0.0.1               1
 192.168.131.0          255.255.255.0      192.168.131.67              192.168.131.67           1
 192.168.131.67      255.255.255.255        127.0.0.1                         127.0.0.1                1
 192.168.131.255    255.255.255.255    192.168.131.67              192.168.131.67           1
     224.0.0.0                   224.0.0.0         192.168.131.67              192.168.131.67           1
 255.255.255.255    255.255.255.255    192.168.131.67              192.168.131.67           1

Default Gateway:   192.168.131.254
=============================================================================
Persistent Routes:
  None


Any advice or guidence you can offer to help me figure this one out would be greatly appreciated.


Thanks - NetToken

0
Comment
Question by:NetToken
  • 3
  • 2
5 Comments
 

Author Comment

by:NetToken
ID: 22850643

When the Virtual 2007 session is setup using the NETGEAR WG311v3 802.11g Wireless PCI Adapter as the NIC and I then run a VPN connection to a (separate) Windows 2000 server on my network, I am able to access both my local LAN and browse the Internet at the same time.   However, I consider this a to be a sloppy work-around as I shouldn't have to VPN to a computer on my own local network.

Can someone offer a better solution?

Ethernet adapter Local Area Connection 2:

        Connection-specific DNS Suffix  . : ga.at.cox.net
        Description . . . . . . . . . . . :               Intel 21140 Based PCI Fast Ethernet
Adapter #1
        Physical Address. . . . . . . . . : 00-03-FF-2F-78-1A
        DHCP Enabled. . . . . . . . . . . :       Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . :     192.168.1.106
        Subnet Mask . . . . . . . . . . . :   255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DHCP Server . . . . . . . . . . . :    192.168.1.1
        DNS Servers . . . . . . . . . . . :    68.105.28.11
                                                         68.105.29.11
                                                         68.105.28.12
        Lease Obtained. . . . . . . . . . : Friday, October 31, 2008 9:39:10 AM
        Lease Expires . . . . . . . . . . : Saturday, November 01, 2008 9:39:10 AM

PPP adapter 2000-SERVER_VPN:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . :      WAN (PPP/SLIP) Interface
        Physical Address. . . . . . . . . : 00-53-45-00-00-00
        DHCP Enabled. . . . . . . . . . . :   No
        IP Address. . . . . . . . . . . . :      192.168.1.151
        Subnet Mask . . . . . . . . . . . :   255.255.255.255
        Default Gateway . . . . . . . . . :  192.168.1.151
        DNS Servers . . . . . . . . . . . :      68.105.28.11
                                                          192.168.1.200
        Primary WINS Server . . . . . . . : 192.168.1.200
0
 
LVL 77

Accepted Solution

by:
Rob Williams earned 500 total points
ID: 22858481
Though your DNS servers I believe are valid, it may be a DNS issue.
Condition 1 should work fine. Can you try accessing a web page by using the IP address, such as Google: http://64.233.187.99/  If this works it would verify it is a DNS issue and we can then address that.
Condition 2 due to NAT may be, and 3 due to the VPN is using an internal server (host) for DNS.
0
 

Author Closing Comment

by:NetToken
ID: 31511854
That was it!  
I am able to access Google by using their IP address.
Now I've just got to figure out why the virtual PC can't access COX's DNS server even though DHCP is setting up the correct addresses to it.

0
 

Author Comment

by:NetToken
ID: 22859510

Many thanks to RobWill for the correct solution!

In the future I will remember to test DNS by using the website's IP in the IE address line.



0
 
LVL 77

Expert Comment

by:Rob Williams
ID: 22861273
Thanks NetToken.
Try assigning your client machine the server's DNS address not the COX DNS servers. If you have a domain environment this is actually a basic requirement; the server must point only to itself for DNS, the workstations must point only to the server for DNS, and the server should have a forwarder configured to use the ISP's DNS.

For the record there are posts on the Internet where others have had problems from time to time with those DNS servers. Try using 4.2.2.2 and 4.2.2.3 instead of the 68.105.x.x addresses as a test.
Cheers !
--Rob
0

Featured Post

Highfive + Dolby Voice = No More Audio Complaints!

Poor audio quality is one of the top reasons people don’t use video conferencing. Get the crispest, clearest audio powered by Dolby Voice in every meeting. Highfive and Dolby Voice deliver the best video conferencing and audio experience for every meeting and every room.

Join & Write a Comment

PRTG Network Monitor lets you monitor your bandwidth usage, so you know who is using up your bandwidth, and what they're using it for.
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Viewers will learn how to connect to a wireless network using the network security key. They will also learn how to access the IP address and DNS server for connections that must be done manually. After setting up a router, find the network security…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now