Announcement

Collapse
No announcement yet.

Windows 2003 RRAs routing setup in VMWare test lab

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Windows 2003 RRAs routing setup in VMWare test lab

    I have done this before but for whatever reason cannot get it to work now. I have one Windows 2003 Server setup as DHCP and RRAS, multihomed. One network interface is for my lab subnet and the other is for my home network subnet. I went through the wizard and set up for LAN routing and the Firewall. No matter what I do I cannot ping from inside my lab subnet to the outside world or my home network subnet nor can IE open anything (thought maybe ICMP was blocked at first). I don't remember having to set any routes up for this to work but I tried some static routes to no avail. If anyone has some time to take me through some systematic troubleshooting I would greatly appreciate it. I do not play with RRAS much, just need it to work. Thank you in advance.

    Eric

  • #2
    Re: Windows 2003 RRAs routing setup in VMWare test lab

    Shouldn't need static routes in 2003, unlike 2008. LAN routing should be all you need to get this working. On the "external" NIC (to your home network) you should have a static IP, Subnet Mask and Default Gateway configured. On the "internal" NIC (to the test network) you should have a static IP, Subnet Mask and DNS Servers configured but no Default Gateway.

    If you can, post an ipconfig /all and Route Print from the RRAS server.
    BSc, MCSA: Server 2008, MCSE, MCSA: Messaging, MCTS
    sigpic
    Cruachan's Blog

    Comment


    • #3
      Re: Windows 2003 RRAs routing setup in VMWare test lab

      Windows IP Configuration

      Host Name . . . . . . . . . . . . : RRAS
      Primary Dns Suffix . . . . . . . : Tester.local
      Node Type . . . . . . . . . . . . : Unknown
      IP Routing Enabled. . . . . . . . : Yes
      WINS Proxy Enabled. . . . . . . . : No
      DNS Suffix Search List. . . . . . : Tester.local

      Ethernet adapter ExternalSub:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
      Physical Address. . . . . . . . . : 00-0C-29-BF-CC-5B
      DHCP Enabled. . . . . . . . . . . : No
      IP Address. . . . . . . . . . . . : 192.168.1.26
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . : 192.168.1.1
      DNS Servers . . . . . . . . . . . : 4.2.2.1

      Ethernet adapter InternalSub:

      Connection-specific DNS Suffix . :
      Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection #2
      Physical Address. . . . . . . . . : 00-0C-29-BF-CC-65
      DHCP Enabled. . . . . . . . . . . : No
      IP Address. . . . . . . . . . . . : 192.168.140.40
      Subnet Mask . . . . . . . . . . . : 255.255.255.0
      Default Gateway . . . . . . . . . :
      DNS Servers . . . . . . . . . . . : 192.168.140.30





      IPv4 Route Table
      ================================================== =========================
      Interface List
      0x1 ........................... MS TCP Loopback interface
      0x10003 ...00 0c 29 bf cc 5b ...... Intel(R) PRO/1000 MT Network Connection
      0x10004 ...00 0c 29 bf cc 65 ...... Intel(R) PRO/1000 MT Network Connection #2
      ================================================== =========================
      ================================================== =========================
      Active Routes:
      Network Destination Netmask Gateway Interface Metric
      0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.26 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.26 192.168.1.26 10
      192.168.1.26 255.255.255.255 127.0.0.1 127.0.0.1 10
      192.168.1.255 255.255.255.255 192.168.1.26 192.168.1.26 10
      192.168.140.0 255.255.255.0 192.168.140.40 192.168.140.40 10
      192.168.140.40 255.255.255.255 127.0.0.1 127.0.0.1 10
      192.168.140.255 255.255.255.255 192.168.140.40 192.168.140.40 10
      224.0.0.0 240.0.0.0 192.168.1.26 192.168.1.26 10
      224.0.0.0 240.0.0.0 192.168.140.40 192.168.140.40 10
      255.255.255.255 255.255.255.255 192.168.1.26 192.168.1.26 1
      255.255.255.255 255.255.255.255 192.168.140.40 192.168.140.40 1
      Default Gateway: 192.168.1.1
      ================================================== =========================
      Persistent Routes:
      None




      On my home network side I only have my Linksys router configured as a gateway - just started to wonder if I had set up RRAS to use NAT instead of acting like a router. Should I need a second router in my home network for this RRAS setup to work - starting to think I do. But then again, I would think a ping reply would go back to the IP address the echo was received from and then the RRAS would route the response to the right computer in my lab network.

      Thanks for your thoughts, this one is stumping me.

      Eric

      Comment

      Working...
      X