Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NT 4 Routing Issue through T1

Status
Not open for further replies.

KenIT

IS-IT--Management
Feb 20, 2002
16
US
Ok guys I will try to be brief with the explanation. Here is the setup:
Location A: Running a Frame Relay Netopia router (1) with IP Scheme assigned with static Ips to systems of 192.168.1.xxx
That router is connected to another Netopia router (2) with internal address of same scheme for connection to location A's network.
Location B: I have another Netopia router (3) loop and tied into router (2) at location a via a PTP T1. This router is using the scheme 192.168.2.xxx.

Now in testing the connection I have been able to ping other machines across the T1. Example: Machine A (192.168.2.75) can ping 192.168.1.2 and I can attempt to connect to it but cannot authenticate because it says no domain controller is present to do so.

Attempting to ping the PDC (NT 4.0) I get request timed out (PDC being 192.168.1.xx) but pinging a Windows 2k server set up as a MS with ip in the same range works fine. This issue is only happening when I ping NT 4 server. I am not running WINS ... is there another service I should be concerned with. Any suggestions would be appreciated.
 
Pinging by IP address does not require any other service to be running. Try pinging other machines from the NT4 server.
Also double check your network settings, NIC settings, and network cable on the server.
 
Thanks for the help, but we got it figured out. We were also running dual NICS in the system for something we thought we were going to do in the future. We were curious as if it was necessary to run another service for router to router communication on the NT 4.0 based server but we compared it to others we have and narrowed the answer to no. The second NIC, though not connected, but set with an IP was causing the issue. It was broadcasting quite a bit so I removed the card and problem solved. Thanks for the response.
 
Just FYI from your comment "I am not running WINS" from the description of your Network "WAN" Wins was made for! it will do Net Bios Name resolution and decrease broadcast congestion by resolving any registered computer and allow directed broadcast. Responsiveness from computers on other sub-nets will be much improved. It does lots of registration types PDC, BDC among others that will preserve bandwidth by reducing broadcast traffic.

Steve Bowman
steve.bowman@ultraex.com

 
Thanks Steve. I decided after we got the other problem solved to go ahead and use WINS because of an issue we were having with browsing the network from the second subnet. After we took the second card out of the PDC we could ping all machines but still could not browse the network. That was when the decision to install WINS was made. Any other suggestions would be greatly appreciated. Thanks for the help. Thank you both.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top