Networks

Ask something
Discussion Locked

WinXP SP1 cannot find Novell server

0 helpful
9 replies

by oldmansax

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have one Netware 5.1 & one Netware 6 file server on seperate networks. Both have only WinXP machines connected to them with no problems for about a year. I recently deployed 1 new machine in each network, using WinXP SP1 OS. I installed Novell XP Client V 4.831 on both. Both machines see & log on to their respective servers the first time I boot up. Once I log off, neither will see the server again. Both see the other Windows machines on the networks with no problems. The only differences in old & new machines is the old have XP Pro WITHOUT SP1 (it is installed later as an update) & the new have XP Pro WITH SP1. I have tried the windows client and the Novell V4.83 client with the same results. Anyone have any ideas?

9 replies

by gr8dane

When you say they can't see the server after you logged off the first time, what exactly do you mean? Are you trying to browse to the server before loggin in? If so, have you removed the Public's right to browse the tree? Many people, like me, have removed Public's right to browse the tree, which makes the server transparent to a non-authenticated user. You can still map to the server using the server name, and you can manually type in the context and server in the advanced options of the client login screen to log into the server instead of browsing to it. Not sure if this is what you meant, but I hope it helps.

by oldmansax

I mean the very first time after I install the novell client, I can browse for the tree, context, & server, "see" them all, & log into the server. Once I log out the first time, although the tree, context & server are still in the client logon window, I cannot log on to the server. Message is "tree not found, do you still want to log on to windows". If I completely uninstall the client, reboot the machine, log on to windows, log off, reboot the machine, reinstall the Novell client, I can browsefor the tree, ect. again & log onto the server. Once I log off, "the tree is not found" again. It's really weird. & it's on both unrelated network. I am going to try formating the harddrive & installing the WinXP Pro wihout SP1 & see what happens.

by budthegrey

This kinda sounds like a protocol issue (your environment will prefer that you install the client with "IP only")

However, I had a couple WinXP machines that displayed other "little mysteries" with SP1 applied; we later decided not to roll it out. Can you un-install SP1, install the client, then apply SP1?

by oldmansax

I hate to rate this "unacceptable" because it helped to know there are others who are having problems with SP1 besides me; however, I would like to leave the question open & this is the only choice to do that. I can't uninstall SP1 as it is includedin the WinXP CD. I am looking for an older copy of Win XP to try your approch. Thanks!

by tommymcbrayer

Sounds like a browsing issue. When the Novell client login screen comes up can you click the advanced tab and browse to the tree and servers. I had the same issue on NT 4.0 workstations. I would configure and load slpda on both servers. Should already be done on the netware 6 server. Netware 6 is slpda dependent. If you are still having login issues you can set a static da in the service location in the netware client properties. Let me know if you need more info.

TL McBrayer CNE6,CNE5, CCNA, CXE

by oldmansax

As an update, I found a copy of Win XP without SP1, did a clean install, & installed the Novell 4.83 Client. I have had no problems since then with either machine on either network. They both found their respective servers & logged every time with no problems. I admit you are over my head with the static da. The WinXP SP1 seems to be the problem. Have you had any conflics between SP1 & Novell?

by borrim

We have had the same type of problem here. We've found that even though Novell says that updating your nwhosts file with all ip addressing/nds name resolves this, it does not. If you put the IP address itself in the login box, you will be able to login. Otherwise, making sure that SLP is up and running is supposed to fix this issue.

by oldmansax

Update: I have had this same problem with three other machines in two other networks;but even putting the IP address in the login window didn't help. I have since gotten later versions of WinXP Pro w/SP1 & had no problems. Evidently this was a problem with the first versions of WinXP Pro W/SP1. I guess it's business as usual at Micro$oft! Thanks to all who answered this question

This discussion is closed to new replies.