Strange Problem

[Dan Sgambelluri]

I have a D-Link WBR-1310 Wireless Router

I am able to connect to the internet throughout the whole day but I am
unable to connect to the internet in the morning after a few hours on
inactivity. I am able to connect to the internet if the cable goes from
the modem to the computer's nic card. I can after a few seconds
connected from the modem to the nic card and than transfer the cable
from the modem to router and than put back the cable from the router to
the nic card, it works fine.

Is there a setting that I am forgetting to change so the router does not
do this because it will be a pain to do this every single day? I had to
do this for the 3 mornings I had this router.

Thanks
Dan

 

[Barry Watzman]

This is usually a sign of a bad router, when they need to be reset
periodically.

 

[Dan Sgambelluri]

This is usually a sign of a bad router, when they need to be reset
periodically.

just to be sure, you said a bad router like a bad batch or bad router
like router series is crap and get a different type?

Thanks
Dan

 

[Barry Watzman]

Bad router as in your particular router is no longer totally reliable.
This does not mean that another router of the exact same model would
necessarily have the same problem.

However, my one-year failure rate with the low cost routers has been
terrible, I've gone through one to two dozen since I started doing this
in the late 1990's. I've had more problems with Linksys than with
D-Link, and while I used to recommend Linksys, I no longer am able to do
so. I see both failures "out of the box", and also what is more
troubling is failures that develop after 3 to 12 months. These are not
"hard failures" .... the routers work, superficially. But they "lock
up" and need to be reset periodically (anywhere from every few hours to
every few days). If a router can't work reliably for weeks at a time
without locking up and needing to be reset, it has a problem. And this
kind of unreliability is especially unacceptable if you have Internet
phone service (as we do).

 

[SPD]

Before you scrap the router, have your ISP check your modem for resets. My
network was experiencing the same symptoms. Two routers later, I called the
cable company and they reported my 6 year old Toshiba was resetting 300
times a day according to their logs.

 

[Dan Sgambelluri]

Before you scrap the router, have your ISP check your modem for resets. My
network was experiencing the same symptoms. Two routers later, I called the
cable company and they reported my 6 year old Toshiba was resetting 300
times a day according to their logs.

What did your ISP do after you contacted them. Did the replace the
modem, fixed
the modem from their end, have a tech come to your place to fix it?
Was your modem bought or rented?

Thanks
Dan

 

[Dan Sgambelluri]

Bad router as in your particular router is no longer totally reliable.
This does not mean that another router of the exact same model would
necessarily have the same problem.

However, my one-year failure rate with the low cost routers has been
terrible, I've gone through one to two dozen since I started doing this
in the late 1990's. I've had more problems with Linksys than with
D-Link, and while I used to recommend Linksys, I no longer am able to do
so. I see both failures "out of the box", and also what is more
troubling is failures that develop after 3 to 12 months. These are not
"hard failures" .... the routers work, superficially. But they "lock
up" and need to be reset periodically (anywhere from every few hours to
every few days). If a router can't work reliably for weeks at a time
without locking up and needing to be reset, it has a problem. And this
kind of unreliability is especially unacceptable if you have Internet
phone service (as we do).

Do you recommend any non cheap low cost wireless router?

Thanks
Dan

 

[Colin Wilson]

I have a D-Link WBR-1310 Wireless Router

I am able to connect to the internet throughout the whole day but I am
unable to connect to the internet in the morning after a few hours on
inactivity.

I'll start by saying i'm no expert :-}

Check for the IP lease length time - you might need to bump it as high
as possible

There may be a setting to drop the connection after a period of
inactivity - have a good look around the settings !

It sounds like the computer itself isn't connecting, rather than the
router being an issue here - almost as if it isn't using the wireless
side by default until its managed to get "out" via the NIC - not sure
what you might be able to check to try to force it to connect via
wireless though :-(

Rather than connecting the modem to the computers' NIC, how about trying
to connect it to a port on the router, and go into the config from
there, see if it thinks its connected at that stage.

 

[Dan Sgambelluri]

I'll start by saying i'm no expert :-}

Check for the IP lease length time - you might need to bump it as high
as possible

It says 10080 minutes. I change it to all 9s and see if that helps.

There may be a setting to drop the connection after a period of
inactivity - have a good look around the settings !

I hope that is it but I can't find it.

