General discussion

Locked

Connecting to a NT network with ISDN

By steve_a_nelson ·
I am trying to connect a peer-to-peer network at a remote location to a Windows NT network using 2 3Com ISDN Lanmodems. I can get the modems connected but am unable to talk with computers at the other location (I've tried from both sides). The ISDN service is for a private network only and doesn't connect to an ISP for internet service. According to 3Com support, I had to set each site up in it s own subnet (192.168.104.xx for the NT side and 192.168.100.xx on the peer side)As far as Windows settings, 3Com advised to set the default gateway and DNS server to the address of the LANmodems and have the workstation names and IP addresses listed in the LANModems. I have tried that and had no luck. The subnet masks for the computers and LANModems on both sides is 255.255.255.0 which is how 3Com said to set them up. Any help would be great.

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Connecting to a NT network with ISDN

by steve_a_nelson In reply to Connecting to a NT networ ...

I can be reached at steve_a_nelson@hotmail.com
My settings were off and doesn't list the author.

Collapse -

Connecting to a NT network with ISDN

by Some Guy in Seattle In reply to Connecting to a NT networ ...

Basic checks:

Can you ping your local gateway (ISDN lanmodem) from your PC? If so, can you ping the far gateway on the remote side (other landmodem)? If so, can you ping a remote machine on that network? This will determine that traffic is up and flowing in both directions. Any problems, check the IP setup of the machine in question.

Once that is determined, then figure out how you are accessing machines on the other side. If you are trying to get to them via DNS, make sure the lanmodem is set up with the DNS entries of the machines that need to be accessed. Since this is a private LAN you can set up the DNS entries any way you want. 3Com might recommend that users of this product for Internet access use the lanmodem as their DNS server but this is generally for people that want to resolve public websites and have access to the public root DNS servers. If this is strictly internal and private you will need to make sure the DNS service on the lanmodem is updated with whatever machines you want to resolve. If this *IS* strictly internal and the LAN is small enough, you might want to go with host and lmhost files on your PCs instead or configure the lanmodems to forward NetBIOS broadcasts across for name resolution.
Hope that helps -

Collapse -

Connecting to a NT network with ISDN

by steve_a_nelson In reply to Connecting to a NT networ ...

The question was auto-closed by TechRepublic

Collapse -

Connecting to a NT network with ISDN

by mattd In reply to Connecting to a NT networ ...

Hi Steve,
I agree with the first answer, but there's a couple of other points...I'm not particularly familiar with your routers, but there are some basic principles that can be applied to all IP routers in this scenario: Each router needs a route specified, so that it knows what to do with packets destined for the remote network.So on Cisco's you would have a route on one router that reads: (on the 192.198.100 network) ip route 192.168.104.0 255.255.255.0 (isdn iterface address) - this last address is the IP of the ISDN interface that dials the other network.Once you have this on each router, you should be able to ping machines across the link. Don't bother trying to see machines in network neighborhood until you can ping across this link. Once you can do this, you're almost done. For name resolution, I would recommend you configure WINS on the NT server,(I take it there is one?) with static mappings for each machine on the peer-to-peer lan, then have the peer-to-peer clients use theIP of the NT server for WINS. This is really easy to manage, and much better than hosts or lmhosts files on all the PC's.(less running around to manage them!) Once you can ping netbios machine names, not IP's, you should be able to see everything innetwork neighborhood. Hope that helps :-)

Collapse -

Connecting to a NT network with ISDN

by steve_a_nelson In reply to Connecting to a NT networ ...

The question was auto-closed by TechRepublic

Collapse -

Connecting to a NT network with ISDN

by steve_a_nelson In reply to Connecting to a NT networ ...

This question was auto closed due to inactivity

Back to Windows Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums