Accessing a Router Behind a Router

I am doing this all remotely. The customer's ISP (CenturyLink) supplied a router with the service. It is at and is a DHCP Server. One of the LAN Ports goes directly to a Netgear Wireless Router so that the Netgear Router is the only thing attached to the CenturyLink Router.

   The Netgear is static IPed at and the WAN port picked up and IP address of from the CenturyLink Router. I remote in to a computer on the LAN (NetGear LAN) and gave this computer two static IP addresses. and So... why can't I ping or access the CenturyLink router at or even ping the WAN port of the Netgear at

   Is there any way to access the CenturyLink router?
LVL 15
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Have you looked at your route tables to see if a route back is in place? Check your masks also, you may  need to set up a IP Helper address.

Can you post your config?

Muhammad BurhanManager I.T.Commented:
on any client after Netger's Router, open Netgear Web console and try to ping from there.
it should reply because is the default gateway for Netgear. If it didn't respond, so you have to troubleshoot/configure this thing first.

then, remove proxy (if any) on client's browser and try
if any error appears, please share it.
You must NOT give an IP address in 192.168.1.x on anything to the LAN/WLAN ports of the netgear router. By the way, it is not a router but a gateway, as it does not route packets both ways but perform NAT (network address translation) between the LAN/WLAN ports and the WAN port.

Why can't you give an IP address in 192.168.1.x on a node connected to the Netgear ? Because then, it will "think" that any other IP address in 192.168.1.x is local and it will NOT send the corresponding packets to its default gateway for it to forward them.

So, at first, remove the IP address from your node and try to ping It should work.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
IT Administration

From novice to tech pro — start learning today.