"Michel S." <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Hi !
>
> I have 3 computers connected using a 2 weeks old D-Link DI-624 router.
> For the moment, they are all connected using a cable, the wireless
> functions are disabled.
>
> Last time I used my network yesterday, everything was working fine.
>
> This morning, I found MSN Messenger "waiting to reconnect" dancing
> icon in my tray. On another computer, firing IE resulted on a "this
> page cannot be displayed - DNS error" message.
>
>
> I first went in my router's status to confirm that I was "connected".
> A look in the log revealed nothing unusual.
>
> I then checked with my ISP and was told that they had no problem to
> report on their side.
>
> I finally went in the router's tools tab and rebooted the modem.
> After a few seconds, my internet connection was up and running again.
>
>
> Is this what is called a "connection drop" ? It's the tird time in
> the last two weeks that it happens. Is it a known problem with the
> DI-624 ? For the last two years, I had a SMC-7004VBR and did not
> experience this kind of problem.
>
> Is there anything I can do to fix this ?
>
> BTW, the router's firmware is version 2.53 (the latest)
The next time it happens, look at your lease start and expiration times
for your dynamically assigned IP address from your ISP's DHCP server.
Maybe the problem is when your IP lease expires and you are *supposed*
to get a new one. I've seen it where the IP lease expired and the user
was reverted to APIPA addressing (which allows connecting to other
intranetwork hosts but not out to internetwork hosts); see Microsoft's
KB articles 220874 and 307287 regarding APIPA. I had to logon the
router and force it to release and renew its WAN-side IP address (which
is the IP address to which traffic gets returned from requests that you
send out). As soon as I say "ipconfig /all" show up an APIPA address
(169.254.X.X) being used by my host, I knew the IP lease renewal didn't
work. My ISP could help and didn't know why the problem occurred, but
then they don't support a user's router behavior, anyway.
I think I had this problem show up about 3 or 4 times per year and I was
using a D-Link DI-604 at the time. I'm now using a Linksys BEFSR41 but
only had it a month so I won't know if the problem gets exhibited until
a lot longer time has passed. A Google search on "+APIPA +Linksys
+BEFSR41" shows some others have experienced the problem with the
Linksys, too. Obviously my IP leases are nowhere near that long so the
problem didn't occur on every IP lease expiration but only a few times.
What I did notice a couple times is that my ISP's DHCP server was
unresponsive, so an IP lease renew operation would timeout. So if the
request times out then I suppose you get reverted to APIPA so your
intranetwork remains functional.
Rebooting the modem probably triggered your router to successfully
perform an IP lease renewal. After all, the cable modem also has its
own DHCP server (and probably from which the router gets its WAN-side IP
address) and that was where I actually would see APIPA getting used;
i.e., my router would request an IP renew but it goes to the cable
modem's DHCP server which was unable to connect to my ISP's DHCP server
so the cable modem's DHCP server was reverting to APIPA. I don't know
which cable modem you are using, but I can login to my cable modem's web
server by browsing to
http://192.168.100.1/. You could try
disconnecting the cable from your cable modem to see what LAN-side
Ethernet IP address it was using (after a reboot of it while
disconnected) and then do an IP renew at your router to see what
WAN-side IP address it got from the cable modem's DHCP server.