Cisco ValetPlus (M20) Not Receiving IP From Cisco 1841

BW1982
BW1982 used Ask the Experts™
on
Our Cisco 1841 router is set to assign IP addresses on the network, however our wifi access point (M20) will not resolve an IP address from the router for some reason. Using the exact same physical port, I plugged in my laptop and it assigned an IP address to it right away, without any issues.

I logged into the router via HTTP and released/renewed the IP address. By default, the M20 resolves a loopback address, and the moment I release/renew, it resolves nothing. Yet once again, the second I plug in my laptop, all is well connectivity-wise.

The odd thing is that the M20's link lights suggest the router is receiving internet connectivity just fine, however no device connected to it either via wifi or directly via ethernet port can receive any network connectivity whatsoever.

I'm not keen on SSH routers, particularly the configuration of the 1841. Anything with syntax is super-intimidating and wildly confusing, so naturally, I figure the issue is with my zero understanding of SSH or its syntax on the 1841.
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Top Expert 2014

Commented:
Which port on the M20 do you have connected to the 1841?

I think for this to work the it has to be one of the LAN ports.  I don't think the M20 will forward DCHP requests/responses through the WAN port.

Author

Commented:
It is a LAN port. The connection goes like this:

Internet > Modem > 1841 > Patch Panel > M20

But I've tried these with the exact same results:

Internet > Modem > 1841/M20 > Patch Panel

Internet > Modem > 1841 > M20/Patch Panel

(The / indicates devices are plugged into the same previous device simultaneously)
Top Expert 2014

Commented:
I would mirror the port connecting to the M20 and do a packet capture to make sure the M20 is forwarding the DHCP requests.
Commented:
My apologies. It was an IP addressing conflict. The default LAN IP the router assigns itself (192.168.1.1) was already in use which is why it could not resolve a WAN IP. My mistake. The Valet is resolving the IP just fine now. Thanks.

Author

Commented:
Stupid mistake -- IP address conflict. Sorry for the inconvenience.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial