You usually talk to/setup the DLink routers by connecting to the default gateway IP address (192.168.0.1 by default ). Not sure what happened, but I'd try to talk to your router with the gateway that you gave us ( 24.198.80.0 ).
The IP addresses you're now receiving appear to be coming directly from RoadRunner (24.198.80.63/netmask 255.255.240.0/gateway 24.198.80.0, etc.)
So it's as if your DI-604 is no longer functioning as a router, but as a hub! You didn't by chance plug the Ethernet cable to the cable modem into one of the LAN connectors on the DI-604 instead of the WAN connector? That's about the only way you'd be getting IP addresses from RoadRunner instead of from the DI-604!
Since the IP address of the DHCP server doesn't match the gateway address, it looks like RR's happily handing out a whole bunch of IP addresses through your newly reincarnated
HUB??? *Very* strange. As far as what IP address the router may have obtained, you may be able to guess based on the IP addresses the PCs received. If the PCs are all consecutive, try one IP address less than the lowest one, or one address more than the highest one. Since the netmask is larger than a Class C (255.255.240.0, or /20, giving 4094 useable IP addresses), finding the thing by brute force could be daunting!
Interestingly, if I traceroute to the listed gateway from here, the traceroute ends successfully with IP address 24.25.160.90, DNS name pos1-0.ptldmesac-ubr01.nyroc.rr.com. So that's apparently some sort of aggregation device belonging to RoadRunner.
"If it was just a hub you could see my computer, at least I would think you could." Agreed. But if the pattern of open ports matched that of the D-Link, would you know? From a security standpoint, Gibson's data says things are OK. Did you check all the IP addresses assigned to the PCs?
This is
really odd. That D-Link's certainly acting like an access point!
(edit) Given when this started, a slightly fried D-Link's a possibility. But what an interesting failure mode!
I also have a DI-604 router. You usually talk to it to make settings changes by typing 192.168.0.1 in the address bar of internet explorer. What I was saying is to type the IP address of the default gateway that you gave us in the address bar of IE to try and talk to it.
If that doesn't work, here is how to reset the router to the factroy settings that it shipped with:
Reset
Used to restore the DI-604 back to factory default settings.
LAN
PORTS
1-4
LAN port sockets (CAT5 Ethernet RJ-45 cable). The LED
glows steadily when a port is connected to a hub, switch or
network-adapter-equipped computer in your local area network
(LAN.)
WAN
WAN port socket (CAT5 Ethernet RJ-45 cable). This is where
you will connect your Cable or DSL modem.
Power
Connect one end of your included power adapter to the power
port and the other end into your power outlet.
Reset
To reset the system settings to factory defaults, please follow these steps:
1. Leave the device powered on, do not disconnect the power
2. Press the reset button and hold (use a paper-clip)
That is what I thought too. I even went to Steve Gibson's site to see if the firewall in the router was still working and all but one port is closed or stealth, so I figured the router was still working. If it was just a hub you could see my computer, at least I would think you could. The wirers are all plug into the right places. My DHCP Server and DNS Server have changed to RR too, so I would say it is acting as a hub, but I do not know what that really means because everything is still working, at least right now. I am posting a link to my ipconfig /all, a screen shot. To big to post.
Charlye,
I do not understand what you mean by talk to my router? I can not get to the web based configurer at 192.168.0.1 because my current IP Address is not in the same reange. D-Link had me manually insert all the right numbers and I still could not connect to or ping 192.168.0.1 to change anything.
Yes it is an interesting "failure mode". The IP are not consectutive but I tried one lower and I got a message "server root". I will test the other two IP at Gibson's and see. Thanks for the replies, if it changes I will post back.
Edit- I checked the other machines and they are not "stealth" , I was mistaken about the first one too. Everything is closed but I can be seen from the internet, so I would say this router has failed.
I tried going to the gateway I have and nothing same as the 192.168.0.1 . Thanks for the reset directions, D-Link tech had me try it but it did not reset, but I read on another site that a poster had to hold the reset button for longer then 10-20 seconds for it to work. I may try again, but I had to mess up what is working now. thanks for your in put.
I tried another reset, held it for 45 seconds, it didn't reset. I have come to the conclusion it is fried. I know what you mean about the saying thanks!!!
I was mistaken about the first one too. Everything is closed but I can be seen from the internet, so I would say this router has failed.
Agreed. What an amazingly strange way to fail! RR usually only issues *one* IP address per cable modem, so you may have a uniquely capable ex-router! Maybe you can sell it on EBay?
(edit)
Everything is closed... That probably means it's OK to leave things connected until you get the router replaced. I was worried that the internal machines that were formerly protected by NAT in the router were now open to the Internet, but (oddly) that doesn't appear to be true.
Wow guys! This thread has just been fun to read! It got my attention because I have the same router and have had some strange problems of my own, but this one was really interesting! Thanks!
Something that I learned a long time ago is that it's important to take problems as seriously as the situation warrants...but no more! That was definitely an interesting problem!
Marvin,
You might want to consider getting a UPS for the replacement router. They're not a panacea, but they'll help keep strange surges out of the equipment they're protecting. We had a windstorm a few years back that knocked a tree into a power pole near us. The lights grew brighter, then dimmer, and finally went out completely. We lost two UPSs, but nothing that they were protecting was damaged.
charlye
102 Posts
0
January 11th, 2004 00:00
You usually talk to/setup the DLink routers by connecting to the default gateway IP address (192.168.0.1 by default ). Not sure what happened, but I'd try to talk to your router with the gateway that you gave us ( 24.198.80.0 ).
Let us know what happens.
Charlye
jwatt
4.4K Posts
0
January 11th, 2004 00:00
The IP addresses you're now receiving appear to be coming directly from RoadRunner (24.198.80.63/netmask 255.255.240.0/gateway 24.198.80.0, etc.)
So it's as if your DI-604 is no longer functioning as a router, but as a hub! You didn't by chance plug the Ethernet cable to the cable modem into one of the LAN connectors on the DI-604 instead of the WAN connector? That's about the only way you'd be getting IP addresses from RoadRunner instead of from the DI-604!
Jim
jwatt
4.4K Posts
0
January 11th, 2004 01:00
Since the IP address of the DHCP server doesn't match the gateway address, it looks like RR's happily handing out a whole bunch of IP addresses through your newly reincarnated HUB??? *Very* strange. As far as what IP address the router may have obtained, you may be able to guess based on the IP addresses the PCs received. If the PCs are all consecutive, try one IP address less than the lowest one, or one address more than the highest one. Since the netmask is larger than a Class C (255.255.240.0, or /20, giving 4094 useable IP addresses), finding the thing by brute force could be daunting!
Interestingly, if I traceroute to the listed gateway from here, the traceroute ends successfully with IP address 24.25.160.90, DNS name pos1-0.ptldmesac-ubr01.nyroc.rr.com. So that's apparently some sort of aggregation device belonging to RoadRunner.
"If it was just a hub you could see my computer, at least I would think you could." Agreed. But if the pattern of open ports matched that of the D-Link, would you know? From a security standpoint, Gibson's data says things are OK. Did you check all the IP addresses assigned to the PCs?
This is really odd. That D-Link's certainly acting like an access point!
(edit) Given when this started, a slightly fried D-Link's a possibility. But what an interesting failure mode!
Jim
Message Edited by jimw on 01-10-2004 07:37 PM
charlye
102 Posts
0
January 11th, 2004 01:00
I also have a DI-604 router. You usually talk to it to make settings changes by typing 192.168.0.1 in the address bar of internet explorer. What I was saying is to type the IP address of the default gateway that you gave us in the address bar of IE to try and talk to it.
If that doesn't work, here is how to reset the router to the factroy settings that it shipped with:
Reset
Used to restore the DI-604 back to factory default settings.LAN
PORTS
1-4
LAN port sockets (CAT5 Ethernet RJ-45 cable). The LED
glows steadily when a port is connected to a hub, switch or
network-adapter-equipped computer in your local area network
(LAN.)
WAN
WAN port socket (CAT5 Ethernet RJ-45 cable). This is whereyou will connect your Cable or DSL modem.
Power
Connect one end of your included power adapter to the powerport and the other end into your power outlet.
Reset
To reset the system settings to factory defaults, please follow these steps:
1. Leave the device powered on, do not disconnect the power
2. Press the reset button and hold (use a paper-clip)
3. Keep the button pressed about 10 seconds
4. Release the button
The DI-604 will then automatically reboot itself.
Marvin P
1.3K Posts
0
January 11th, 2004 01:00
Jim,
That is what I thought too. I even went to Steve Gibson's site to see if the firewall in the router was still working and all but one port is closed or stealth, so I figured the router was still working. If it was just a hub you could see my computer, at least I would think you could. The wirers are all plug into the right places. My DHCP Server and DNS Server have changed to RR too, so I would say it is acting as a hub, but I do not know what that really means because everything is still working, at least right now. I am posting a link to my ipconfig /all, a screen shot. To big to post.
Charlye,
I do not understand what you mean by talk to my router? I can not get to the web based configurer at 192.168.0.1 because my current IP Address is not in the same reange. D-Link had me manually insert all the right numbers and I still could not connect to or ping 192.168.0.1 to change anything.
Link to ipconfig /all screen shot;
http://home.maine.rr.com/marvinp/ipconfig%201_10_04.jpg
Message Edited by Marvin P on 01-10-2004 10:02 PM
Marvin P
1.3K Posts
0
January 11th, 2004 02:00
Jim,
Yes it is an interesting "failure mode". The IP are not consectutive but I tried one lower and I got a message "server root". I will test the other two IP at Gibson's and see. Thanks for the replies, if it changes I will post back.
Edit- I checked the other machines and they are not "stealth" , I was mistaken about the first one too. Everything is closed but I can be seen from the internet, so I would say this router has failed.
Message Edited by Marvin P on 01-11-2004 12:15 AM
Marvin P
1.3K Posts
0
January 11th, 2004 02:00
Charlye,
I tried going to the gateway I have and nothing same as the 192.168.0.1 . Thanks for the reset directions, D-Link tech had me try it but it did not reset, but I read on another site that a poster had to hold the reset button for longer then 10-20 seconds for it to work. I may try again, but I had to mess up what is working now. thanks for your in put.
Marvin P
1.3K Posts
0
January 11th, 2004 03:00
Charyle,
I tried another reset, held it for 45 seconds, it didn't reset. I have come to the conclusion it is fried. I know what you mean about the saying thanks!!!
charlye
102 Posts
0
January 11th, 2004 03:00
Sorry I couldn't help. Hope you get it worked out...
Thanks for saying thanks, most aren't polite enough to say anything.
Charlye
jwatt
4.4K Posts
0
January 11th, 2004 04:00
Agreed. What an amazingly strange way to fail! RR usually only issues *one* IP address per cable modem, so you may have a uniquely capable ex-router! Maybe you can sell it on EBay?
(edit) Everything is closed... That probably means it's OK to leave things connected until you get the router replaced. I was worried that the internal machines that were formerly protected by NAT in the router were now open to the Internet, but (oddly) that doesn't appear to be true.
Jim
Message Edited by jimw on 01-10-2004 10:17 PM
Marvin P
1.3K Posts
0
January 12th, 2004 00:00
Jim,
Called DLink Tech. back and I am returning the Router/Hub ! Thanks for all your input. Nice to know you cam find help on these boards.
jwatt
4.4K Posts
0
January 12th, 2004 02:00
Jim
lincat442
1 Message
0
January 14th, 2004 16:00
Marvin P
1.3K Posts
0
January 14th, 2004 21:00
lincat442,
It has been interesting if nothing else :-) . Hopefully the new DLink will work better and longer.
jwatt
4.4K Posts
0
January 14th, 2004 22:00
Something that I learned a long time ago is that it's important to take problems as seriously as the situation warrants...but no more! That was definitely an interesting problem!
Marvin,
You might want to consider getting a UPS for the replacement router. They're not a panacea, but they'll help keep strange surges out of the equipment they're protecting. We had a windstorm a few years back that knocked a tree into a power pole near us. The lights grew brighter, then dimmer, and finally went out completely. We lost two UPSs, but nothing that they were protecting was damaged.
Jim