WAP getting kicked off network

[imported_ChaoticGeek]

I'm currently working at a university with a large campus network. The department I'm working for is trying to set up a wireless access point for one of our buildings. The main problem is that when we connect the WAP to our network, it's up for a few minutes and then just disappears entirely. Not just the wireless connection...you can't even ping it with a computer that's connected via a physical ethernet connection.

We use DHCP here, but you have to create an entry for the device using the MAC address in the DHCP table. We've tried two different IPs (that were most definitely NOT in use) for the WAP to no avail. I've tried setting it to both DHCP and a static IP (the one assigned to the device in our DHCP tables) in the WAP's settings. Both ways, it will show up for a couple of minutes and then disappear completely.

I reset the WAP to factory settings, kept it off of our network, and just connected to it directly with my laptop. From there I gave it a static IP, changed the TCP/IP settings on my wireless connection to a static address that would match the subnet of the WAP, and disconnected the ethernet cable. The wireless connection showed up on my laptop fine, and I left it connected for about 45 minutes with no problems. Connected it back to our network, it showed up for a couple of minutes, and then disappeared again.

Something is definitely kicking the WAP off the network, but I can't figure out what or why. Any ideas or suggestions as to what I should be looking for?

The WAP is a Linksys WAP54GX, connected to our network with an ethernet connection. I've reset it to factory defaults and reconfigured it several times now.

Thanks in advance!

 

[netsysadmin]

Did you consider you might be doing something against the rules? Both universities I have worked for have had very strict rules on adding non-university installed access points to the network. Most likely they are finding your rogue access point and shutting it down. You might want to check into the policies before you get yourself in trouble.

What school are you at?

John

 

[imported_ChaoticGeek]

No, it's not a matter of going against the rules. I've been told to set this up by the IT manager of this department, and he's in charge of the entire subnet that this is going under. So I'm not breaking any rules or anything, this has been OKed by the appropriate people. Oh, and I'm at UGA.

Thanks!

 

[spidey07]

could be a speed duplex setting.

What is the model of AP?
What are the models of the switches?
Are there any errors on the switch port - should be none?
What features are enabled (spanning-tree, bpduguard, udld, portfast, etc) on the switch port?
Is the port going err-disabled or is the switch shutting down the port and you lose link?

1) use a static IP address/mask/GW on the AP
2) set speed/duplex to auto on the switch and AP (or force both sides), never hard code one side of the link and leave the other end auto

There are a few dozen things that could cause the behavior you are seeing.

-edit- read your post again. The switch is most likely kicking the AP off (security, etc). You'll need to talk to who controls the network.

 

[RebateMonger]

Originally posted by: spidey07
-edit- read your post again. The switch is most likely kicking the AP off (security, etc). You'll need to talk to who controls the network.

I know zip about managed switches, but that certainly seems the case. It appears that the switch that's connected to your (WAP) switch has deemed its MAC address to be unwelcome and has disconnected it from the rest of the network.

 

[spidey07]

Originally posted by: RebateMonger

Originally posted by: spidey07
-edit- read your post again. The switch is most likely kicking the AP off (security, etc). You'll need to talk to who controls the network.

I know zip about managed switches, but that certainly seems the case. It appears that the switch that's connected to your (WAP) switch has deemed its MAC address to be unwelcome and has disconnected it from the rest of the network.

Or the wireless control system sees/hears another radio being brought up and kicks the AP off the network.

If they setup their network properly this is probably the case. It's to prevent people from connecting access points.

 

[RebateMonger]

Originally posted by: spidey07
Or the wireless control system sees/hears another radio being brought up and kicks the AP off the network.

If they setup their network properly this is probably the case. It's to prevent people from connecting access points.

You could test that one by turning off the radio transmitter on the WAP, I imagine.

 

[spidey07]

but there are still a host of security features to prevent it even if the radio is turned off.

for example if you see more than one mac address on the port (AP with any clients connected will show this), shut down the port.

There's just too many ways to prevent people from just plugging active network gear in.

 

[JackMDS]

It seems to me that you do not have the correct parameter to keep the Access Point live on the Network.

The IT people in charge should provide you with the exact credentials as it should apply to the specific Access Point that you are using.

Once you have the credentials you should connect the Access Point with a crossover cable to a stand alone computer (not on the Network) that is set to Auto obtain IP. Configure the Access Point according to the IT parameters, and then put it on the Network.

:sun:

 

[imported_ChaoticGeek]

Thanks for all your help guys, I'll investigate further and talk to some higher-ups.