On 25 Dec 2005 05:09:19 -0800, "Leon Spinks"
<(E-Mail Removed)> wrote:
>The router H/W is v3.1.
That's one of the good ones. I have a 1.1, 3.0, 4.0 along with a mess
of customers that use these. However, all but one use alternative
firmware and not the stock Linksys firmware. I have never seen the
problem of only allowing a single DHCP delivered wireless connection.
Are you using SES (Secure Easy Setup)? Incidentally, stomping on the
front panel SES button for a "long" time is suppose to reset just the
wireless settings in the router.
Are you *SURE* you have 4.20.7 firmware installed? I'm asking because
version 4.00.7 had an interesting problem that vaguely sounds like it
might be involved.
- Resolves issue with enabling TKIP after enabling WEP
See release notes at:
|
http://www.linksys.com/servlet/Satel...&ssbinary=true
>Per your suggestions, I configured WPA-PSK
>using the HP. The Toshiba client wireless connection again indicated
>Limited or No Connectivity.
Argh. Have you tried to setup the Toshiba temporarily with a static
IP address, netmask, gateway, and DNS servers? I'm not sure what it
proves if it works, but it would be interesting to know.
>The router is setup to permit a maximum of
>5 connections simultaneously.
My sense of smell tells me that this is the source of the problem,
even though it totally legitimate. How are you limiting connections?
Do you have the DHCP server pool limited to 192.168.1.100 thru
192.168.1.104 in the WRT54G setup? That's fine. However, if you did
it by tweaking the netmask for the LAN side, methinks that might be
the problem. Leave it at 255.255.255.0 in the router on the:
Setup -> Basic Setup
page.
Oops, if the HP is successfully getting 255.255.255.0 from the WRT54g,
then the WRT54G is correctly setup with the proper netmask. So much
for that theory.
>The client that configures successfully
>(the HP in this case) possesses a class C netmask (255.255.255.0). The
>client that does not configure via DHCP has a class B netmask
>(255.255.0.0).
The 255.255.0.0 comes from when the DHCP request fails and the client
reverts to 169.254.xxx.xxx IP address. This is normal. If the DHCP
request is successful, the assigned netmask will be 255.255.255.0
unless otherwise changes in the LAN setup.
>I grabbed a network cable and plugged the Toshiba into
>the WRT54G. A connection materialized instantaneously. Web surfing
>restored.
OK, then it's not a trashed LSP stack or mangled winsock on the client
end. Basically, the Toshiba DHCP is working as expected.
>The wireless lan drivers on both clients are based on the
>WRT54G cdrom for v3.1 contents.
I'm not sure what that means. I've never used whatever is on the
cdrom that comes with the router. If you've installed some sort of
driver from Linksys on the Toshiba, you might wanna remove it and see
if the Intel 2100a Proset utilties (7.1.4.5) do a better job. For the
very latest, see:
|
http://downloadfinder.intel.com/scri...&ProductID=944
|
http://support.intel.com/support/wir...wlan/pro2100a/
>I tried the master reset button on the
>router several times -- this WPA issue is persistent and an annoying.
>I posted to dslreports per the previous discussion. I have not
>attempted the DHCP sniffer.
Could I trouble you for the operating system version on both machines?
Also the model number of the Toshiba Portege? It probably comes with
XP but I just wanna be sure.
I don't have a clue what is happening. My guess(tm) is that there's
either a major bug somewhere, or you're doing something creative in
the setup with the 5 IP address limit. Try resetting everything to
defaults (again). Get it working with no encryption. Leave every
other setting in the router at defaults. Delete any wireless profiles
on both the HP and Toshibah. In other words, start over and make no
assumptions that your previous work was correct. That should work as
you previously indicated. Then, enable WPA-PSK using an easy to type
encryption key (typo errors are rediculously common). Don't tinker
with limiting the number of connections and don't use wireless
profiles in the client. If you don't get a DHCP address, reboot the
client to be sure it's not "hung" or something odd. If that works,
put the DHCP address limits into the router and see what happens. If
it then doesn't work, you may have found a router bug.
--
Jeff Liebermann
(E-Mail Removed)
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060
http://802.11junk.com
Skype: JeffLiebermann AE6KS 831-336-2558