asked on

Question about Shares and expected behavior on a 2003 server

Is it normall on a windows 2003 server to see diisk letters externally mapped to shares using credentials other than that of the currently logged in server to show up as" disconnected Network drives" that do have no access to them. First is this normal? Shouldn't the administrator of the machine have access to the share connections? If not please explain this further. I am now under the impression such behavior would be normal even logged in as the server local Administrator. Please not the Shares I have been speaking about were created by a service running as SYSTEM. Also:
When I go to the CMD.EXE prompt and type NET USE nothing lists even though there is a mapped drive connection to an external server that is being used

Robert Silver

ASKER

Here is what the explorer window looked from the User's Login:
See the image at:

http://profile.imageshack.us/user/rss0245/images/detail/#176/sharetroubleeb2.png

Note the drives listed as Disconnected are really connected with other credentials:
when double clicked the entries display:
X: \ is not accessable
Logon Failure Unknown user name or bad password

where X are any of the drive letters with

Phadke_hemant

have you tried disconnecting the drives and reconnecting? if not, just try it.
It may also happen if you don't have access rights to those drives, just check the share permissions for those folders

ASKER CERTIFIED SOLUTION

SunKnight0

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Robert Silver

ASKER

In the end I have to critique Microsoft. As Administrator of the domain and / or machine you would hope Microsoft would have the good sense to show all net use share connections established on the PC and given access to Administrators within the machine makiing connection. Why wouldn't they. Obviously this was not handled well because it causes some rather nasty problems.