C
Chris_G
Recently (within the last two months or so), I have been getting some
quite odd and very drive mapping issues with my Windows XP Pro with
SP1 PC that I do not have with my Windows NT 4.0 PC.
Due to job requirements, I need to map to Users PC's, servers (NT,
2000, 2003 and various flavors of Novell) and sometimes over painfully
SLOW links. In certain cases, I need to do so with different
credentials, etc. 99% of the time, I map using a batch file using net
use * and about 75% of the time, everything works fine. However, the
other 25% of the time I get the following issues:
1) Drive drive doesn't show up within Windows Explorer or My Computer.
Though, if you type in the drive, you can get to it. On Windows
Explorer, it shows it as a connection via the little network icon,
though it has no drive mapped to it. Sometimes, it even removes the
little network icon if you refresh your screen hitting F5 OR doesn't
show one at at. Then, if you try to copy files to the PC via Windows
Explorer/My Computer, it comes up with an error stating that the
remote drive doesn't support long file names and wants to know if I
want to automatically change it to the 8.3 naming convention (at this
point, I give up and use DOS to get the job/task done). If you try to
unmap it via Windows Explorer/My Computer, it doesn't. However, if
you go to disconnect a network drive via the Network Neighborhood
Icon, the drive mappings are all there and it will allow you do unmap
the drive (DOS allows you to unmap the drive to). I know that most
might think it is the slow connection that is doing it. However, it
can happen between two PC's, on the same subnet, one number off on the
IP address with 100 Mbps cards, logged in via the local admins with
Virus Scan turned off.
NOTE: Sometimes, this problem resolved itself over time. However, I
have also had the problem take over a day and a half to resolve to a
PC on the same subnet.
2) The other thing is phantom drives. These show up whenever they
want to, even with no mention of it under the Network Registry entries
or any old mapped drives. Sometimes rebooting removes them, other
times it takes numerous reboots to fix it.
3) Yet another thing is opening up Windows Explorer to cruise around
my local hard drives, which sometimes ends up with a hung process and
the white screen of Explorer death. This happens sporatically, logged
in via the network or the local admin, with or without virus scan
running. Sometimes, even with the network cable taken out logged in
as the local admin of the PC.
The only thing I can even remotely think of that might be related to
this is that XP is trying to "save resources" and dropping all drives.
But, that doesn't explain why it works SOMETIMES and it fails
sometimes logged on locally with the local admin.
Since I am at a loss, does anyone have any ideas??? Let me know and
thanks!
Chris
quite odd and very drive mapping issues with my Windows XP Pro with
SP1 PC that I do not have with my Windows NT 4.0 PC.
Due to job requirements, I need to map to Users PC's, servers (NT,
2000, 2003 and various flavors of Novell) and sometimes over painfully
SLOW links. In certain cases, I need to do so with different
credentials, etc. 99% of the time, I map using a batch file using net
use * and about 75% of the time, everything works fine. However, the
other 25% of the time I get the following issues:
1) Drive drive doesn't show up within Windows Explorer or My Computer.
Though, if you type in the drive, you can get to it. On Windows
Explorer, it shows it as a connection via the little network icon,
though it has no drive mapped to it. Sometimes, it even removes the
little network icon if you refresh your screen hitting F5 OR doesn't
show one at at. Then, if you try to copy files to the PC via Windows
Explorer/My Computer, it comes up with an error stating that the
remote drive doesn't support long file names and wants to know if I
want to automatically change it to the 8.3 naming convention (at this
point, I give up and use DOS to get the job/task done). If you try to
unmap it via Windows Explorer/My Computer, it doesn't. However, if
you go to disconnect a network drive via the Network Neighborhood
Icon, the drive mappings are all there and it will allow you do unmap
the drive (DOS allows you to unmap the drive to). I know that most
might think it is the slow connection that is doing it. However, it
can happen between two PC's, on the same subnet, one number off on the
IP address with 100 Mbps cards, logged in via the local admins with
Virus Scan turned off.
NOTE: Sometimes, this problem resolved itself over time. However, I
have also had the problem take over a day and a half to resolve to a
PC on the same subnet.
2) The other thing is phantom drives. These show up whenever they
want to, even with no mention of it under the Network Registry entries
or any old mapped drives. Sometimes rebooting removes them, other
times it takes numerous reboots to fix it.
3) Yet another thing is opening up Windows Explorer to cruise around
my local hard drives, which sometimes ends up with a hung process and
the white screen of Explorer death. This happens sporatically, logged
in via the network or the local admin, with or without virus scan
running. Sometimes, even with the network cable taken out logged in
as the local admin of the PC.
The only thing I can even remotely think of that might be related to
this is that XP is trying to "save resources" and dropping all drives.
But, that doesn't explain why it works SOMETIMES and it fails
sometimes logged on locally with the local admin.
Since I am at a loss, does anyone have any ideas??? Let me know and
thanks!
Chris