Just got a new replacement Dell PC and installed the XP Netware client. I can connect to the server but my F (SYS) drive shows the files on my H (VOL1) drive. I have total access to the server. I am logging in as the same user as before and the user login script has not changed. The system login script has not changed either. The server has NetWare 4.11. Can you suggest a fix for this? Thanks.

Is the F: drive assigned to another device by any chance? Or is Windows just choosing H: as the first network drive? If F: is presently assigned to a physical drive (ie. CDROM, Zip/Jazz, DVD, Flashmedia) then you will have to reserve a different letter to that device using the device manager. If that is not the case, then try going into the (novell) client properties and enabling the "force first network drive" option (I think it's an advanced option). This should force the first mapped drive to F: I hope that helps :)

F drive is not assigned to any physical drive. I checked the Novell client and it is already set to F as the first network drive. The weird thing is that if I map a folder below the root of F, it works. Everything works fine, as is, on my Windows 2000 machine that I am replacing. Any other ideas? This is too weird! Thanks.

Anna, If I understand right, you can map a folder under the SYS volume, that's what you mean by "below the root of F", right? Okay, if that's the case, then the first thing I would verify is that you actually have file permissions to the sys volume. You cannot map a folder to which you do not have browse rights (read, file scan). The fastest way to check this would be to login as someone with NDS & NFS admin rights and see if the F drive maps properly. If it does, then this is a simple permission problem. Remember, having access to the NDS server object is separate from NFS (file system) permissions. Make sure you have the file permissions you need. If this isn't the case, let me know and I'll see if I can think of anything else :( Good luck

I found the answer to my problem. I am logged in with total access to the network so that was not the problem. I found an article that was related (in reverse to my problem) and tried that solution. I went into my own user login script, deleted everything and typed in "NO DEFAULT" (without the quotation marks) and that solved it. Thanks for all your help!