Mapped drives in Win2K

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Recently, I had a Win2003 SBS running a small domain. I had to reformat the
server and install Win2K server instead and did not setup the domain. I left
the network as a workgroup. On all my workstations i disconnected the
previous mapped drives to the old domain controller and re-mapped the same
drive letters to the new Win2K server in the new workgroup. My Windows 2000
desktops now always show a red X on the mappings even though i can always
connect to them. My XP desktops had no problems and do not show the red x's
Any ideas?
Is there something that needs to be deleted or re-configured on the Win2K
desktops? On the previous mappings, one drive was assigned through the login
script and the other was just a simple mapping

Any help would be great!!
 
My guess is that the red "X" goes away for
a while each time you connect to the drive, then
reppears after a while. No?

Open a CMD prompt on the server and enter the
command: "net config server /disconnect:-1".

See if that helps.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.
 
Hello and thanks for the advice.
However it didn't fix my problem.

What i did notice was that when the Win2K desktop logs in the drives show up
without any red X's. But as soon as i access one of the mapped drives, all
the mapped drives get marked with a red X even though i can still access all
of them, then the red x's stay on the mapped drives until i log off then back
in. Even then, as soon as i access any of them, they all get marked with the
X.
Weird problem, but at least my users can still access thier files, the
problem with this is whenever they try to save a file or backup something to
one of the drives marked with the red X they get an error saying "cannot
connect to the drive". Even though if i drop out to the desktop i can access
the drive no problem.

Any other recommendations?
 
I agree this is strange.

Can you try a "non-persistent" mapping? When you do the "net use," add the
switch: "/persistent:no" . This creates the mapping only while the user is logged
in -- the system doesn't "remember" it, so it needs to be in a startup batch file
to be run each time they log in.

This will sometimes correct that problem -- the Win2K machines are on SP4, yes?

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.
 
ugh, sorry no luck on this one either. and yes running SP4.
starts out good at initial login, but as soon as i access the mapped drive
it get marked with the red x.
Going nuts at this point....i may bite the bullet and just reformat and
upgrade to XP..just hard to justify a reformat for something like this...

any other last ditch efforts?
thx!
 
Does it do it if you boot to safe mode w/ network support?

This is such a backward symptom from the usual situation
I'm suspecting there might be some kind of 3rd party software
interaction.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.
 
I have the same problem on one workstation.

The network has 10 workstation that are the same.
Only one always has red x's.

The problem is also with the saving of files.

Please post if you find the answer
 
Back
Top