Networks

Ask something
Discussion Locked

Microsoft client for netware

0 helpful
12 replies

by sandi.deahn

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

I have client for netware installed and everything is fine. I then uninstalled client for netware and rebooted the computer. I was told to put the client back on and I did, but...I now cannot be authenticated, the network path cannot be found. This is on a P2 and I entered in the corect tree and context that was there before. I don't know what more info you may need so I will stop here.
Thanks so much.

12 replies

by oz_media

You mention you installed the "Micosoft" Client for Netware. I am assuming from the Windows Networking interface, REALLY hokey unless running IPX.
Try running the Netware Client from the CD or download the latest client from their website.

by oz_media

NOTE: After installing the 'correct' Netware Client, DO NOT USE WINDOWS UNINSTALLER TO REMOVE IT !!!
If you uninstall the Netware Client without using the "UNC32.exe" from the Novell CD, you will not be able to reboot your PC until booting to Safe Mode and removing it with UNC32. Netware Client is installed with a specific set of drivers that will cause your PC to reboot continuously if not removed properly.

by sandi.deahn

I am not running novell client 32. Just from the properties box service tab in windows NT - added microsoft client for netware. And I removed it from the same place. It removes the bindings and you reboot.

by oz_media

Are you running Netware server? If so, use the right Novell Netware Client from Novell.
MS's Clients don't work worth a damn.

Download the client from Novell at http://tinyurl.com/h9yw

As I mentioned before, if you use the correct client (from Novell) you will not be able to uninstall it through the Add/Remove programs applet. You MUST use the UNC32.EXE provided by Novell. Do you not have the Netware client disks?

by sandi.deahn

I am sorry but I want to use microsoft client for netware. I am not running server. It is just a useres PC. The client worked fine till I removed it and not it doesn't work when I added it back.

by oz_media

Sorry about that then. I just didn't know anyone would want to install a Novell client if not using a Novell server. Especially the wrong client?!?

What protocols are installed?

by sandi.deahn

I misunderstood your last message. Yes I am running novell servers. Sorry about that. On the PC I want "Microsoft client for netware". I have over 300 PCs running it with no problems. But when I remove the client I can not put it back. I get "network path not found" so it can not authenticate me. What does it remove that doesn't get put back?

by oz_media

I haven't used the MS Client for Netware for a couple of years. Novell doesn't recommend using it either. Microsoft just included it for the older NW servers so that it would install an IPX client.
I assume that you are using straight TCP/IP ONLY, ensure that the protocol is installed and that other clients or protocols aren't.

Although you should never compare two pc's, even though they may come from the same manufacturer with the same specs and probably MOST of the software is the same, one working won't mean the other should too.

In your case make sure the protocols listed in the working achines are the same as in a working machine.

Can I ask why you wouldn't want to install the proper client?

by sandi.deahn

I have compaired everything there is to compare in the networking properties and the PC that I am having the trouble with has all the same settings. I can go in and hard map all the drives I want so it is working "kinda". Why we use MS client is because that is what we have always used. The only ones running Novell client32 are network admins.

by oz_media

Well it looks if you're using the MS client to reduce licencing costs for Netware.

Netware turns their nose up at your error (sorry but they do)see:
http://tinyurl.com/hkx4

They say to contact Microsoft or use the correct client for the OS you are using.

It may be due to your servers being updated and the standard MS Client wil not work without these forced client updates.

I fear this thread may drag out as your other unresolved questions have so that's about all I can offer and all the time I can put into this issue.

Good luck, sorry I couldn't offer a more definitive solution.
OM

This discussion is closed to new replies.