Router Woes

Thag · Post by **Thag** » 2007-11-10 12:14pm

For the last two weeks, I've been trying to get a router working without success. It's a D-Link Rangebooster G, and I haven't even been able to access it's configuration utility. Using the software that came with it only gives me cryptic error codes (wtf is error 109?), resetting the router doesn't appear to do anything, going to 192.168.0.1 gives me an 'unable to display page' screen, and last night I found out that it wasn't even assigning the computer an IP address when I plugged it in. Their tech support hasn't helped at all, and I'm ready to either try to return it or take out my hammer. Does this sound like something that can be fixed, or is the router toast?

Xenophobe3691 · Post by **Xenophobe3691** » 2007-11-10 01:36pm

I thought it was 192.168.1.1, with a 1 in the third set. At least, that's what my router requires.

Thag · Post by **Thag** » 2007-11-10 02:21pm

According to the manual and the tag on the bottom it's 0.1. Although, one of my friends did try 1.1, and got the same result.

Bounty · Post by **Bounty** » 2007-11-10 02:23pm

I'm assuming you're connecting to the router directly during setup (ie, with a cable, not via wireless)?

Thag · Post by **Thag** » 2007-11-10 02:46pm

Yes. I've connected it directly to both my desktop and laptop.

Uraniun235 · Post by **Uraniun235** » 2007-11-10 02:58pm

Xenophobe3691 wrote:I thought it was 192.168.1.1, with a 1 in the third set. At least, that's what my router requires.

This varies depending on how the router is set up.

Luke Starkiller · Post by **Luke Starkiller** » 2007-11-10 03:09pm

I had what sounds like the same thing happen to me a while back, with the same router I think; D-Link's Tech support was able to help me with it. I kept a log of what they had me do, I'll pull it up and post it after work

brianeyci · Post by **brianeyci** » 2007-11-10 03:10pm

Time to hijack.

I need a low ping router under 100 bucks. Or free. Anybody who has one, with demonstrated low ping if it's a used one or has a recommendation for a new one... I really do not feel like paying 120 bucks for the latest gaming router, and I'm relatively sure good routers exist out there (even with no wireless support I couldn't give a shit about wireless) which do not add a 300 ms ping overhead to every fucking game or flash out every ten seconds.

I have a DI-524 right now and it's pretty disgusting: I can confirm it by plugging in directly to the Internet and getting low ping, compared to plugged into the router. I set up to demilitarized zone for my computer and it doesn't seem to help.

phongn · Post by **phongn** » 2007-11-10 04:09pm

You probably have a defective router if it's adding 300ms overhead. No router should ever do that.

Thag · Post by **Thag** » 2007-11-10 08:28pm

Luke Starkiller wrote:I had what sounds like the same thing happen to me a while back, with the same router I think; D-Link's Tech support was able to help me with it. I kept a log of what they had me do, I'll pull it up and post it after work

Great! All I was able to get from the tech support was a "check the faq" e-mail and an indian guy whose phone kept dropping out.

Luke Starkiller · Post by **Luke Starkiller** » 2007-11-10 08:34pm

Ok, here's what I had to do when my WBR-2310 wouldn't assign an IP.

Download the newest firmware from D-Link with the router bypassed.
Connect the PC back up to the Router and set Static IP settings: IP: 192.168.0.52, Gateway 192.168.0.1, Subnet: 255.255.255.0
Browse to 192.168.0.1, it gave a prompt for the location of the firmware on my PC
Once the firmware upload was complete disconnect power from the Router for 2 minutes and set the PC back for DHCP
Reconnect the power to the router and log back in to 192.168.0.1 to configure the router

[Cover my ass Disclaimer]I don't gaurantee that this will work and as with anything with updating your firmware it has the potential to turn the router into a brick if something goes wrong.[/Disclaimer]

Thag · Post by **Thag** » 2007-11-11 11:26am

CYA noted, but since it's about as useful as a brick right now, I'll probably take a crack at it. One question, why set the computer back to DHCP? Do I need to switch it to something else to begin with?

Netko · Post by **Netko** » 2007-11-11 01:58pm

DHCP is used for dynamic allocation of IP addresses so by setting your IP address statically to 192.168.0.x you'll be turning it off.

Thag · Post by **Thag** » 2007-11-11 06:58pm

Well, I gave it a shot. I was able to go from limited connectivity to full connectivity, but it still wouldn't accept 192.168.0.1 as a valied address in IE. So, thanks for the help everyone, but it looks like it's time for the router place-kick.

Braedley · Post by **Braedley** » 2007-11-11 08:20pm

I was just going to ask if you were using IE. Another stupid question, have you checked your firewall settings (if you're using a software firewall)?

Thag · Post by **Thag** » 2007-11-11 09:03pm

Yeah, I use Zonealarm, but I've shut it down before each attempt. Windows firewall was killed as soon as I got the system.

Netko · Post by **Netko** » 2007-11-12 04:06am

Thag wrote:Well, I gave it a shot. I was able to go from limited connectivity to full connectivity, but it still wouldn't accept 192.168.0.1 as a valied address in IE. So, thanks for the help everyone, but it looks like it's time for the router place-kick.

Did you try resetting it to factory defaults? There should be a small hole on it where you stick something like a toothpick and wait until the lights start blinking (or some similar procedure - check the manual). I've been having occasional problems with my cheapo ISP issued router that force me to sometimes do such a reset (its uPnP capabilites die, and sometimes it even winds up in a state similar to what you have).

Thag · Post by **Thag** » 2007-11-12 06:22pm

I've tried the reset a couple times on previous attempts, but I didn't do it right before the firmware try. Maybe that'll work, although there hasn't been any change in the lights on the front when I've done it before. I would think something would a happen.