NIR_030: Windows to NT Networking

Written by: Christopher Bradley and Jayson Sakata Date: 9/18/97
Revised by: Alisa Walker Date: 3/2/00

Connecting a Windows Machine to a remote Windows NT Network via 2 Netopia Routers

Problem:

How does one connect a Windows machine to a remote Windows NT network using IP such that you can browse computers in the Domain of the remote Network Neighborhood?

Notice:

This document is provided to you as an added service by Netopia Technical Support. Although the configurations described below have proven successful in many instances for doing Microsoft Networking across a WAN or VPN connection, we cannot guarantee success in all circumstances due to the many variables and unpredictable behavior common to Windows OS. If the following suggestions do not provide the results you desire, please contact your MIS Department, or Microsoft Technical Support directly as Netopia cannot further support the features of Windows OS.

Parameters:

To complete this technote we used the following equipment:
Hardware Firmware/Version Installed Options
2 Netopia Routers 3.1.3 or later none
1 Windows 9X Machine none
1 Windows NT Machine 4.0 Service Pack 3 or higher

Network Configuration:

Background:

The key to browsing the remote network is that the Windows NT Server needs to be running WINS Services and acting as a Primary Domain Controller (PDC). See below for more information on how to set up WINS Services. If this is not possible refer to technote NIR_028: Windows Peer to Peer Networking, and treat the NT Server as if it were a Windows machine. This technote assumes that you have TCP/IP set up on your Windows machine. If you do not, please refer to technote NQG_100: Configuration of Windows 9X TCP/IP Properties. Do not continue until you have consulted the technote and have a connection established.

Configuration:

Both Netopia Routers are running firmware 3.1.3 or later and are routing IP only. The NT Server is running version 4.0 with Service Pack 3 or higher installed. The following is a list of the basic steps necessary for most (not all) systems to access remote networks.

Windows NT Configuration:
  1. Open Network setup in the NT Control Panel.
  2. Click on the Services tab and select Add Service.
  3. Select Windows Internet Name Service.
  4. Restart Windows NT.

Windows Configuration:

  1. Open the Control Panel and select Network.
  2. Click on the Identification tab.
  3. Enter a unique Computer name.
  4. Enter the Workgroup/Domain name of the Windows NT Server (PDC).
  5. Enter a unique Computer description.
  6. Click the Configuration tab.
  7. Select the TCP/IP component from the list that appears in the configuration window. Then select Properties.
  8. Click on the WINS configuration tab in the Properties window.
  9. Select Enable WINS resolution.
  10. For Primary WINS Server, enter the IP address of the Windows NT Server running WINS.
  11. For Secondary WINS Server, enter the same address.
  12. Click OK and restart Windows.

At this point, once the connection has been made you will be able to browse the Network Neighborhood and see all the computers in the remote Workgroup/Domain. However, this configuration will only facilitate full network browsing in the direction of the host network to NT server's network. It does not facilitate full network browsing in the opposite direction. In other words, considering the above example network configuration, the network of 192.168.3.0 will be able to browse the network of 192.168.1.0, but the 192.168.1.0 network will not be able to browse the 192.168.3.0 network. To locate a Windows machine on the 192.168.3.0 network from a Windows machine on the NT Server's network of 192.168.1.0, you must use the Find | Computer option of your Start Menu to search for that particular computer.

Alternatively, if you have Windows NT Servers on both networks, you can achieve full browsing in both directions if you have WINS running on both servers and configure them as Replication (or Push/Pull) Partners.

Windows NT Replication Partner Configuration:

  1. Open the WINS Manager in the Administrative Tools
  2. Highlight your local WINS server and go to Server, then Replication Partners.
  3. Click Add.
  4. Type in the IP Address of the remote WINS server and click OK.
  5. To configure the interval at which you would like these two WINS servers to replicate entries, go to Options, then Preferences.
  6. Click Partners.
  7. Type in a start time and select an interval.
  8. Click OK.
  9. Repeat on remote NT Server.
Summary:

If you have an NT Server running WINS, operating as a Primary Domain Controller (PDC), and configured as a Replication Partner, you can facilitate full network browsing over the WAN or VPN connection. If you only have an NT Server on one side of the connection, you can only facilitate full browsing in one direction (host network to server's network). Without an NT Server running WINS on a network, the network cannot be browsed from a remote network. The alternative would be to configure an LM host file, and use the Find | Computer option from your Start Menu. For more information, see technote NIR_028: Windows Peer to Peer Networking.

NIR_030.pdf (Formatted in PDF for printing)


[an error occurred while processing this directive]