Can Login, but no drive mappings allowed

[summoner]

I have a nw 6 server just installed and service pack 3. Client is using 4.83 SP2 on win2k. Connection between them is 100 megabit lan. The server has 2 HDs with the sys volume on a 20 gig ide drive and a data volume on a 73 gig ide drive. Both hooked up to a promise ide card (so i can get ata-100, using ultra.ham driver). One thing I should mention is that the second drive (73) is not an nss volume but remains tradional netware filesystem. I did an upgrade to this server which previously held nw5.1 but left the second HD alone. So only the first volume is NSS. I have installed all the proper licenses on the server (and many are available and unused) but when I go to login I get no drive mapping. No login script yet...logging in as admin...I've verified in console one his right to [Root], new tree so no blocking IRFs. If I manually go to map a drive using client32, the drive will map and the letter will show up...but I cannot access it. This is logged in as admin! I know my files are stil there...in the server gui I can console one down into the file structure on the volumes. I just can't access them from the windows workstation, either of them. This is also a freshly built and patched win2k workstation. I have no idea what I'm doing wrong. The funny thing is that I had this server going with this same exact configuration and I was able to map drives and so were other client PCs...upon re-install, its a no go. I know I must have forgotten to install/configure something...just what??

 

[Provogeek]

In console one or iManager, go to the Server Licnese object and ensure it is associated with your server. I have seen this to be the cause of the issue you describe. In some cases, I have needed to reboot the sever to get it to take the license affter asigning it.

Also, there is a POST SP2 service pack for client 4.83sp2, download it and apply it.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Provogeek
CNE Network+ Experience

Certified nut case

 

[summoner]

I removed IPX from the server and client...forced the client to only use IP to log in. That seems to fix it. I've heard that the client can get confused and try to use both sets of protocols. Anyhow...that seemed to fix it. Thanks...