Phandalyon
Guest
- Joined
- Jun 12, 2001
- Messages
- 5,839
I am having some trouble with mapped drives on a network I am working on. The network consists of one Dell Server running Windows 2000 Server and 4 Dell workstations running Windows 2000 Professional. The problem is with only one of the workstations. Here it is:
The software they are using requires them to have a drive mapped on the computer. Specifically it has to be mapped as T drive. The problem is that immediately after I map a drive on this PC, it shows up in My computer as disconnected with the red X through it. I can open the drive and save/edit/open files without any issue. If I do a net use t: at the command prompt it tells me the drive is disconnected.
This is not a problem in Windows, but in the software they are using the error "This drive name is already in use" cones up every time they have to access the T: drive. They are then able to proceed with their work, but every time they access the drive it gives that error, which is very annoying. I am going to go back and take a look at it again tomorrow or monday and I am just dead out of ideas.
I tried rebooting the server and the workstation
I turned off the timeout on the mapped drives (on both computers just to be safe)
Tried mapping to an IP address instead of a name
Tried mapping a different directory
All of these have succeeded in the red X reappearing every time.
There is one other catch I should mention. If I disconnect the drive (either in My Computer or through the net command at the command prompt) and then reconnect the drive, it will show connected. I can access the drive all I want at the command prompt changing back and forth, copying files, etc.... The problem comes in when I go into my Computer and access the T: drive. The first time I access it it stays connected, but if I close the drive or hit the back button and then reopen the drive it instantly shows disconnected.
So [H] networkers, any sound advice for me? Did I miss something stupid?
Thanks for the help.
The software they are using requires them to have a drive mapped on the computer. Specifically it has to be mapped as T drive. The problem is that immediately after I map a drive on this PC, it shows up in My computer as disconnected with the red X through it. I can open the drive and save/edit/open files without any issue. If I do a net use t: at the command prompt it tells me the drive is disconnected.
This is not a problem in Windows, but in the software they are using the error "This drive name is already in use" cones up every time they have to access the T: drive. They are then able to proceed with their work, but every time they access the drive it gives that error, which is very annoying. I am going to go back and take a look at it again tomorrow or monday and I am just dead out of ideas.
I tried rebooting the server and the workstation
I turned off the timeout on the mapped drives (on both computers just to be safe)
Tried mapping to an IP address instead of a name
Tried mapping a different directory
All of these have succeeded in the red X reappearing every time.
There is one other catch I should mention. If I disconnect the drive (either in My Computer or through the net command at the command prompt) and then reconnect the drive, it will show connected. I can access the drive all I want at the command prompt changing back and forth, copying files, etc.... The problem comes in when I go into my Computer and access the T: drive. The first time I access it it stays connected, but if I close the drive or hit the back button and then reopen the drive it instantly shows disconnected.
So [H] networkers, any sound advice for me? Did I miss something stupid?
Thanks for the help.