Please help, having problems setting up this Dlink router

[LoStZ]

Hi guys, can someone help me out setting up this router? I'm having a little problem. I plugged in the cable modem into the router then the 2 cat cables into each of the PC. Then I did winipcfg and released and then renewed. But still I wouldn't be able to connect to anything. I checked the lights on the router and it seemed normal. And also how do you get to the Dlink Web Configuration page? The IP that the instructions gave was 192.168.0.1, but that site is like dead. Anyways, can someone please help me out and get this working as I'm trying to set this up for my cousin. Thanks alot.

This is the DI-704 model btw.

 

[MillionaireNextDoor]

What a coincidence.. I'm have the same EXACT problem with the same EXACT equipment. However, 192.168.0.1 works for me. In the device status, it shows that there is no link between the cable modem and the router even though a wire connects both. The problem rests with the router, I've discovered since the cable modem works for one computer and switching wires did nothing. I need to have 3 computers hooked up to the router.

I seek answers and may have to call d-link people up tomorrow morning.

 

[MillionaireNextDoor]

Oh, and resetting to factory default does nothing. Right now, the cable modem is connected directly to this computer. I'm very happy with AT&T since I called in an order last night and AT&T had it installed this morning while the nice tech guy left behind a free cable modem, all for $20 for 3 months plus $10 installation, month-to-month plan.

 

[LoStZ]

Hmm what a major bummer. Guess I gotta call tech support tom morning *sighs*

 

[MillionaireNextDoor]

bump!

 

[cellan]

Arg! Same problem here. I can't find a # to call DLINK either. Anyone who has succesfully hooked up the 704 wish to help? Thanks.

 

[MillionaireNextDoor]

LoStZ got it to work. I sold mine for a profit and bought a linksys 4-port router for $45 instead.

 

[manly]

If the clients successfully configure themselves using DHCP to the router, then you can hit 192.168.0.1

You suggest this is the case, but then the web interface should be working if it were! The first test you should try on any new network is pinging the other host (in this case the router): ping 192.168.0.1

If ping isn't responding, then the basic settings are incorrect. After renewing the DHCP lease, what does winipcfg say?

One alternative to try is static addressing on one of the machines:

IP: 192.168.0.10 (or anything besides .1)
Netmask: 255.255.255.0
Gateway: 192.168.0.1

You can ignore DNS settings for the time being. This test is just so that you can check whether the clients can hit the router web admin. Try to read some basic TCP/IP networking info if you have a chance; it can be helpful.