7 replies
by chris Accepted solution
by Former member Accepted solution
Or it might have failed so put in a new drive.
Please post back if you have any more problems or questions.
by chris Accepted solution
by Former member Accepted solution
If the drive is not lit then go into the storage management section and see if the hard drive is mounted and healthy, you might need to give it a letter or format it (if it is not formatted).
If they are hot swap drives then you will need to switch the drive on at the front end where you place the drive in.
Please post back if you have any more problems or questions.
by 1bn0 Accepted solution
Accessing network drives implies, remotely from a workstatation?
What OS is on the workstation?
When attempting to access network shares via UNC (\\servername\sharename) if you do not have authorisation to access the shares Windows XP (don't know about Vista) will prompt for a username and password. If the authentaication fails, windows maintains the connection state even though you cannot access the share. When you try to connect or map the share, you get an error because the "connectin" already exists.
Open explorer. Click on Tools | Disconnect Network Drive. If the share is displayed in the box , then this is what has happeded.
Disconnect the useless share. Verify your access credentials and re-establish the connection.
I get this all of the time here at work. (help desk remote technical support)
by chris Accepted solution
We are using XP Professional. The system accepted our username and passwords, but would not allow us access because we lost power. All users are mapped to shareable drives on the server, in addition to personal mapping to private drives, which they use to keep certain data off the server.
Thanks for your help.
by 1bn0 Accepted solution
"The system accepted our username and passwords, but would not allow us access"
1. Are you authenticating to the domain when you log on?
Try using a user account that has not been logged on at a workstation (no cached credentials) or create a new AD User account on the server and use it to log in to the workstation for testing.
2. If your are properly logging on to AD but cannot connect to the share then it would appear the share/file permissions have changed or become corrupted.
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending