jacktheripper88
Member
Good morning,
Ran into an odd situation last week while installing a WAP121 at a existing site.
Before I had left my shop, I had pre-configured the AP as a standalone AP and everything functioned fine. When I arrived onsite I connected the AP to the cat5 cable they had their in-house electricians run, attempted to connect to the AP and kept getting a connection error (can't remember the exact wording at the moment). Attempted to log into the AP but couldn't gain access at the time to the router controlling this portion of the network, so using the service laptop I had with me I checked to see if the laptop got an internet connection (which it did), and ran a continuous ping test for a few minutes. So the connection tested out find. Reconnected and power cycled the AP, connected my laptop to the network switch that the AP was connected to and did a local broadcast ping followed by arp -a to see if the AP was going to show up, but no luck.
Came to the conclusion something must have happened to the configuration of the AP or (despite being configured for DHCP) setting it up at the shop was hindering me. Did a factory reset (reset button for 15 secs), attempted to locate the AP on the network again to no avail.
So after the reset I decided to go on the easter egg hunt of finding which router I was dealing with. Traced the cabling back to a Cisco RV110W that ran their entire network. Spoke with one of their managers and got the login info for the router.
Logged into the router and checked for DHCP settings (my laptop connected fine at the desired location), looked for any connection restrictions but couldn't see any. Checked the currently leased IP address, AP was not listed still.
So to cut out every possible middleman device I could think of, I brought and connected the AP directly to the router. Still doesn't pull an IP.
So at this point I head back to the shop, reconnect it to our network and it pulls an IP address right away no problem.
Any ideas?
Ran into an odd situation last week while installing a WAP121 at a existing site.
Before I had left my shop, I had pre-configured the AP as a standalone AP and everything functioned fine. When I arrived onsite I connected the AP to the cat5 cable they had their in-house electricians run, attempted to connect to the AP and kept getting a connection error (can't remember the exact wording at the moment). Attempted to log into the AP but couldn't gain access at the time to the router controlling this portion of the network, so using the service laptop I had with me I checked to see if the laptop got an internet connection (which it did), and ran a continuous ping test for a few minutes. So the connection tested out find. Reconnected and power cycled the AP, connected my laptop to the network switch that the AP was connected to and did a local broadcast ping followed by arp -a to see if the AP was going to show up, but no luck.
Came to the conclusion something must have happened to the configuration of the AP or (despite being configured for DHCP) setting it up at the shop was hindering me. Did a factory reset (reset button for 15 secs), attempted to locate the AP on the network again to no avail.
So after the reset I decided to go on the easter egg hunt of finding which router I was dealing with. Traced the cabling back to a Cisco RV110W that ran their entire network. Spoke with one of their managers and got the login info for the router.
Logged into the router and checked for DHCP settings (my laptop connected fine at the desired location), looked for any connection restrictions but couldn't see any. Checked the currently leased IP address, AP was not listed still.
So to cut out every possible middleman device I could think of, I brought and connected the AP directly to the router. Still doesn't pull an IP.
So at this point I head back to the shop, reconnect it to our network and it pulls an IP address right away no problem.
Any ideas?
