Windows 2000 RRAS/VPN help needed

[Zipster]

Hi,

I have recently set-up a remote office for our windows 2000 native network across a WAN (DSL) with the same ISP and firewall as the main office. I have created a new site, DC, and subnet within our domain

ONLY from each RRAS server can I ping and browse the network, but I would also like the clients behind these RAS servers to be able to see each network too.

I can allow this manually by doing route add from each client, but is their a way of allowing each client on the network to do this automatically when logged on? The default gateway of each client is the same as the RRAS server.

Here's a bit more info about the network:

Main Office:

192.168.10.0/255.255.255.0 IP Range

The main server has DNS (using port forwarding to our ISP),DHCP,RRAS configured on it with ip 192.168.10.191

I added a static route to the RRAS configuration to 192.168.100.0 (remote office IP range), and the remote office dials in to this machine.

15 Clients

Remote Office:

192.168.100.0/255.255.255.0 IP Range (all static)

Main server has just RRAS and gets the remote office IP via the dhcp server at the main office, and I've configured the DNS server on the network adapter to 192.68.10.191 (the main office dns). I added a static Route to the main office of 192.168.10.0

Is this best practise? Or should I be configuring an additional DNS and DHCP configuration at the remote office?

So if anyone can help here's the conclusion:

How do I get clients on both networks to see both networks

http://www.k.abbott.btinternet.co.uk/

 

[AV1611]

Demand Dial Routing and make them both a part of the others AD in Domains and Trust.

AV

 

[jgoodman00]

Not sure if I understand this right, but are you saying you have a single DNS server, located at the main office?
This being so, you will be generating a lot of name-resolution traffic across the WAN link, as all requests will be sent to it.

So, I would personally add another DNS server in the remote location (to enable local name resolution), & create a single forward & reverse lookup zone on each dns server, both AD integrated.

Personally, I would switch the remote clients to DHCP, & allow them to dynamically update the DNS. You should be able to do this with either a DHCP relay agent at the remote office, or another DHCP server at the remote office. Because you say there are only 15 clients at the remote office, I would be tempted to go with a single DHCP server, & a DHCP relay agent. I would then create a single Superscope, which has two scopes within it, one for each subnet.


Can clients ping by ip-address across the WAN?

James Goodman MCP

http://www.james-goodman.co.uk