Can't access the Dlink router admin page.
 

I searched for a thread like this for awhile, but found nothing so forgive me if I'm repeating a topic.

Anyways, I'm running Suse 9.2 on a T40 IBM Thinkpad and I have a Dlink 514 router. The router worked great on my Windows PC, but I wanted to set it up with the laptop, and the laptop has yet to go online. For some reason though, I can't seem to login to the admin page on the router. I've set the network card to a static IP of 192.168.0.2, I've turned off the software firewall, and reset the Router, but everytime I try to type 192.168.0.1 into Konqueror, it gives me an error "Can't access host" or some nonsense. Any ideas are greatly appreciated.

Don't use a static IP. Let the device give you one through dhcp...

Thanks for your response.
But when I had that enabled, the DHCP wouldn't give it one. I should state that the router isn't connected to the internet, but right now I just want to configure the router, and it doesn't have to be connected to the internet to login to the admin page, right?

I just called the Dlink support phone number, and the only thing they could suggest was trying the static IP of 192.168.0.99 and a gateway of 192.168.0.1, but that didn't work either.

Please help!

Are your sure that the router has this IP address? In Brazil, the D-Link routers came with the 10.0.0.1 IP addresses by default, just like the Alcatel ones...

Disconnect your machine from internet. Connect an ethernet cabled from your laptop to ur router. Power on both ur laptop and router. Try connecting it thru browser. If it is still not working ,


1. Make sure that ur router's modem was not configured to some other IP address. Try for a hardware reset to "Factory defaults"

2. Do the command /sbin/route -n and make sure that your dont have any conflicting routes to ur hardwired modem.

Hi,

To connect to the DI-514 router for setup you should use a direct link via a cat5 cable from your NIC(laptop) to a LAN port of the router. From a terminal window first su then;

ifconfig eth0 192.168.0.2
route add default gw 192.168.0.1
ifconfig eth0 up
ping 192.168.0.1

Of course this assumes that the correct driver has been loaded for your NIC and that it is functioning!

You should do any admin of your router with a direct link for security reasons. Don't forget to change your default password for the router.

From a browser you should use the 192.168.0.1 address to access the router.

If this still fails, provide the output of;

relative ports of dmesg

ifconfg -a

route -n

HTH!

Thank you all for your responses.

Unfortunately, nothing has worked yet. And I'm pretty sure I have the driver for the NIC installed, Yast thinks that the card is completely configured so I assume it is. This is so very puzzling.

Alright, I don't know what I did, but now when I ping 192.168.0.1, I get this:

64 bytes from 192.168.0.1: icmp_seq=70 ttl=255 time=0.486 ms
from 192.168.0.2: icmp_seq=100 Destination host unreachable
from 192.168.0.2 icmp_seq=100 Destination host unreachable
from 192.168.0.2 icmp_seq=104 Destination host unreachable
64 bytes from 192.168.0.1: icmp_seq=105 ttl=255 time=351 ms
64 bytes from 192.168.0.1: icmp_seq=106 ttl=255 time=0.531 ms
64 bytes from 192.168.0.1: icmp_seq=107 ttl=255 time=0.524 ms
64 bytes from 192.168.0.1: icmp_seq=108 ttl=255 time=0.562 ms
from 192.168.0.2 icmp_seq=137 Destination host unreachable

and it goes on like that for awhile, but I thought those few "64 bytes from 192.168.0.1" were significant.

What information is significant in ifconfig -a, and route -n?

If you get this type of ping requests you have:

a) a bad cable
b) a defective router(port)
c) a defective nic or wrong driver

If you used the same cable and router(port) connecting your windows pc use lspci to let us know what brand of nic you are using

It's an IBM Pro/1000 MT Mobile Connection.

Perhaps I don't have the driver installed, but would having Yast think the card is configured mean that I DO have the driver installed?

Accessing Dlink router
 

Even under windows Xp some Dlink routers could only be acessed
by using Internet Explorer i.e Mozilla and Firefox wouldn't
work. This was because you could only accesss the router in
browsers that supported openX. Is there a later software
update for your router, if so you may need to load it. This is
best done with a wired connection and windows XP using IE.

Funny you should mention that.
I never had a problem with my old (I said *old*) D-link 714P, but I just put in a Linksys.

Could get to the admin page from FF, but half the screen was missing - couldn't do the setup. Had to go find an old Win2K latop with IE6 to get it configured.
But at least I could talk to the router - don't know what the OPs problem is.

Thanks everyone for your replies, or at least attention to the thread.
I thought about a browser incompatibility, but I can't ping it either.

Ibm has certified the hardware in relation to suse desktop 9 (see link)
http://developer.novell.com/yes/79872.htm
So it must be a hardware problem.