Discussion Locked

Novell Netware 6 + new XP workstation = no drive mapping

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

Hello all.

First I want to admit that I am very new to Novell. I inherited a very neglected Novell 6 server that has two workstations attached: one is running Windows 98 and the other is running Windows 2000. Both use IPX protocol and login via Novell client version 4.9. There is the admin user, two regular users, and another I just added, for a grand total of 4 users.

(Also, the server COULD BE version 5.6 -- I saw an entry in ConsoleOne about it being version 6 and another that said 5.6! -- HOW CONFUSING!)

The whole little system is backed-up with a natural gas generator and it all pretty much runs always. One of those clients has been up now for 786 hours. The other for 340 hours.

But anyway, the PROBLEM:

The other day, I was nonchalantly given the task of adding a 3rd workstation (and hence, a 3rd regular user). I put it together and attached it to the network via network cable. The new workstation runs Windows XP Professional. I downloaded the latest Novell client for XP from the Novell official site.. Something like 4.9 sp4... (don't have that info in front of me at the moment)

I installed the client and got it to log-in to the network. I can browse the eDirectory server (named FS1:) and even execute nwadmin32.exe from it.

But I cannot map any drives. And the login script that executes for all users fails to map the drives also. It produces error 8901.

However, if I login to the new XP workstation with one of the old, existing users that's been configured since the beginning of time, it works perfectly. The only problem is with the new user I created. I have not tested to see how the new user acts on one of the older, existing, working workstations. Those are mission critical and any downtime is automatically a crisis for the management, haha.

Using nwadmin32.exe, I have compared my new user (called 'central3'), to my other 2 users (called 'central1' and 'central2') and it appears EVERYTHING is identical -- user rights, trustees, etc. Everything I can find seems appropriately set to mimmick the other 2 users.

But on the new XP workstation, my new user (central3), and also the admin account both fail to map the drives and mapping isn't possible manually once logged in. It complains that the "network path cannot be found", even though I can easily browse with Windows Explorer to the very folder I want to map! Novell Map Network drive doesn't work, nor does the regular windows mapping.

Any ideas here? Does the server restrict based on workstation? That can't be it.. old users work perfectly on the new workstation.

I don't think this is a licensing issue because management swears it's "probably licensed for atleast 5 users", but I don't even know how to confirm this. What is the easiest way to find out how many users the network is licensed to support?

Sorry for the dumb questions, this is the first I have dealt with Netware and so I am beginning a long road of discovery here. Any help would be much appreciated!

Kevin

1 reply

by vacuole

Haha, just a few hours after I wrote that long-winded message, I figured it out.

Turns out, it was a licensing issue.

Even though we have a 5 user license, we had never actually loaded the license key onto the server.. so we had been usign the licensed server without any licensed users. Novell allows a licensed server to service two user connections simultaneously if there are no user license keys present.

I simply put the disk in and loaded the key, and all is well.

The weird part is that, instead of popping-up with a big error message in giant letters about maybe something like "INSUFFICIENT LICENSE", it just quietly did weird things, like not allowing drive mapping.

Very strange stuff.

In any case, I'm glad that's behind me.

This discussion is closed to new replies.