Quantcast
Channel: Network Infrastructure Servers forum
Viewing all articles
Browse latest Browse all 5877

RRAS/PPPoE difficulties

$
0
0

I'm doing ad-hoc IT support for a small local nonprofit.  They have Verizon DSL, with a Westell 6100F modem.  Modem is connected to NIC 1 on DC running 2008 r2, NIC 2 is connected to LAN (switch) and doing DNS/DHCP.  

Previously,  RRAS was set up and working fine - NIC 1 had a DHCP address of 192.168.1.49, NIC 2 was 10.0.0.75 - modem in standard "routing" mode, but everyone was able to access the internet.  DHCP set to assign router as 10.0.0.75, same address for DNS.

Then... they decided they want VPN capability.  I found instructions online to change 6100 to "bridge" mode - disable RRAS, re-enable with wizard, select VPN & NAT option.  Nothing works.  Do some Google-ing, change NIC 1 to have static IP of 192.168.1.25 (arbitrary but in same subnet of modem/router), add Demand Dial connection to RRAS (including PPPoE credentials), with a static route of IP: 0.0.0.0 / subnet: 0.0.0.0 / Metric: 1.

After that... DC has Internet access, clients do not, but I CAN VPN to the server from WAN.  Further Google-ing yields: Add ISP DNS IP's as Forwarders to DNS server; now clients can resolve host names (i.e., ping shows IP of google.com, but get "request timed out"), but still can't open websites.

Many more rounds of Google-ing: add another static route under RRAS of 10.0.0.0/255.255.255.0.  After that, client PC's can't even ping server.  Remove it, and back to resolving host names, but nothing else.

Tried a few other things I found on message boards, like changing eDNS.  I even re-ran the RRAS wizard to only do NAT routing, no VPN, with the same results.  

Any insight will be hugely appreciated!


Viewing all articles
Browse latest Browse all 5877

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>