General discussion

Locked

Win2K3 Server drive letter namespaces

By jsb_el ·
Have run into a problem. Upgrading a server from Win2K Std to Win2K3 Enterprise (DB server - needs more RAM), and batch jobs which rely on network shares are failing due to the security model of the Win2K3 Drive letter NameSpaces.

The jobs see the drive letters (proven by examining WMI's Win32_LogicalDisk), but can not access the contents of the network shares (all network shares show as 'unavailable').

Both machines are using local accounts - same username/passwords.

This configuration worked fine under Win2K, but this does not work under Win2K3. We've narrowed this down to drive letter namespaces - the shares that are set up under the individual accounts on the Win2K3 box are not retained between sessions like they were with Win2K.

We're looking for a quick, cross the board fix to this problem such that it can be maintained at the server admin level, rather than at the individual job level.

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by wcp In reply to Win2K3 Server drive lette ...

Change the drive letters from Disk Management to the way they were assigned in Win 2K.

Your problem was most likely due to the drive letters got reassigned after upgrading Win 2K to Win 2K3.
This happens when the HD was partitioned after the Win 2K installation. The second partition might have been assigned to E (C the first partition and D the CD-ROM, for example). Upgrading to Win 2K3 might reassign the second partition to D and the CD-ROM to E.

Collapse -

by jsb_el In reply to

This concerns network shares - local drives are unaffected.

Shares exist on the remote Win2K server, and have not been modified. Access to them is not being permitted on the Win2K3 server (where the batch jobs are running) since the upgrade.

The batch environment knows about the drives (checked via walking the WMI logical drive list) however accessing the drives is being blocked somewhere. "Net Use" shows the drives as "unavailable".

From the administrator account, we can disconnect and reconnect the drive, and it is accessible - but only within the confines of the session - once the session is ended and a new one is started, the drive is unaccessible again.

Back to Windows Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums