Network Works but Wireless Doesnt

Microsoft Windows server 2003 r2 standar...
December 10, 2009 at 11:32:46
Specs: Windows Server 2003, Xenon E5504 / 2GB Ram
First ill explain the network. Modem -> Cisco ASA -> two Netgear Switches, both go -> Server and local networked computers and Netgear wireless access points.
Now, the problem is the local network works fine, but wireless gives out 169.254.x.x ip addresses and 255.255.0.0 subnet masks. BUT if i manually put in IP info on the laptop to connect to wireless, it works. Any ideas?

See More: Network Works but Wireless Doesnt

Report •

#1
December 10, 2009 at 11:52:02
but wireless gives out 169.254.x.x ip

It is not the wireless that is giving out that address, it is an automatic address allocated by Windows when it cannot find a DHCP server.

Check your configuration

Stuart


Report •

#2
December 14, 2009 at 12:25:21
DHCP is disabled on the switches. It was working fine before the power outages. Im assuming it reset something but i dont know what. Everything looks ok....

Report •

#3
December 14, 2009 at 14:50:15
Switches don't do DHCP so your statement about DHCP being disabled in them makes no sense. What device in your network is providing DHCP?

If there was a power glitch the configutarion in your WAPs might have been upset. Sometimes a complete shutdown and progressive restart of all hardware is needed to re-establish connections.

Goin' Fishin' (Some day)


Report •

Related Solutions

#4
December 15, 2009 at 06:21:11
I have manual ip's for the switches and the server has the ip ranges and setups for the ips.

Report •

#5
December 17, 2009 at 11:00:18
IP's are handed out by the server, so yes the server.

Report •

#6
December 17, 2009 at 11:08:48
I would have expected either the access points or the cisco ASA to be giving out the ips for internet access.

Anyone else having this issue? If not I would suspect your wireless card is fried.


Report •

#7
December 17, 2009 at 11:22:25
Access points are fine, and the cisco asa is fine. Anyone wired is good. But wirelessly, its not working.

Report •

#8
December 17, 2009 at 12:03:26
is that everyone connected to wireless or just you?
can you connect to the ip of any wireless AP?
is your dhcp server [not asa or router] providing all ips?

It does not appear your APs are passing dhcp thru them


Report •

#9
December 22, 2009 at 07:47:55
i have 3 wireless access points. none work. in their settings i have disabled dhcp and i have given them ip's of 10.1.1.10, 10.1.1.20, and 10.1.1.30 with submask of 255.255.255.0 and a gateway of 10.1.1.1. But for right now, i've removed the .20 and the .30 access points.
On the server i've created a scope named guest, of 10.1.1.0 with an ip range of 10.1.1.1 through 10.1.1.255 and then added the exclusion of the ips 10.1.1.1 through 10.1.1.100. i also added 003 router (10.1.1.1) and my dns servers.

So now ... if i have the laptop search for the ip automatically, it will not work. ipconfig shows a sub mask of 255.255.0.0 and some weird ip. But if i manually input the ip of 10.1.1.11 and etc., it will work. What am i missing? This is driving me insane!


Report •

#10
December 22, 2009 at 09:32:49
ap's need to be configured for dhcp relay?

Report •

#11
December 23, 2009 at 11:27:59
They are being pointed to the right gateway ... unless there's a physical option for that. But i've gone through every since line in the AP's and found nothing yet that looked wrong.

Report •

#12
December 23, 2009 at 11:31:15
I thought your issue was that they are not passing dhcp requests/acks thru. Some AP's are also routers. To pass dhcp thru a router it has to relay dhcp requests. This is why I suggested you check to see if they support dhcp relay and if so to enable it.

Gateway has nothing to do with dhcp. Your gateway may also be your dhcp server but you can specify no gateway [and for a ap's config there is no reason for a gateway unless you wish to maintain it remotely] and dhcp will still work from the same appliance.


Report •

#13
December 28, 2009 at 06:29:39
Its a netgear wpn802 v2 and it doesnt seem to support dhcp relay. I just reset the router by clicking the button on the back, and now i cant even connect to the default 192.168.0.231. Nor the 10.1.1.10 i set it to. This is so aggravating, im about to buy new equipment..

Report •

#14
January 5, 2010 at 07:05:03
Any other ideas? Maybe its the Cisco ASA? I can't get in there to take a look because my ASDM Launcher version is old and not compatible. Anyone know how to get an update on that?

Report •

#15
January 20, 2010 at 10:40:35
Got the wireless to work. I switched the AP's to the other switch, and voila it worked.

Report •

Ask Question