I am trying to log in to a Belkin router to reconfigure it for use as signal extender on my home wireless network. When I type and SEARCH 192.168.2.1 in my web browser, it preforms an internet search. I did GET in one time. I tried just about everything suggested in forum, but probably missed something. Router is teathered to computor via its ethernet port and one of the lan ports on the modem, but not to cable modem. When I ping 192.168.2.1 it appears to see the router. How can I search for the router on my computer without searching the entire web? Of course when I turn off my wireless connection, it goes nowhere. After many hours I resolve that I need help!

Thanks, JoeAre you CERTAIN that is the correct IP-address? Did you lift that off the manual?

Check the details on the Windows network interface to see what the gateway SAYS, that's the I.P you need to use in most cases if you're running DHCP on a simple home network.

You might have to reboot your router, sometimes the interfaces crashes and the router may yet work.Yes, it is the correct address and I have rebooted and preformed all the suggested solutions. I have accessed the modem from this computer once and made changes. Rebooted/reset the modem and still cannot log in to it.Try 192.168.0.1

Also some MODELS also have a pinhole reset....Must say I'm not too fond of Belkin. Does it assign an IP address? What's the gateway according to Windows?I used the Belkin as one the suggested units in a article at ehow on extending a Netgear wireless network.

http://www.ehow.com/how_6862867_extend-netgear-network.html

Belkins defualt IP address is 192.168.2.1

The gateway shows the ip address of the Netgear modem. The Belkin is just tethered for log in access.Try logging in to the Belkin with the Netgear off...I tried logging in with my laptop internet switch off. I get the old no internet connection. It is like it does not know the router is connected even though it shows communications during a ping of the ip address.

JoeAre both the Belkin and the Netgear set for DHCP? If so, there's your problem.