PDA

View Full Version : comp not seeing router


ericm88
February 19th, 2007, 08:29 AM
I recently installed an entirely new hardware set up (mobo, CPU, PSU and GPU) and for some unknown reason my computer will not see my router. However, if i connect directly to my DSL modem everything is fine. Windows has been installed on a completely fresh HD as well, and I have most, if not all upgrades BEFORE SP2.

Motherboard: Asus A8N32-SLI DX
CPU: AMD X2 4400+
OS: Windows XP SP1

Router: SMC Barricade 7004ABR

What I Have tried...

Connecting in all 4 ports of router - does not work
Connecting directly to my DSL modem (accessible internet)
I have NOT tried changing the ethernet cords, as it would be a huge hassle.. they come from my floor - also, as it works with the modem they should work.
I have also tried connecting with all my firewalls turned off.. Still no luck.
When I try to "ipconfig /renew" while connected to the router I get a message saying ...an error occured renewing... : unable to contact your DHCP server. Request timed out. When pinging the router address I get "Destination host unreachable" x4 and then it quits.

Network...

COnnection: DSL
Modem: D-Link
Router: SMC Barricade 7004ABR (wired)
Other PCs: I have one other PC networked in the basement - it works fine - my old system worked just fine as well.


Hopefully this is enough info to get some ideas rolling.. Let me know what you guys think. Thanx :)

degsy
February 19th, 2007, 10:21 AM
Welcome :)

Is your PC getting an IP address at all?
Do you have it set to get an IP Automatically?

Have you tried entering a static IP?

ericm88
February 19th, 2007, 04:00 PM
Thanks for the reply :)

My PC does get an IP, but it seems to be ghosted.. It doesn't actually exist. I can't get the exact number right now, but I remember that the gateway was 255.255.0.0 which seems odd..

It should be picking up an IP automatically, yes.

..and I have tried with a static IP.

When I go to ipconfig /release under the ghost IP, it will not release properly.. maybe that will help.

degsy
February 19th, 2007, 05:55 PM
You cannot use /release or /renew if you have a static IP.
You need to input all the details manually.

ericm88
February 19th, 2007, 06:21 PM
Yes I know that.. It's not supposed to give me a static IP, it SHOULD be dynamic, but it can't even ping to the router.

Another thing worth mentioning is that I had it working SOMEHOW sunday morning. I then shut off the computer when I left for work. Turned it on when I got home and it didn't work anymore.. No idea why...

oink
February 19th, 2007, 10:32 PM
Do you know what the default ip fpr the router is? If knowing the default ip for the router, have you tried resetting it to factory with the reset button in the rear? (I assume that one has that feature) Have you tried the router with the modem not plugged in to either the computer or router?

ericm88
February 19th, 2007, 11:50 PM
I don't know what the IP for the router is.. Is that the ip that I put into the address bar to go to it's options? I have not tried resetting my router to factory default yet either. I have, however, tried the router without the modem and tried the modem without the router - the latter of the two works. This makes me believe it's a problem between router and my board... although I have no idea what it is.

degsy
February 20th, 2007, 10:12 AM
You can get the router details from the manual or from the PC that is connected.

ericm88
February 21st, 2007, 08:10 AM
Alright, so I've fixed the problem...

I called both the distributor of my motherboard and my router. They were no help. Decided to talk to a techi at work... after an hour of testing, he said my router may be too old to run with the motherboard... sure enough i went out and got a new D-Link and everything is great!

Thanks for the help you guys.. I'll be back soon with a question on setting up my second hard drive. :)

You're awesome!

degsy
February 21st, 2007, 10:22 AM
after an hour of testing, he said my router may be too old to run with the motherboard.
That is not the problem. The protocols used have changed for decades.
Could be a faulty router, but most probably just had a glitch that could have been fixed.


Glad you got it sorted though :)

bmiller292
February 22nd, 2007, 04:23 PM
older routers did not have the firmware that is necessary nowadays to do proper configuration, I.E:port forwarding, remote access. our router/surfboard at work through charter communications hinders us from changing anything, hence why we're installing a router behind it to give us more access.