G
Guest
Guest
Archived from groups: microsoft.public.windows.networking.wireless (More info?)
I set up a wireless network for a client who was moving his office. It's
just two computers running Windows XP with some shared files and drives
mapped back and forth. The network seems to work fine, and after encrypting
it, I mapped the drives across it. All works fine, except upon reboot. When
either of the computers reboots, it gets to where it tries to reconnect the
mapped drives, and announces that it cannot reconnect the network drive.
Hardly surprising since it doesn't load the wireless software until much
later in the boot process. Of course, none of the programs that use those
mapped drives will work until after opening up My Computer and
double-clicking on each of the network drives in turn, upon which it finds
them and connects the drive. After that everything works fine until the next
reboot. While this is a workable short term workaround, he is just beside
himself about having to do that. What is the solution to this problem? Is
there a way to delay when Windows XP tried to map network drives? Is there a
way to get it recheck them later? Is there a way to script the process of
double-clicking on each one after bootup? Any help would be greatly
appreciated.
I set up a wireless network for a client who was moving his office. It's
just two computers running Windows XP with some shared files and drives
mapped back and forth. The network seems to work fine, and after encrypting
it, I mapped the drives across it. All works fine, except upon reboot. When
either of the computers reboots, it gets to where it tries to reconnect the
mapped drives, and announces that it cannot reconnect the network drive.
Hardly surprising since it doesn't load the wireless software until much
later in the boot process. Of course, none of the programs that use those
mapped drives will work until after opening up My Computer and
double-clicking on each of the network drives in turn, upon which it finds
them and connects the drive. After that everything works fine until the next
reboot. While this is a workable short term workaround, he is just beside
himself about having to do that. What is the solution to this problem? Is
there a way to delay when Windows XP tried to map network drives? Is there a
way to get it recheck them later? Is there a way to script the process of
double-clicking on each one after bootup? Any help would be greatly
appreciated.