Client32 3.21 invalid drive mappings

[WayneOrth]

We are pilot testing Client32 V3.21 on Windows 95 PCs that log in to a Netware 5 server running ZENworks for Desktops 2. Sometimes on certain PCs extra drives (as many as 4) will appear in Explorer after a user logs in. These are drive letters that we do not map in a login script, but still they sometimes appear. If you click on the drive, there is nothing in it. If you highlight one of the drives mapped to nothing, you are unable to "unmap it" using either Explorer or the DOS command "map del." Under DOS you receive "MAP-4.13 (970813) PTF-440: The operation was attempted on an invalid drive" when you try to delete the mapping.

Also, you can successfully re-map the invalid drive letter to a folder on a Novell Netware server but not to a Windows NT/2000 server using either Explorer or DOS.

This doesn't happen on every 3.21 client, and doesn't happen at all on our existing 3.02 client.

Any ideas???

 

[yvfwc]

There were several bugs in the 3.2 client hence the sp to 3.21, however some remained. Have you tried 3.3 client? We have been using for several months with no problems. Otherwise the 3.1x client might be a better solution.

Good luck,

Mark ;-)

 

[dan]

Also you might look to be sure you don't have any "saved" Windows drive maps.
(Check explorer for drive letters before logging in)
I agree with Mark that you should try Client 3.3.