Discussion Locked

WinXP SP1 logging into NW4.2 tree

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

Good day all.
I have new workstations that are running the 483SP1 client logging into a tree with two servers. If I log in at location A I get connected to both servers fine. If I log in at location B the logon process hangs for about a minute and eventually comes up with a 1054 error - Server could not be found(this is the server at location A, location B server logs in fine). Both servers are running Netware 4.2. The DNS settings are correct. Last week I used the "reset router" command at location B and it cleared up the issue for about a week. This problem has returned over the weekend. The only major difference between the two servers is that location B has two NIC's.

Any help would be greatly appreciated

7 replies

by pgm554

4.2 does not require DNS,it is an IPX only type of network.So don't even bother (You aren't running NWIP ,are you?)

Make sure that when you install the NW client only IPX is selected as a protocol (custom install).
Having IP as a protocol will confuse the client.It will try a us ip EVEN if ipx is the preferred protocol sometimes.

How the clients find the tree is by a number of methods ,but what happens is that the WS sends out a hello packet and the first server to respond is the login server.If server B has 2 NIC's ,it could be a routing issue.

This could be a RIP/SAP or a DS issue.

Are these servers in the same tree?
Do they each have a copy of the DS replicas?
Are they at the same physical location?

by soulman918

Thanks for the help, I think I found the problem. The main issue was that we were maxing out the licenses on one of the servers. I added licenses and it seems to have cleared up the issue.

by pgm554

4.2 does not require DNS,it is an IPX only type of network.So don't even bother (You aren't running NWIP ,are you?)

Make sure that when you install the NW client only IPX is selected as a protocol (custom install).
Having IP as a protocol will confuse the client.It will try a us ip EVEN if ipx is the preferred protocol sometimes.

How the clients find the tree is by a number of methods ,but what happens is that the WS sends out a hello packet and the first server to respond is the login server.If server B has 2 NIC's ,it could be a routing issue.

This could be a RIP/SAP or a DS issue.

Are these servers in the same tree?
Do they each have a copy of the DS replicas?
Are they at the same physical location?

by pgm554

Make sure you have NMAS on the client install deselected too.It can cause time outs and other issues.

by soulman918

4.2 does not require DNS,it is an IPX only type of network.So don't even bother (You aren't running NWIP ,are you?)

NO I AM NOT

How the clients find the tree is by a number of methods ,but what happens is that the WS sends out a hello packet and the first server to respond is the login server.If server B has 2 NIC's ,it could be a routing issue.

I DON'T THINK THIS IS STRICTLY A ROUTING ISSUE. I HAVE 9X AND OTHER XP MACHINES (PRE SP1) THAT HAVE NO ISSUES LOGGING IN AND CONNECTING TO BOTH SERVERS

This could be a RIP/SAP or a DS issue.

Are these servers in the same tree?
IN SUB TREES AS SHOWN BELOW
|---LOCATION A ---SERVER
MASTER---
|---LOCATION B ---SERVER

Do they each have a copy of the DS replicas?
B IS MASTER, A IS READ/WRITE

Are they at the same physical location?
DIFFERENT BUILDING ON THE SAME LAN SEGMENT

I WILL TRY REINSTALLING CLIENT WITH ONLY IPX THIS TIME.

by soulman918

Does anyone have any advice for troubleshooting router rip/sap? I've been searching online and it's very hard to find...

Thanks,
Soulman

This discussion is closed to new replies.