R
Richard
I run XP Home on my PC and access a Windows NT server via
a small Lan. I have defined mappings to 3 shared drives
in the server to drive letters F, G, and H. All are
defined with the 'reconnect at logon' option ticked.
All worked fine until I changed the LAN card in my PC to
a 3Com 1Gb card (model 3C2000); whenever I boot the PC
now, these mapped drives are unavailable. If I go into
Windows Explorer I can see the drives under 'my
computer'; the drive letters have an X through them. If
I open 'My Computer' from the Start menu I again can see
the drive letters but they again have an X through them.
If I then double-click on each drive letter in turn, they
open and I can see the contents of each drive, and the X
disappears, and I can use data and apps on these drives
OK (until the next reboot). As far as I can see I am
logging into the server domain/workgroup OK, there are
successful login entries in the event viewer. Other XP
PCs on the same Lan (including those which have had
similar Lan card changes) do not have these problems and
connect to the server drives OK when they boot. Any
ideas what's causing this failure to map the drives ?
a small Lan. I have defined mappings to 3 shared drives
in the server to drive letters F, G, and H. All are
defined with the 'reconnect at logon' option ticked.
All worked fine until I changed the LAN card in my PC to
a 3Com 1Gb card (model 3C2000); whenever I boot the PC
now, these mapped drives are unavailable. If I go into
Windows Explorer I can see the drives under 'my
computer'; the drive letters have an X through them. If
I open 'My Computer' from the Start menu I again can see
the drive letters but they again have an X through them.
If I then double-click on each drive letter in turn, they
open and I can see the contents of each drive, and the X
disappears, and I can use data and apps on these drives
OK (until the next reboot). As far as I can see I am
logging into the server domain/workgroup OK, there are
successful login entries in the event viewer. Other XP
PCs on the same Lan (including those which have had
similar Lan card changes) do not have these problems and
connect to the server drives OK when they boot. Any
ideas what's causing this failure to map the drives ?