LAN Routing

[rosscopt]

Hi,

hopefully someone can help me with this request, I can't take some days off until I fix it!

Basically, I have just installed a wireless link between 2 buildings so that the remote office can access our LAN. There's something screwy happening with routing on the switches I think as the connection drops off now and again.

My Intention is to install a 2003 server with 2 nics, 1 on the office LAN - 192.128.10.255 and the other on the remote office LAN - 192.168.0.255 and use the server as a router.

The server is up and connected to both LAN's, I just can't reach one from the other. I've installed the routing and remote access bit and tried adding static routes but I must be doing something wrong. Can someone point me in the right direction?

The IP config for the 2 nics are:

LAN - IP 192.128.10.9
SM 255.255.255.0
GW 192.128.10.254

REMOTE LAN - IP 192.168.0.250
SM 255.255.255.0
GW 192.168.0.254

I'd like to get this up and running so that I can make the server a DC for the main LAN and have workstation validate logons against it, instead of going over the wireless link etc.

Any help would be appreciated!

Thanks

Rossco

 

[pagy]

I don't think you should need the gateway address on the remote lan NIC, if that nic is directly attached to 192.168.0. network you should not need a gateway setting.

Also were both nics installed and configured with IPs when you enabled RRAS?


All you need in this life is ignorance and confidence; then success is sure.
- Mark Twain

 

[rosscopt]

The 192.168.0 interface is connected to a switch on the lan in the remote office. The 192.128.10 interface is connected to a wireless access point which provides the connection to the main office lan.

RRAS can see both interfaces.

Curiously, I can RDP to the server from both lan's. When I connect to it on the 192.128.10.9 address, I can ping addresses on the 192.168.0 subnet but not addresses on the 192.128.10 subnet, other than the wireless access point.

 

[pagy]

To make sure I have this right;
from 192.168.10.0 you can't ping anything on 192.168.0.0 and vice versa.
Whats the IP settings on the workstastions? Ip addr, GW etc.

From a pc on 192.168.0.0, for arguments sake 192.168.0.10 run a tracert to 192.168.10.9 and see where it fails.


All you need in this life is ignorance and confidence; then success is sure.
- Mark Twain

 

[rosscopt]

When I logon to the server I can ping both the 192.128.10 and 192.168.0 subnets.

When I logon to a machine on either subnet, I can't ping the other.

It just seems that the link between the 2 is missing?

 

[pagy]

Whats the default gateway set to on the machines in both subnets?



All you need in this life is ignorance and confidence; then success is sure.
- Mark Twain

 

[rosscopt]

I set the default gateway to the IP of the server interface on that subnet.

 

[pagy]

if you run a tracert from a pc where does it fail?


All you need in this life is ignorance and confidence; then success is sure.
- Mark Twain

 

[rosscopt]

Sorry for the late reply!

I've got it working, but by using Linux!

Thanks for all the help though.