Computing.Net > Forums > Networking > 192.168.0.1 won't connect

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

192.168.0.1 won't connect

Reply to Message Icon

Name: exetik
Date: November 23, 2007 at 03:59:07 Pacific
OS: XP
CPU/Ram: P III
Product: DI-524
Comment:

Hey, I really need help on this: I have 2 routers, first is connected directly into the net, 2nd router is D-Link DI-524 wireless and connects to the 1st router mentioned. the thing is that I want to set a password to the D-link and for some reason I can't access it, the default IP should be 192.168.0.1 but it won't respond to it.
Iv'e tried going to CMD ipconfigq tracert 4.2.2.4 and basicly got no new info on this issue.
I also looked up in the net to figure some different default IP prohaps and nada, it won't respont to any of my attempts.
I should mention that my laptop connects perfectly to the router itself and I can surf the net, I just can't get into it's control panel for some reason

Plzzzzzzzzzzzzz help




Sponsored Link
Ads by Google

Response Number 1
Name: WebsWonder
Date: November 23, 2007 at 06:04:58 Pacific
Reply:

Use the IP address that your WiFi Card uses as the default gateway.........


0

Response Number 2
Name: mountain
Date: November 23, 2007 at 06:55:51 Pacific
Reply:

router ip's are always 192.168.1.1
dsl modems are 192.168.0.1


0

Response Number 3
Name: StuartS
Date: November 23, 2007 at 07:06:28 Pacific
Reply:

>> router ip's are always 192.168.1.1 <<

Not necessarily so. You can make a routers IP any address you want it to be with in the private address range. Different manufactures come with different default addresses. Most use 192.168.1.1, some use 192.168.0.1 and I have even had one with 10.0.0.1. You need to read the manual to find the default address.


Stuart


0

Response Number 4
Name: XpUser
Date: November 23, 2007 at 07:17:50 Pacific
Reply:

I agree with Stuart. There is no such thing as one default IP address for all make of routers. Examples are:

Linksys routers use 192.168.1.1

D-Link & and Netgear routers typically use 192.168.0.1

Some US Robotics routers use 192.168.123.254

Some SMC routers including Belkin uses 192.168.2.1

and so on.

The bottom line is always read the router documentation.


i_Xp/VistaUser


0

Response Number 5
Name: DarthOdor
Date: November 25, 2007 at 19:29:33 Pacific
Reply:

You've probably set the wireless router to bridge mode in order for it not to nat data ip addresses. You described a collaped backbone configuration with two routers running on a single IP. The correct thing to do is to use the wireless router as a bridge, which disables nat'ing-- in effect the wireless just established communications at the network layer level. The IP's are assigned by the router up front (assuming DHCP is in use) and not the nat inside of the wireless router. That's really the only big difference between a switch and a router. The drawback is that your wireless router won't allow you access to it's configuration utility which you may need access to in order to change the encryption type (if you've recently bought a PSP and found out that it's wireless connections requires an older type of encryption. Otherwise, there's not much need to access the wireless router. I would decide what you want to set up, go back to factory default on the wireless-set it up, reset bridge mode and forget it. When you have one router with an internet IP and the other connected to it set in bridge mode, then you won't be able to access the configuration of the second router after enabling bridge mode, unless you do a factory reset and then go into the configuration from scratch, as bridge mode removes that option and it also removes nat'ing of which you don't want anyway because you already have a router natting for you, up front.



0

Related Posts

See More



Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Networking Forum Home


Sponsored links

Ads by Google


Results for: 192.168.0.1 won't connect

192.168.0.1, no thanks www.computing.net/answers/networking/19216801-no-thanks/20233.html

Unable to access 192.168.0.1 www.computing.net/answers/networking/unable-to-access-19216801/33023.html

wireless card won't connect to Net www.computing.net/answers/networking/wireless-card-wont-connect-to-net/17805.html