Funny router behavior

[T. R. Oglodyte Moderator Find all posts View Profile Close T. R. Oglodyte]

This one has me totally stumped.

Yesterday morning I was replying to a thread at TUG, I had posted a reply, then decided to edit my reply. I clicked on "advanced" to open the full featured editing window. At that point, the tab went into never-never land; the page never loaded and eventually returned an error. The same things started then started happening with any page I attempted to load from tug2.net or tugbbs.com. tug1.net worked fine.

All other web sites and web pages worked fine. The only sites that wouldn't load are tug2.net and tugbbs.com.

*****

Now, if I bypass the router and connect the modem directly to the computer, tug1.net and tugbbs.com load just fine. The only time I have a problem is if the traffic goes through the router. And it's only those sites.

I checked the router settings to see if there were any screens or controls. Nothing. No web pages of any type are blocked. I reinitialized the router and repeated the installation. No change at all.

*****

Anyone out there have any ideas as to what might be going on with my router???

[JLB Please excuse me, I'm a Dick. Not a moron just a Dick Find all posts View Profile Close JLB]

Once when I was on TUG, the next time I went to Post, I had gone to Never Never Land, too.

[bigfrank Administrator Find all posts View Profile Close bigfrank]

It's a hint

[bnoble Senior Member Find all posts View Profile Close bnoble]

The only thing I can think of is that for some reason its DNS cache has a bad IP address for those TUG names. But, I would have thought a hard-restart would have cleared it.

Depending on the value of your time, the right solution might be to buy another router.

[T. R. Oglodyte Moderator Find all posts View Profile Close T. R. Oglodyte]

The only thing I can think of is that for some reason its DNS cache has a bad IP address for those TUG names. But, I would have thought a hard-restart would have cleared it.

Depending on the value of your time, the right solution might be to buy another router.

I did about five or six compete power cycles of the modem and router, including one where I shut down the entire network, to no avail.

Finally, I reset the router to factory settings, power cycled, and ran a router setup. The router kept detecting a static IP address.

After a few more power cycles didn't solve the problem, I shut down the entire network, let it sit for about one half hour, then brought the network back to life very slowly - five to ten minutes per item from the modem to my desktop. Doing manual configuration of the router, it was still reporting a static IP address. But when I ran the automatic setup routine (startup for dummies) it resolved the problems and began behaving normally. I then restarted the remaining switches and network gear, and everything seems to be operating normally now.

FWIW - it's a Netgear 3500 wireless N unit - about six weeks old. I bought it just after last Christmas when my family was here because the old router had lost range.

Actually I kept the old router - moved it to a dead location in the house and connected it to the new Netgear router with an ethernet cable. So now I run two wireless networks in the house. Which works out OK because I keep all of my business activities on one network and the personal computing goes on the other.