It sounds like the computer itself isn't connecting, rather than the
router being an issue here - almost as if it isn't using the wireless
side by default until its managed to get "out" via the NIC - not sure
what you might be able to check to try to force it to connect via
wireless though :-(

Rather than connecting the modem to the computers' NIC, how about trying
to connect it to a port on the router, and go into the config from
there, see if it thinks its connected at that stage.

I don't understand, can you explain it even easier terms.
I connect the cable modem to the router than to the computer's NIC first
and it works fine until the morning than it does not work. I than
unplug the modem cable that is connected to the router and plug it into
the computer's NIC after I removed the cable that is connect from the
router to the computer's NIC. I am able to get onto the net. I can than re
I do not have wireless on my computer's NIC. It is a wired one.



Thanks
Dan

 

[Colin Wilson]

I don't understand, can you explain it even easier terms.

I connect the cable modem to the router than to the computer's NIC first
and it works fine until the morning than it does not work. I than
unplug the modem cable that is connected to the router and plug it into
the computer's NIC after I removed the cable that is connect from the
router to the computer's NIC. I am able to get onto the net. I can than re
I do not have wireless on my computer's NIC. It is a wired one.

Apologies (and for the cross posting, i`m in alt.sys.pc-clone.dell so
i'll restrict my posts to that group after this one) if I misunderstood
your position - I thought you had a wireless PC / laptop, but it
wouldn't connect wirelessly unless you first connected via direct cable
connection.

I'm afraid my answer to this is short - not a clue :-}

 

[MZB]

Barry:

I wonder if this is a newer phenomenon. I've had my router for about 18
months and only once did i have to reset it.

Mel

 

[Dan Sgambelluri]

Apologies (and for the cross posting, i`m in alt.sys.pc-clone.dell so
i'll restrict my posts to that group after this one) if I misunderstood
your position - I thought you had a wireless PC / laptop, but it
wouldn't connect wirelessly unless you first connected via direct cable
connection.

I'm afraid my answer to this is short - not a clue :-}

I just got my wireless laptop today, however the problem is for my wired
computer for now, we will see tomorrow if my laptop has this problem as
well.

Thanks though
Dan

 

[Jay B]

it doesnt sound like this problem is being diagnosed properly.
you say you "cannot connect to the internet" but that is clearly not
enough info for anyone to go on.
when you have this condition, you must shell out to a dos prompt, and
check your ip address. by issuing ipconfig/all
and tell us those numbers there.
if you dont have an ip address, that is one problem,
if you dont have a gateway, or dhcp server or dns server, that will also
keep you from getting out to the internet.

if you do have an ip address, then connect to your router at the gateway
address, and check the status from that point.

i would also reset the router back to factory. it should work with
factory settings.
dont mess with the dhcp timeout settings. longer is always better.

it is also possible that you programmed scheduled periods that the
router would not work for parental control purposes.

it could be almost anything.

 

[Dan Sgambelluri]

it doesnt sound like this problem is being diagnosed properly.
you say you "cannot connect to the internet" but that is clearly not
enough info for anyone to go on.
when you have this condition, you must shell out to a dos prompt, and
check your ip address. by issuing ipconfig/all
and tell us those numbers there.
if you dont have an ip address, that is one problem,
if you dont have a gateway, or dhcp server or dns server, that will also
keep you from getting out to the internet.

if you do have an ip address, then connect to your router at the gateway
address, and check the status from that point.

i would also reset the router back to factory. it should work with
factory settings.
dont mess with the dhcp timeout settings. longer is always better.

it is also possible that you programmed scheduled periods that the
router would not work for parental control purposes.

it could be almost anything.

I will do ipconfig/all the next time it does that and see what it gives me.

I have reseted the router a couple times.

I haven't seen any programmed scheduled periods settings but that would
go away by taking out the cable from the router and put it computer and
than a few seconds later put it back to the router and have it working
again.

Thanks
Dan

 

[hoerschy]

Bad router as in your particular router is no longer totally reliable.
This does not mean that another router of the exact same model would
necessarily have the same problem.

However, my one-year failure rate with the low cost routers has been
terrible, I've gone through one to two dozen since I started doing this in
the late 1990's. I've had more problems with Linksys than with D-Link,
and while I used to recommend Linksys, I no longer am able to do so. I
see both failures "out of the box", and also what is more troubling is
failures that develop after 3 to 12 months. These are not "hard failures"
.... the routers work, superficially. But they "lock up" and need to be
reset periodically (anywhere from every few hours to every few days). If
a router can't work reliably for weeks at a time without locking up and
needing to be reset, it has a problem. And this kind of unreliability is
especially unacceptable if you have Internet phone service (as we do).

I had just the other problem. Because my model was D-Link, I thought that I
would stick with them for the router. Over a 2 day period of time, I went
through 3 routers that did not work. I talked with technical support for
each of them and the techs said that the router was the problem. Picked up
a Linksys WRT54G and it worked like a charm. It actually set itself up with
a CD. Never had a problem with it in the 2 years that I used it. I have
heard that setting up wireless networks can be a pain, but is wasn't with
the Linksys.

 

[Dan Sgambelluri]

I will do ipconfig/all the next time it does that and see what it gives me.

I have reseted the router a couple times.

I haven't seen any programmed scheduled periods settings but that would
go away by taking out the cable from the router and put it computer and
than a few seconds later put it back to the router and have it working
again.

Thanks
Dan

Quarter to 7 in the morning and and it works. Hopefully it works when I
get back from work.