Windows Forum

Ask something
Discussion Locked

Routed network with remote sites

0 helpful
7 replies

by edudley

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

We are currently setting up a routed network over frame relay. We have three sites in different states. The NT 4.0 sp6 servers and internet connection all reside at the home office. The other two sites just have clients.
The frame relay is up and the routers have been configured by our vendor, but the remote clients can not see the network at the home site.
I have setup DHCP so that each site has it's own IP address set. The router at each location is the clients default gateway.
When they boot up they get a message that the domain is not available and they do not recieve any dhcp information.
I can manually input the ip address on the clients and put add the remote routers in the routing tables of the email and application server and that allows the remote client to communicate with them but they still don't log into the domain.
Is there something else in NT that I need to setup or what should I look for in the router configuration?
On the router Bootp forwarding has been enabled but All subnet broadcasting and IP and UDP broadcast forwarding has been disabled.
What else should I look for?

7 replies

by nettek

You don't mention WINs. In order to resolve names to IP addresses across routers, your clients need to know the address of your WINs server. If you do not have a WINs server on your network, you will need to use LMHOSTS files on your clients located at the remote sites.

As far as DHCP is concerned, when your clients request an IP address from a DHCP server, these broadcasts by default do not cross routers. However, if you are running NT Workstation, you can enable 1, and only 1, workstation at the remote site as a DHCP relay agent. The relay agent will intercept broadcast requests to the DHCP server that are coming from the clients, convert them to IP, and send them across the router to the DHCP server. Be aware that you of course need this workstation to be up and running at all times, and it will consume some of the workstations resources.

by Former member

You say you have enabled bootp forwarding, and yet have DHCP at each site? This is sort of redundant. You need to troubleshooting using simple IP techniques. If you can ping the servers and such using their IP addresses, you should then attempt to ping using their names (netbios names). I would suggest that as answer 1 stated, you need to enable WINS at the server site, and then be sure your workstations are P-node or Hybrid node WINS clients, which you can set in your DHCP configuration. If you already have a WINS server, then check your DHCP scope properties and be sure it has a WINS entry and node type.

by maz1980

1. To make your client get their IP address trough DHCP, you must install DHCP relay agent on each new subnet gateway.
2. Make a new BDC-of existing domain-in new subnet. You may also make new domain on the new subnet then set the trust relationship between PDCs.
3. Install at least a WINS server so that client names on different network can be resolved.

This discussion is closed to new replies.