RRAS issue... I think??

JayrodEFJayrodEF Member Posts: 111 ■□□□□□□□□□
Hey all, i'm in the process of studyingn for the 291. Just got around to really setting up a decent VMware lab and I've hit one little snag. Here's a link to my topology diagram.
http://www.filefactory.com/file/9227f0
The problem I'm having is that no computers except Server02 can access the internet. All the other computers can ping eachother across subnets, name resolution and DHCP addressing seems to be going fine. Whenever I try to ping something on the internet or browse to it on any computer other than server02, I get nothing. I've tried adding a static route on the RRAS server for destination 0.0.0.0.0 netmask 0.0.0.0.0 DG 192.168.0.1 Interface 192.168.0.191. That didn't work. I also tried just bridging all my network connections on Server02, didn't work. Hopefully I've explained it enough so that somebody could make some sense of it? Thanks.

(Sorry the document dowload is such a hassle)

Comments

  • bighornsheepbighornsheep Member Posts: 1,506
    I see that your subnet1 and subnet2 are using DGs of 192.168.1.1 & 192.168.2.1, if you want those subnets to get out to the Internet, you have to make sure you are running NAT in RRAS. Otherwise, set the DG in subnet1 and subnet2 to 192.168.0.1 (cable modem), but I have a feeling that won't be an option because you will need 2 static routes configured on the cable modem as follows:
    192.168.1.0 255.255.255.0 192.168.0.191
    192.168.2.0 255.255.255.0 192.168.0.191
    Jack of all trades, master of none
  • JayrodEFJayrodEF Member Posts: 111 ■□□□□□□□□□
    thanks for the reply. Yeah, I wasn't sure if I'd need NAT on the RRAS server since the physcial router is doing the NAT for the rest of the physical computers I have hooked up to it. But it makes sense when you mentioned that otherwise I'd need static routes in the actual router as well because it wouldn't know the correct ports to send those two subnet addresses. I'll have to try to play around with NAT configuration then later on. Thanks again.
  • JayrodEFJayrodEF Member Posts: 111 ■□□□□□□□□□
    Ok, so I played around with it right now. Definitely an easy fix when you think about it the right way. I think I had been working on it for too long there and I didn't even think about it. I just enabled NAT on the virtual adapter that was bridged to the physical adapter and it pretty much took care of the rest. I can now access the internet from any of the servers as well as the clients. Thanks again!
  • bighornsheepbighornsheep Member Posts: 1,506
    That's great, I've got an exercise for you to try if you're interested.

    Either with vmware/virtual PC or with physical connections, create a seperate domain with outside IP 192.168.0.x with inside subnets 192.168.3.0 and 192.168.4.0, now try to implement routing with RRAS so that every node can connect to every other node including Internet access.

    Hint....you need to play with the outside/inside interfaces for NAT function.
    Jack of all trades, master of none
  • JayrodEFJayrodEF Member Posts: 111 ■□□□□□□□□□
    Sounds like fun, I'll have to give that a shot here. I don' know if I can handle running that many VMs at once, but I'll give it a shot.
  • Tommy_DTommy_D Member Posts: 47 ■■□□□□□□□□
    I have tried that exercise you mentioned but I am getting hung up when I go make my RRAS server (VM running virtual on my laptop, which is wirelessly connected to my home network, to a wireless router running NAT to the outside world) able to see the internet. I have 1 NIC for inernal communication to the VMs, and another NIC set to connect directly to my wireles NIC on my laptop, I guess I am just unsure if it should be to the NIC or shoudl it be NAT in the vitrual PC settings?
  • bighornsheepbighornsheep Member Posts: 1,506
    it wouldn't be NAT to the physical desktop, I would just map the vmnet interfaces to physical interfaces, in this case the wireless adapter.

    I would use vmware virtual machines to represent one domain, create one vm for the DC/RRAS server which maps the physical wireless adapter as the outside interfaces, and then create internal vm interfaces to talk to your other vm machines in the inside network.

    Then use virtual PC to create a seperate domain and essential do the same thing. Now try and get your two domains to talk to each other.
    Jack of all trades, master of none
Sign In or Register to comment.