Network Drives Not Connecting Properly
From: Tagge (wdoch_at_yahoo.com)
Date: 04/22/04
- Next message: Ron Lowe: "Re: Detect network very slow"
- Previous message: Ron Lowe: "Re: error 711"
- Next in thread: Jeffrey: "Network Drives Not Connecting Properly"
- Reply: Jeffrey: "Network Drives Not Connecting Properly"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 22 Apr 2004 05:37:42 -0700
Hey folks,
I have a wireless (802.11B) network running at this point
and time, all machines are running Windows XP and also a
server running Windows 2K3 on it. I have a mapped drive
that is nessicary for all the laptops to gain access to
when they connect. However, often when they boot their
laptops up and get into Windows it doesn't recognize the
mapped drive and leaves a red x through it indicating it
isn't connected.
A specific program requires this mapped drive to work
properly. If they go in and immedately start that program
up, it doesn't see the mapped drive and fails to start
properly. The only way for these people to get there
laptops to recognize the drive sometimes is to physically
browse to it and click on the drive, forcing the PC to
read it's contents on the network and recognize it is
connected. This is troublesome as none of these people
using this software are very handy w/ a computer.
The drive is only really required inside of this program.
I wrote a batch file to ping the drive as it seems to help
wake it up most of the time but isn't fool proof. Still
about 10% of the time, it doesn't connect. Is there any
way I can make this network resource more readily readable
to XP? Help would be appreciated.
-T
- Next message: Ron Lowe: "Re: Detect network very slow"
- Previous message: Ron Lowe: "Re: error 711"
- Next in thread: Jeffrey: "Network Drives Not Connecting Properly"
- Reply: Jeffrey: "Network Drives Not Connecting Properly"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
