Limited or No Connectivity message on all laptops

As of yesterday, wireless laptops are all getting "Limited or No Connectivity" when they connect to either of our WAP's.  Windows Server 2003 SP1, I have tried new profiles on the machines, reset and reconfigured both WAP's.  The laptops connect via Ethernet with no problem.
Any help would be appreciated.

Thanks,
Ric
HanoverFisteAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
HanoverFisteConnect With a Mentor Author Commented:
Well, I guess I have jumped too soon againn.  In all the hustle to address this problem quickly, it never occurred to me to re-initialize the router.  That's all it was.
Sorry everyone.
Thanks so much for your responses.
0
 
A ProorocuISMCommented:
Can u acces any of the WAP ? Maybe some connectivity problem, cables, etc.
0
 
HanoverFisteAuthor Commented:
I can access both WAP's from any (Ethernet) station on the network.
Yesterday afternoon was the first day anyone noticed the problem.
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Darius GhassemCommented:
Go into the Wireless Cards Profiles delete the Profile that is for the WAP. Try to connect again. Usually the error is for systems that can't get IP address or using the wrong Wireless Authentication.
0
 
KzooSteveCommented:
Run an ipconfig and check to see what IP address is being assigned. If the IP address starts with 169.254 then you aren't able to get DHCP.
0
 
KzooSteveCommented:
Out of curiosity, does the router provide DHCP?
0
 
HanoverFisteAuthor Commented:
Yes.  It's a SonicWall TZ-170 firewall that also servers at the router.
0
 
KzooSteveCommented:
If you run into the problem again, you can check to see if the users are getting a proper IP address (not 169.254.x.x). If they aren't, then this will tell you that something is wrong with the DHCP server, which in this case, is your TZ-170.
0
 
HanoverFisteAuthor Commented:
Resetting the router fixed the problem.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.