Mapped drives have Red X?

  • Thread starter Thread starter Michael Cecil
  • Start date Start date
M

Michael Cecil

I had no problems with networking and sharing files, etc. Even this is
really a cosmetic annoyance. I've mapped a shared folder on my server
onto my Vista workstation using Windows Explorer.

When I rename it from "Shared (\\SERVER)" to just "SERVER" it displays a
red X on the little networked drive icon in explorer. It still works fine
however. I was just wondering if there was a way to rename it without
getting the incorrect red X.
 
Michael Cecil said:
I had no problems with networking and sharing files, etc. Even this is
really a cosmetic annoyance. I've mapped a shared folder on my server
onto my Vista workstation using Windows Explorer.

When I rename it from "Shared (\\SERVER)" to just "SERVER" it displays a
red X on the little networked drive icon in explorer. It still works fine
however. I was just wondering if there was a way to rename it without
getting the incorrect red X.
Click to expand...


Are you on a wireless connection? Does the red X go away after you access
the mapped drive? On my notebook mapped drives have the red X. If I do
something that accesses the drive then the next time I look in Explorer the
red X has gone away. After a while it comes back. As it doesn't affect the
way things work I've always just ignored it. In my case I've always assumed
it has something to do with the wireless connection. My notebook goes
through two wireless connections to get to my server, one to the router,
then a wireless bridge to the server. On a workstation on the same switch as
the server I don't see this behavior. It would be interesting to find out
what is really going on.
 
Are you on a wireless connection? Does the red X go away after you access
the mapped drive? On my notebook mapped drives have the red X. If I do
something that accesses the drive then the next time I look in Explorer the
red X has gone away. After a while it comes back. As it doesn't affect the
way things work I've always just ignored it. In my case I've always assumed
it has something to do with the wireless connection. My notebook goes
through two wireless connections to get to my server, one to the router,
then a wireless bridge to the server. On a workstation on the same switch as
the server I don't see this behavior. It would be interesting to find out
what is really going on.
Click to expand...

No, this machine wasn't using a wireless connection. I did notice that if
I add the // back to the drive name that it makes the X go away. Pretty
odd, eh?
 
Back
Top