Link to home
Start Free TrialLog in
Avatar of colindow
colindow

asked on

Wireless Networking - Wireless recognises router but cant ping

I have a Toshiba tecra 9100 running Win2000 sp4.
I also have a Vigor2600we  router with wireless networking (at home).

My Tosh recognises the wireless broadcast and returns the Mac address etc but I cant seem to get any further. I cant ping renew IP address etc.

Work have an intel 2011 router and other Tosh tecras  get on fine but not mine . I experience the same problem. As far as I can see settings are the same although not all the SP's,Bios etc are the same level (mine is more up to date).

Am I missing some obvious setting that is preventing me from networking with either of these routers?

Avatar of Adrian Dobrota
Adrian Dobrota
Flag of Romania image

Well , the answer is simple: You either have a failing card either missing some settings.
What to check ... Let's see:
- set the same SSID and channel to communicate in RF
- if WEP encription is activated, disable it on the router side at least temporarily
- check for autonegociation speed to be set (not to be an arbitrary 11Mb or so )
- card's IP address to be set in the same subnet
- try both software to connect (provided by vendor and Windows's )
- 802.11x card to be set in "client" mode (not ad-hoc --> used to connect directly to other card)

If still no go ...  replay and we'll see.

Kronos
colindow ... if you agree I'll ask for this Q to be moved in Wireless area where it belongs.
Avatar of colindow
colindow

ASKER

yep sorry missed the wireless section
any conclusion Colindow ?
Still going through it. Ideally I want to test it on my home router so it means waiting till I get home!
ok.
waiting
Hmm still no banana (although I'm not sure I totally followed the last 802 suggestion).
I can get a conection via cable suing my normal lan network card though.
Wireless reception still shows as excellent but I just cant get a tcp/ip connection.
ASKER CERTIFIED SOLUTION
Avatar of Adrian Dobrota
Adrian Dobrota
Flag of Romania image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
You might try to manually give the wireless card an IP and see if that works. If so it could be a DHCP problem on the wireless part.
Can you connect to the touter directly and check it's log? Is it seeing you when you associate?

AFAIK, kronostm's guidelines are the way to go. One things he forgot though was to tell you to disable MAC filtering. DHCP may be a problem, as well as WEP or even 802.1x auth. But your problem sounds to be like a "AP sees NIC but rejects MAC".


Also check that both are running, same band and protocol.

Apart from that I can;t see except a faulty card.
I have the same issue with a different router: one of the Linksys BEFSR41 series 802.11b wlan/routers.  All my 80211b cards connect fine, but when I tried to introduce any (linksys, netgear, etc) 80211g cards, I had the same symptoms as above.  Eventually, I tried a Sony VAIO laptop with integrated 80211g, and it, too failed.  I'd been on techsupport for hours with each respective manufacturer (each access card, the router, the integrated card).

Finally, I broke down and replaced my 80211b router with an 80211g, and everything connects just fine.  (incidentally, increased range, too with the new technology, I guess)
I've experienced the exact same problem on several different routers.  The solution was always to disable WEP on both the router and the client, get a good working connection.

Then if you need, re-enable WEP carefully, and it should continue to work.

Unfortunately I've seen it "break itself" again for no reason a week later, and I just disabled then re-enabled WEP again and it was back online.

-Matt
As the Toshiba problem... sigh...  I know the answer, but not how to fix it.

All the other stuff is good general ideas for 802.11 problems, but is probably not really the problem.

There are some patches typically distributed as part of the usual corporate common image that have the side effect of disabling the built in 802.11b card.  It says it's working, BUT IT IS NOT.

My wife had the exact same issue as did many of her work-mates.  They found - bypassing the outsourced support folk - a patch to re-enable it.  Unfortunately it's on her laptop and I don't/won't have access to it.  I'll have to see if I can find the #...

-----Burton
Many thanks. I've been out of the office but I shall return home and try a few of these ideas out on my router tonight.
Many thanks. I've been out of the office but I shall return home and try a few of these ideas out on my router tonight.
I had the same trouble. Inabiling NetBIOS over TCP/IP did the trick for me.
....waiting ....
Things to consider when purchasing and troubleshooting equipment...

Try to buy the same brand RF equipment when you can.  All to often compatibility issues arise between mixed vender RF networks.  Also, ALWAYS update the firmware in all RF hardware.  This is especially true with the "low-end" units such as Linksys and D-Link.  Not to say these products are junk, they are not.  However, one would be surprised how far a firmware upgrade will go on these lower priced, home models.

Lastly, no one mentioned this directly, so I will.  Someone mentioned to turn encryption off on both ends and that's an excellent place to start.  Here's why;

If you're using WEP encryption, you will still see signal strength on the mobile unit even if you enter the encryption key into the mobile unit incorrectly.  So, it's very misleading and one would assume that the encryption is set up correctly.  I see this often.  If you have good signal to the AP but can't pull an IP, kill the encryption on both sides and see if you get an IP then.  If so, re-enable encryption and make sure the keys on both ends are correct.  If they are, upgrade, upgrade, and upgrade the firmware.