Windows Forum

Ask something
Discussion Locked

Windows 2000 Routing and Remote Access

0 helpful
10 replies

by oridjinn 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a Domain Controller, we will call it DC1 at Main Site Location. I also have a VPN server set up with Routing and Remote access at the Main Site Location. Main site IP address config is 10.200.120.0 with Subnet of 255.255.255.0. I have successfully set up the VPN to accept incoming connections and to allow for external connections. I have also set up DHCP for this server to assign IP addresses correctly. At the remote site, I have a Domain Controller that we will call DC2. DC2 is configured as a Routing and Remote access server as well with the IP address schema 10.200.121.0 with subnet 255.255.254.0. After setting up a persistent connection on both ends, I am able to connect to the VPN server at the main site, but the main site cannot connect to me. I have also correctly configure routing and can successfully ping the IP address of DC1 from DC2. I can also successfully replicate changes from the two DC's and they are both set up as seperate sites. My problem is that
1. I cannot ping DC1 from any computer other than DC2 at the remote site.
2. I cannot connect the VPN server back to DC2 using a persisten connection, therefore,
I cannot route back to DC2 even from the VPN server using ping.

I need to find out what I am doing wrong in this situation where it wont allow me to ping DC1 from any computer on the network with DC2 at the remote site and why I can't get VPN server to connect with DC2 and route back. I am making this question worth alot of points since it is very important to me.

10 replies

by oridjinn

Additional information that I have left out...

I have tried changing the IP address scheme at remote location to 10.200.121.0 with subnet 255.255.255.0 and also tried 10.200.130.0 with 255.255.255.0 to see if this would help.

by gregory w. smith

1. I cannot ping DC1 from any computer other than DC2 at the remote site.

Is that ping "by name" or "by IP address". If it's by name, then it would appear to be a name resolution issue, possibly solvable by LMHOSTS files on the servers and WINS for the rest of the machines. Or, since it's 2000, DNS replication (I'm not very familiar with it, though)

2. I cannot connect the VPN server back to DC2 using a persistent connection, therefore,
I cannot route back to DC2 even from the VPN server using ping.

You only need to establish a single connection (persistent is fine) from one end. If DC2 can ping DC1, then DC1 can route packets to DC2 in your current config, else the ping would never return.

Email or post for additional help.

by oridjinn

1. I can ping by name and by ip address from DC2 to DC1, but not from any of the PC's on the LAN connected to DC2.

2. I have one persistent connection, which is fine for the replication between DC2 and DC1, but for some reason, I cannot ping DC2 from the VPN Server

by gregory w. smith

My next speculation is that "Main Site" already has a default gateway for traffic, (maybe an Internet connection) thus sending packets to the default gateway instead of to the remote subnet.

A secondary default gateway *could* do this, or you could add routes at the existing default gateway or at the workstations (if NT/2000 workstations, anyway)

by oridjinn

I am still having some problems, but I was able to successfully set up and ping from my workstation to the remote server by adding the local VPN server as a router. I also enabled NAT to help a little, and there is also a registry value (IPEnableRouter) under TCP/IP that you have to set the value to 1 to enable IP routing. Imagine that?

This discussion is closed to new replies.