Re: Mapped network drives don't reconnect at logon
- From: rlw@xxxxxxxxxxxxxxxx (Bob Weissman)
- Date: Sat, 15 Oct 2005 18:55:25 GMT
In article <ewPPIfY0FHA.2064@xxxxxxxxxxxxxxxxxxxx>,
Malke <notreally@xxxxxxxxxxx> wrote:
>Bob Weissman wrote:
>
>> Yes, I've narrowed it down to the wireless card and/or driver because
>> the problem doesn't occur when using a hard wire. It's gotta be a
>> timing thing. Every Windows startup-time program is yelling "me
>> first!" and somebody's gotta lose. I wish there were a finer-grained
>> way of specifying who gets to go first. I need the wireless connection
>> to be up before Windows tries to reconnect mapped drives.
>>
>> I use the mapped drives for purposes other than backup. (I'm using the
>> Iomega auto backup program which came with my NAS drive, and it works
>> well.) I also use the mapped drives for Quicken, which after all these
>> years still needs them to see network drives, and in some of my own
>> batch scripts. So I wish I could find a way to get the wireless card
>> to start sooner.
>
>I've Googled around but I can't find anything to show how to make the
>wireless driver start early enough. Maybe one of the networking gurus
>in one of the wireless and/or networking groups can help. Here's a list
>of all the MS newsgroups:
>http://aumha.org/nntp.htm
>
>Like you, I think the timing is the cause of the problem. Some
>suggestions which may or may not be useful:
>
>1. Assign the laptop a static IP address and set the gateway to the
>router's address. Use the router's address for DNS. You can always use
>the alternate configuration (setting it up as dynamic) for when you and
>the laptop are not at home.
>
>2. If you are using Windows to manage the wireless, use the wireless
>adapter's software instead - or vice versa.
>
>3. Try a different wireless adapter and use its drivers.
>
>If you figure this out, I'd love to know if any of that worked.
>
>Good luck,
>
>Malke
I'd already tried #3 with my old Linksys 'b' card, and it worked fine. I
guess this narrows it down to the D-Link driver being slow to start.
I tried #1 and #2 also; neither helped.
I did come up with a workaround. It's kind of annoying, but it solves
the problem: I added a password to my logon.
Because the driver starts at boot time, but the reconnecting doesn't
occur until logon, prompting for a logon password delays logon long
enough for the wireless connection to complete. I can tell by looking at
the LEDs on the D-Link wireless card whether it's connected. So I delay
logging on until then.
It's annoying to have to supply a password, but it's less annoying than
having to manually reconnect the drives every time.
I'll keep looking for a more elegant solution.
Thanks,
- Bob
.
- References:
- Re: Mapped network drives don't reconnect at logon
- From: Malke
- Re: Mapped network drives don't reconnect at logon
- From: Bob Weissman
- Re: Mapped network drives don't reconnect at logon
- From: Malke
- Re: Mapped network drives don't reconnect at logon
- Prev by Date: Re: Problem setting up Encryption with Wireless Network
- Next by Date: Re: Hijacked Maybe
- Previous by thread: Re: Mapped network drives don't reconnect at logon
- Next by thread: Xp Install
- Index(es):
Relevant Pages
|
