Discussion Locked

windows 2000 w/novell client ip only

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am in a 2000 user environment that is soon going to windows 2000 pro. We are primarily a Novell shop and we have the novel 4.8 client ready for win2k pro. installing novell client ip only is causing a problem with some users who are losing network connectivity when they dial up an outside resource that is needed for there job function. I would like to know if anyone knows of a way to keep network connectivity on the Lan while also being able to use a modem to connect to another companies resource.

6 replies

by tony.colgrove

It sounds like a routing issue. Most likely the default routes are being changed to the dialup connection, and since the other company doesn't have a route back to your internal lan, the data gets lost.
You probably want to build a little route script that runs after dial-up completes. This should set the default routes back to your network and only leave a route to the company network throught the dial-up adapter.

by drdon

A portion of this issue is the difference between Novell and MS' implementation of the IP protocol. If I am reading this right, when the user dials in with the Novell Client installed, you should be getting an error they cannot agree on Protocol error I believe it is 702 is that right? If so, you will also need to install the Novell Dial Up adapter portion of the 4.8 client. IP will bind to it and you should be able then to connect to a remote NT or 2000 computer.

by chris.grider

Let me clarify... that the users are already connected to the LAN using novell IP only (no ipx)(we use netware 5)... then they need to access a banking resource by dialup and still have access to the LAN... when they dial up the outside resource the lose LAN connectivity... I appreciate the input anything further would be helpfull.

This discussion is closed to new replies.