General discussion

Locked

Routing and Remote Access

By dominicjohnson83 ·
Hi Guys and Girls,

I really need your help on this question:

I have a Windows 2000 Server with two network cards.

Eth1 - LAN
192.168.0.1
255.255.255.0
GW- 192.168.0.1
DNS 192.168.0.1

Eth2 - Handles Internet connection provided by a ADSL Firewall router.

10.0.0.4
255.0.0.0
10.0.0.1
DNS - some isp address

The Windows box is set as a domain controller, dhcp server, dns server.
Internet browsing is excellent on the server.

My aim is to get access from 192.168.0.10 to 10.0.0.1 to browse the internet without enabling the rediculous internet connection sharing mechanism on my box.

I have tried setting up RRAS (internet connection server - router with NAT routing protocol) and it doesnt seem to work...

Errors when trying to reach www.google.com from client machine (192.168.0.10) with RRAS activated on the server:
request timed out

Cannot ping 10.0.0.1
Can ping 10.0.0.4

When RRAS is turned off i can resolve www.google.com to an IP obviously because of my DNS server (192.168.0.1). and still cant ping...


Setting up internet connection sharing seems to do all weird things to my server such as **** up dns or active directory or dhcp.


In dhcp i have the following scope options -

DNS Server- 192.168.0.1
Router - 10.0.0.4 (i have also tried with 192.168.0.1)

Do you think asking my ISP for a bridged connection to the net may help solve this issue??

any input would be appreciated.. or if you have any furtner questions im more than willing to find out the answers for u.

regards

dom

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Ok - I had the same scenario

by meldrew In reply to Routing and Remote Access

Hi

I had a similar problem
Basically I had 2 2003 DC servers on separate networks but sharing the ADSL connection.

I put an additonal NIC in each server and enabled the Routing and remote access on each one adding NAT. I too was getting inetrnet access on each of the servers altough not on the client machines UNTIL I configured the interfaces into the NAT. This is not done automatically by the wizard and you ahve to add each interface manually.

I hope this helps

Best regards

Meldrew

Collapse -

Just a thought from Network perspective

by yu.chiu In reply to Routing and Remote Access

Wonder if this will work:
1. Is 10.0.0.1 pingable from 192.168.0.1?
2. If so, point GW on ETH1 LAN to 10.0.0.1
3. Perfrom NAT to convert your 192.168.0.0/24 addresses to 10.0.0.0/8 addresses on your ADSL firewall router.
From network point of view, it makes more sense to perfrom NAT on the router than on the server.

Back to IT Employment Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums