• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Do routers go bad??

MrPhelps

Golden Member
I have a D-Link DI-704p and I can ping it from the two machines hooked up to it and the ip and submask is correct, but when I go to the web based set up I only see 00000's for all adresses.

I can go directely from my cable modem in to one computer and get online.


In did reset the router.

Any help would be great. thanks🙁
 
Do you mean the WAN address listed is showing all zeroes, but the LAN address lists the proper IP for your internal network? Some cable providers require you to register the MAC address of the device that will be connected to the cable modem (AT&T Broadband did, Comcast took over their network and no longer seems to require it). If you're only showing all zeroes, then that indicates that your router's WAN port is unable to get an IP address from the cable network DHCP servers. This may be because the network doesn't have the router's MAC address registered, or you may need to unplug the cable modem for a minute or so before connecting the new router to it in order to clear out any cached information.

Also, you do have the cable modem connected to the proper port on the router, yes? And you're not using a crossover Ethernet cable between the router and the modem? (Try using a different cable if you're not sure.)
 
There is a mac address but no lan or wan. I have it hooked up correct and I swapped cables. Both computers can ping the router but through the router I can't get online. With the cable hooked to one computer I can get online.

I took my router to my friends house and it failed also so it looks like its router time.

I reset my cable modem and the router.

Thanks for you help.🙂
 
I had the same problem, though I didn't remember until it happened again today. Power down your cable modem, router, and PC. Turn on the cable modem with NO PCs or the router connected. Give it time to sync (At least a minute or two). Then connect the router and power it on. It should come alive. Give it about 20 seconds and then turn on the client machine. I've had to do it this way in this order at home and at work.

At home, the router refused to even "see" my Internet connection if I plugged it in after powering the router up. The cable modem must have the power cycled and be on first so that it can do what it needs to do as soon as it turns on. The cable modem needs to be reset because it may be associated with your network card's MAC address and it will reassociate with the next MAC when you cycle it (Unless your ISP restricts it to one NIC, which is what the MAC cloning option in your router setup is for).

At work, I was configuring my router and disabling the wireless options before connecting it (They certainly don't want rogue access points here). When I connected it, the "WAN" and "Internet" lights wouldn't "go live" until I shut everything down and booted the router first. It came back up instantly. Everything was "00000" just like you said before doing so.
 
CZroe
Thanks for the info, I tried it but it didn't work. I am going to get the microsoft router from office depot using coupons. It'll end up costing me $20/$25 so I'll have to bite the bullet.

Thanks
 
YES, SOHO routers go bad sometimes. At around $30 a pop, sometimes more and sometimes less, they're heavily cost optimized and something's gotta give -- namely quality. As far as I can tell, all of the cheap SOHO routers are about the same in this respect, though Linksys AC power bricks seem to fail notably more often than others.

If you spend more money and get something like a ZyXEL box, you should get better reliability. But you may find that buying multiple "disposable" cheaper boxes is still more cost effective.
 
It's unlikely that the router has actually gone bad, though I have had one Netgear's internal LAN ports go bad. More likely you're going to run into the same issues because the MAC address is the problem, not the router itself.
 
I bought the Microsoft router and the #1 slot stopped working for a couple minutes so I returned it. Now I need to buy a router.

Any suggestion??? I still don't want to spend alot. maybe $30/50
 
You never did address the issue of whether your ISP is using registered MAC addresses. Did the MS router actually get an IP when you connected it? Or did you never get a chance to find out? If it didn't get an IP, then the MAC address is your issue and you either need to clone your computer's MAC address or have your ISP register the MAC from the router.
 
Thanks for the reply, I don't know enough to answer. The help I got was from a friend who is in th IT field/networking. As for registering the Mac address with the cable company no I haven't, they would know I am using multiple computers and charge me for it.


The Microsoft router worked fine except port #1 went bad. So I assume it had to get a ip from my cable modem.


Thanks and sorry I don't know more.

 
I had the Linksys 1 port router switch which go bad, and two of my friends had the linksys 4 port switch router which went bad twice for each of my friends. I guess we are the lucky ones, so we stay away from Linksys. However I think my Netgear MR314 is going bad..........maybe that is why the router is so cheap now......=D
 
Eh, I had 2 Linksys BEFSR41 routers that just seemed flaky, no matter what firmware version, so I ditched my own for a Netgear RT314 that I was happy with (the other Linksys was for someone else who doesn't use the net much). The Netgear's LAN ports died a year or so later, and I ended up just buying another one that's worked fine since then.
 


Frankly, I think Dlink Router sucks. I also think it's bad idea to have firewall built in router. I m having some difficulties to acces in some wesbite.... I m trying to figure how to set it up correct.. I need to use netmeeting but cant use it cuz of router.

 
Originally posted by: WoofyJr
Frankly, I think Dlink Router sucks. I also think it's bad idea to have firewall built in router. I m having some difficulties to acces in some wesbite.... I m trying to figure how to set it up correct.. I need to use netmeeting but cant use it cuz of router.

I must contradict here, and say that 1) I like Dlink routers (I'll explain why), and b) built in firewalls can be beneficial with broadband.

I like Dlink routers because they just seem to work. I've not used many brands, I'll admit that - but I did have a Linksys router once, and it would freeze up constantly, or just lose the connection. Dlink routers never seemed to do that - it'll keep a steady connection for days or weeks it seems. Now yes, my first Dlink router, DI-701, did die unexpectedly - it just would power on, but only the power LED would light up, and nothing else would happen. That's why I bought the Linksys, only to find it didn't seem to work well at all. I'm now using a Dlink DI-704, and it's been working perfectly since I got it.

I've never had any problems with the firewall in the 704 either; the 701 did present some problems with establishing direct connections in AOL Instant Messenger, at least I am fairly sure it was a problem on my end, but I never was entirely sure. Having a firewall built in too is helpful, since many users may not be aware of the possible security risks of having an unshielded computer that's always connected to the Internet. Yes, routers may have some flaws, and once the company decides to discontinue the product, it becomes more vulnerable, as any existing exploits will remain, but that can happen with software as well. I think that even a little protection can be better than none at all.
 
To the going bad question...

EVERYTHING goes bad in this field. Routers, backplanes, blades, NICs, cables, ports, X-connects, connectors. Eventually, it'll all fail. Question is, when? And what exactly caused it.
 
Back
Top