Re: Mapped network drives don't reconnect at logon
- From: Malke <notreally@xxxxxxxxxxx>
- Date: Fri, 14 Oct 2005 12:48:33 -0700
Bob Weissman wrote:
> Malke, thanks for the reply. I can't imagine I'm hitting the
> connections limit because my network is almost minimally tiny. I have
> three hosts on the network: a desktop computer, a laptop computer, and
> a network hard drive. The failure is occurring on the laptop, which is
> trying to mount the two other hosts. The desktop and network drive are
> hard-wired to the router, and the laptop is using a wireless
> connection.
>
> This was all working fine right up until I changed things. ("Tweak it
> until it breaks" has always been my motto.)
>
> I was hoping my problem was generic enough that the details wouldn't
> matter. Wrong again. Here's what's changed. Maybe you or someone will
> recognize this.
>
> This last week I switched my ISP from SBC-Yahoo DSL to Comcast cable,
> because at my location, cable is about 8x faster than DSL.
>
> Seeing the increased speed for the WAN connection motivated me to
> upgrade my wireless LAN as well, from 802.11b to 802.11g. I switched
> from a Linksys router & WiFi card to a D-Link ("pre-N super-G") pair.
> All works fine except for the failure of the drives to reconnect on
> the laptop.
>
> In order to get the Comcast setup running, I ran the Comcast setup
> disk on the laptop while it was hardwired to the cable modem, thus not
> connected to the rest of the then-still-existing DSL-based network.
> Then, after getting the D-Link wireless card, I ran D-Link setup
> software/driver install on the laptop.
>
> This brings us up to date. Either the Comcast or the D-Link software
> could be the culprit, or some combination of the two. I shudder to
> consider attempting to get tech support from Comcast or D-Link, due to
> the hours of "first prove to the phone rep that you're not a complete
> idiot," not to mention "it must be the fault of some other part of
> your network which we don't support" which that always entails.
It sounds like it could possibly be a power management problem and/or a
timing problem. Either the wireless adapter is getting turned off by
power management or the wireless network doesn't kick in quickly
enough. I don't think this has anything to do with Comcast. To check
the power management on the network card, look at its properties in
Device Manager and see if there is a power management tab. If so,
uncheck the box that says "allow Windows to turn off this device when
not in use".
Another way to handle this would be to set your backup software to wait
until you know all computers are on. For instance, on a small network
like yours I would suggest using SecondCopy (www.centered.com) and
simply set the copying time to when you know all three machines will be
on instead of mapping drives. There is no need to map drives unless you
are using specialized software running on a server that needs the
workstations to think it is really running locally.
Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User
.
- Follow-Ups:
- Re: Mapped network drives don't reconnect at logon
- From: Bob Weissman
- Re: Mapped network drives don't reconnect at logon
- References:
- Prev by Date: Re: Good Antivirus prog.
- Next by Date: Re: Good Antivirus prog.
- Previous by thread: Re: Mapped network drives don't reconnect at logon
- Next by thread: Re: Mapped network drives don't reconnect at logon
- Index(es):
Relevant Pages
|
Loading
