Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

No drive letter available after SP6A applied

Status
Not open for further replies.

Conman

IS-IT--Management
Jan 22, 2002
42
IE
Service Pack 6A applied, users can login but no drive letter available. Server available in Nework Neighbourhood but if you try and open any thing it says invalid path.
 
I take it you are referring to NetWare 5.0? Are there any errors on the console referring to the volumes?

If you load NETBASIC or TOOLBOX, can you browse the volumes from the server console? Did LONG.NAM get upgraded as part of the SP? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
Sorry it is NW5, there are no Volume errors, Netbasic allows me to view the contents of the SyS Volume (Only Volume), how do I check if Long.nam was updated?
 
Could you exand on your issue a bit more? What errors are you getting when you log in - be specific in your detail.

By the way, you do have enough free diskspace on SYS? You haven't ran out of diskspace have you? -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
Basically, when you login it accepts my username and password, but it does not map my F:. If I go through Network Neighbourhood I can see SYS vol and all folders, I can open folders and see files etc but I cannot open any files. i.e. if I try and open a word doc it says invalid path. This is the same for all users.

Thanks
 
What version of the Novell Client are you running and on what OS? What default protocol are you using on the client and what protocols is the server setup for?

Also, try the following at the server console and test again:

SET CLIENT FILE CACHING ENABLED = OFF -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
First, check the Rights through NWADMIN32 and the Properties/Trustee Assignments of the Directory and files themselves. Otherwise, you should run a DSREPAIR on your Server. It sounds like the Trustee Assignments have been corrupted somehow. Running DSREPAIR will re-link the Trustee Assignments to what they should be.

Good Luck!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top