locked
Cannot connect to the Internet RRS feed

  • Question

  • Hello,

    I am setting up the virtual Hyper-V test network on Windows Server 2008 R2.  I created two different LANs   10.0.10.0/24 and 10.0.20.0/24.  I setup virtual RRAS server and I have connection between those two LANs. 

    Everything looks good, so I decided to connect the RRAS server to the Internet.  It already had the Network card and IP address of the LAN assigned to that card.

    Not sure what is going on, but there is a problem with this setup.  I can connect to the Internet from the RRAS server, but I cannot run Windows updates.  It gives me 80072EE2 error.  The virutal server on my test LANs (10.0.10.0/24 and 10.0.20.0/24) cannot connect to the Internet or to any computers on my LAN. From those test LANs, I can ping the LAN interface of the RRAS server, but I cannot ping anything that is connected to that interface on my real LAN.

    Any ideas what the problem could be? I hope I was able to explain my setup.

    Thank you.


    Thank you. Eric.

    Sunday, August 19, 2012 12:17 AM

Answers

  • Hi Eric,

    It sounds to me like there is a route missing from the LAN (outside interface of your RAS server) to 10.0.10.0/24 and 10.0.20.0/24.

    Take an example address on one of those networks like 10.0.10.4. You didn't give the subnet of the outside LAN but let's pretend that it is 192.168.0.0/24 and the RRAS server has an interface at 192.168.0.1 and also an interface on the 10.0.10.0/24 network at 10.0.10.1.

    Let's also assume that the default route for the computer at 10.0.10.4 is the RRAS server at 10.0.10.1.

    If you ping from 10.0.10.4 to 192.168.0.1, the default route says to send the packet to 10.0.10.1. The RRAS server gets the packet and knows where 192.168.0.1 is because it has this address as a directly connected interface, so it replies. It can reply to the 10.0.10.0/24 network because it is directly connected to that network too.

    If you ping from 10.0.10.4 to a different computer on the 192.168.0.0/24 network, such as 192.168.0.6 this doesn't work because the computer at 192.168.0.6 doesn't know how to get to the 10.0.10.0/24 network. It isn't directly connected, and the default route for this computer probably sends packets out to the Internet. The packet arrives at this computer just fine because the RRAS server knows how to get it there, but the computer needs to send a reply back to 10.0.10.4 and it doesn't have a clue where to send this.

    Anyway, this is just a guess. It will help to know the routing tables and the other subnet address.

    -Greg

    • Marked as answer by KPABA Sunday, August 19, 2012 1:39 PM
    Sunday, August 19, 2012 11:57 AM

All replies

  • Hi Eric,

    It sounds to me like there is a route missing from the LAN (outside interface of your RAS server) to 10.0.10.0/24 and 10.0.20.0/24.

    Take an example address on one of those networks like 10.0.10.4. You didn't give the subnet of the outside LAN but let's pretend that it is 192.168.0.0/24 and the RRAS server has an interface at 192.168.0.1 and also an interface on the 10.0.10.0/24 network at 10.0.10.1.

    Let's also assume that the default route for the computer at 10.0.10.4 is the RRAS server at 10.0.10.1.

    If you ping from 10.0.10.4 to 192.168.0.1, the default route says to send the packet to 10.0.10.1. The RRAS server gets the packet and knows where 192.168.0.1 is because it has this address as a directly connected interface, so it replies. It can reply to the 10.0.10.0/24 network because it is directly connected to that network too.

    If you ping from 10.0.10.4 to a different computer on the 192.168.0.0/24 network, such as 192.168.0.6 this doesn't work because the computer at 192.168.0.6 doesn't know how to get to the 10.0.10.0/24 network. It isn't directly connected, and the default route for this computer probably sends packets out to the Internet. The packet arrives at this computer just fine because the RRAS server knows how to get it there, but the computer needs to send a reply back to 10.0.10.4 and it doesn't have a clue where to send this.

    Anyway, this is just a guess. It will help to know the routing tables and the other subnet address.

    -Greg

    • Marked as answer by KPABA Sunday, August 19, 2012 1:39 PM
    Sunday, August 19, 2012 11:57 AM
  • You could be right, but I am not sure where on my LAN (outside interface of my RAS server) can I set it up.  This is my home network.  I do not have DNS server.  I use Linksys E1000 and I do not think that I can set it up on this router.

    Any ideas?

    Thank you.


    Thank you. Eric.

    Sunday, August 19, 2012 1:27 PM
  • You were right.  That was the problem.  I found how to set it up on the router and everything works. Well, almost everything.  Windows update does not work but this is another question.

    Thank you for your reply.


    Thank you. Eric.

    Sunday, August 19, 2012 1:39 PM