fsckin router

Ok so lately ive been having problems with the comcast connection, alot of you know that. thats not the issue though, under the suggestion of comcast (heh) and alot of you, i decide to try another, known good, router.

Buddy has the exact same one (belkin 4 port, love this thing). My router has never given me problems. But anyway. I unhook the cat cables and power to the router, and pull the power plug on the modem.

I swap in the other router, exact same router mind you, and hook everything back up. I fire it up, net is working fine. Just like it wass on the other router.

First thing i notice is that my WAN ip has changed, but i expected that because a few months back i RMA'd my router and the new one did the same thing. Other than that, my ip never changes.

So i go to the router addy, 192.168.2.1. Comes up no prob and i login under the fault password. I go straight to the gateway settings and allow pass for my Webserver and my FTP (80 and 2593).

After applying the settings i shoot to the DHCP settings. I set the start point to 192.168.2.20. I do this because i have about 5 computers that i need to specify ip's for, and i use .2 and up. I just start the dhcp pool at 20 to keep it a ways away from mine, as i also have a few comps that need to aquire auto. But, my setup wont matter.

I save these settings, and suddenly its not loading. So i go to yahoo.com, internet works great. On all pc's, except, i can no longer get to 192.168.2.1 anymore.....

So i reset the router physically, no dice. Any ideas why it would do that? I'm going to keep toying with it.

So you have static IPs set up? Assuming you're running Windows, could you copy and paste the output of 'ipconfig /all' please?

sure can, each one shows the printout for the pc its run on only though. Its always been that way, even when i had the old router on. Give me a few minutes though, ive somehow gotten it to come up on my dads (an auto ip comp) so im going to upload my old defaults and see if they all come online.

Maybe it's due to your forwarding port 80 to a different computer. When you try to access the router's webserver, it's forwarding the request to the other machine. Just a thought.

Problem solved. The router isnt the same, its the same router FIVE firmware releases prior. See the router was given to him un-opened a few months back from someone who found it in their new apartment, and didnt need it.

He doesnt know anything so he just used it without ever logging into it for setting changes. So the internet works great, but that particular release was actually RECALLED for defective hardware.

Since i still think it could be my router i am going to make staples return my belkin, third time, third router, and get linksys. I love linksys products, never give me attitude.

Thnx for the quick replies though.

Quote:

---

Originally Posted by bithub

Maybe it's due to your forwarding port 80 to a different computer. When you try to access the router's webserver, it's forwarding the request to the other machine. Just a thought.

---

the routers access page doesnt run off of port 80. And that wouldnt have made sense, seeing as how i was using the same (so we thought) router with the same settings.

O well, its "fixed' now.

You're not running a domain at your house are you?

nah, its fixed now

ok just checking because I had the exact some problem at work and it's because routing and remote access was not set up with dns correctly...anywho, glad it worked out.