I am reminded again how much I liked Insight before Comcast bought them.
As much trouble as I've had since then I suspected foul play. I'm pretty
sure my router is bad because past experience tells me it should work
without any user config from me. Too bad my modem doesn't serve any DHCP
or it would have worked plugged into my LAN. Until a couple days ago
extending all the way back to when I first installed this router (1996)
all my boxes connected to the Internet and that includes the one running
PCLinuxOS Tiny Me. Since my modem is working and not caching the MAC
addy it must be a router malf. Thanks again.
DHSinclair wrote:
Stan,
I'm gonna snip and inline below.............. :)
At 13:21 01/26/2009 -0600, you wrote:
DHSinclair wrote:
Stan,
I have been following your thread since the beginning. Sorry not to
jump in until now.
Not a problem man. :-)
snip
Seemed to work because I didn't get any error messages but with my
router between the cable modem and my 4 boxes none of them will
connect. I have to unplug my modem ethernet cable from the router and
hook it direct to my main machine to send this email.
Tougher question! Do you know whether your Cable Modem has a DNS
Server running inside it? If so, this might be a
complication.......When the router does a reset; like anytime it
looses power and reboots, it will call out for an IP Addy. If your
modem is happy and using DNS, it will happily grant your router a
(?new?) IP Addy. OK, fine. This is how those little IC chips work!
All good so far; the modem assigned a lease to the router and is
happy. The router is happy cuz it can talk to the modem with its' NEW
IP Addy. The problem now is, nobody below the router yet knows the IP
Addy of the ROUTER. AND, the router will NOT answer any calls to it
unless the IP ADDY address is matched.............. :(
I do not recall completely ATM, but there is a cmd prompt routine that
can be use to query the router from a machine to SEE what its' NEW IP
Addy may be! Easier is just to admin (log into) the router and it has
to show you what its' LAN-SIDE IP Addy IS! This YOU HAVE TO KNOW!
Once you know what the LAN-SIDE IP Addy of the router is, just go to
each machine and PUT that IP Addy into the GATEWAY field
(CP-Network-TCP/IP Properties). Once, all the machines again know
WHERE on the LAN the router is, they will all settle up and again have
access THRU the router to the Modem and out to the WWW.
Well, that's my view, and, I'm sticking to it; cuz it werkz here in
the woods of NW Georgia!
This tells me that your router is just borked up. Either, it does not
have the MAC addy of your primary machine "spoofed/masqueraded" on
its' WAN side, or, it has lost where it is at. Do you tell your
clients (machines) to point to your router's ip address as their
GateWay address?
See, your "modem" still knows who you are and is still willing to talk
to you (well the machine you used to send your last reply)! I suspect
that Comcast assigned; or, has records of the MAC addy you chose (or
they chose) when you set your account up. I had to do this with
Verizon years ago, and, I suspect that AT&T does this in the
background. Att&T only allows ONE machine per account per their
TOA!...............Hello, NAT router!!
You need to do some admin work at your router to fix this, locally, if
you are up to it. Or, as you say, your router just could be toast;
and the fix will be a new router! (I can suggest the DL-4300, though
it does have more bells and whistles than a dog has fleas!)
snip
I love computer hardware but when it comes to networking I choke.
Thats the beauty of a router for me. It's plug-n-play simplicity with
DHCP handling all the esoteric stuff. Back when I used ZoneAlarm I
often had to go into settings and give it specific IP's and Subnet
Mask's to get connections with my other boxes. Needless to say, I
don't use ZoneAlarm anymore.
Not to worry. Network stuff can be very simple, or, very, very
difficult and obtuse. Everything I know about "Networking" came to me
from the Collective. Every book I ever bought put me into nappy-time!
ZoneAlarm and their ilk are personal, local, firewall sw packages. I
use none of them. I do not even use the default Windows XP internal
firewall.......OOH! OOH!........Do your other machines have the
Windows FireWall ACTIVE? IF so, disable it. Then disable System
Restore. Reboot the machine.
Let it try and reconnect with the router. Then, if you need to, turn
the Windows FW back on!
snip
I use a D-Link DI-604 and the last firmware is dated 2004 and I have
probably been using it since 2006. I've heard of DMZ and NAT but so
much of networking seems confusing to me. I've read and read but this
is one of those areas where the theory and reality clash. I need to
go back to school. <g>
Please go to either DLink and/or the DLSReports web page and check to
see if there is a NEWER F/W for your router (by m/n). You could be so
F/W behind that the router is now just "Stupid." It is not broken; it
is just not quite able to get its' head out of its' arse! Perhaps a
simple F/W update to your router may fix this whole miasma.
If your router's F/W is up-2-date and you just can NOT admin it to get
"stuff" to work/flow, then perhaps the router is toast. It does happen.
Yes, networking can easily be confusing. The answers to the most
plebeian question will be answered here in the Collective. If
"nothing" else, this Collective does KNOW networking. You get to
choose how complex your course syllabus will be! LOL!
My Pleasure. I finally get to give a bit back..................... :)
Best,
Duncan
snip
