victor voul wrote:
> I am using linksys DI-614+ wireless broadband router in my LAN and it
> always takes about 2 minutes for my Dell Inspiron 2650 laptop to
> receive a wireless network connection signal when I turn on the
> laptop. Is this 2 minute waiting time normal?? Appreciate any info on
> this!
Since you posted here through Google, it is not possible to know
definitively what OS you're using. I'll give you the benefit of the
doubt and assume you've got a brain, so you're using a Mac....:-)
Now, in your post, it *seems* as though you're saying that it takes two
minutes from turn on, to acquire an RF signal. Is this correct, or are
you saying that it takes you two minutes to make a valid, usable connection?
This is not simply an issue of semantics, but rather a point that if
you're attemtping serious diagnostics, then you must be clear on what is
happening with the equipment.
From the time that the client manager software loads in the operating
system, you should have indication of the reception of the RF signal.
From that point on, what you initiate can vary tremendously, depending
upon the sequence of events which the software initiates.
In my case, when I boot the operating system, the drivers for my
wireless device load up. At that point, reception of RF is indicated.
If I then select an AP to connect to, the connection (or most of it) is
nearly instantaneous. It will connect within a second or so. The
connection is instantaneous, if I have manually assigned an IP address
to the wireless card. If I have configured the card to dynamically
obtain its IP address, this "requesting of the IP address" usually is
accomplished in four to five seconds. The client manager display takes
about 500ms to update from the time that the operating system itself
obtains the IP address.
I can know that, because I request the DHCP address manually from a
console, and watch the client manager software update on the adjacent
screen. see
http://www.thuntek.net/~vguillen/art/desktop1.png
This is/was TOTALLY different from when I run the exact same hardware in
windoz9x. I was initially convinced that my very expensive Buffalo .11g
card was flaky or defective. I would initiate a connection, and the
connection would take anywhere from twenty seconds, to two minutes or
more, and then very often, even when the Buffalo Client Manager software
indicated a working connection, page requests in a browser would time
out. I then determined through diagnostics that the DHCP requests
hadn't been obtained, or that the old, previous IP address hadn't been
purged yet. When attempting to manually initiate this sequence with
"winipcfg", the TCP/IP stack would usually lock up. I performed a
repartitioning of the drive, fdisk, reformatting, reinstallation of JUST
win98, and then the drivers/Client manager......no other software at all.
Same exact story. I had known about limitations in win98's protocol
stack for many years, but only when I obtained the WiFi kit did the
profound flakiness of the stack really become apparent to me. Needless
to say, I don't ever boot in the virusware when using WiFi anymore. I
am very happy with my WiFi equipment now that I use it exclusively in
GNU/Linux. It performs flawlessly, at distances of several miles.
So the whole jist of this post is to make apparent that if you wish to
determine what is happening with your gear, you need to determine at
what point you delays are being incurred. If it is limitations in your
operating system, maybe it's time to switch so something more reliable,
and more importantly, something which is secure and not subject to the
countless trojans/viruses/worms.
Similar Threads
Linear Mode
