dlink router WBR-1310 forgets password

Just upgraded the firmware, and a new wrinkle added, the login password
gets lost somewhere. The default user and password don't work. Once I
reset to defaults with the button in back, I can login. Replace all
settings including password, everything's fine for a while, then, can't
login. This has happened twice now. Any ideas?

Not really a solution, but I have the same problem. After about a day
of uptime, it won't let me log into the configuration utility. I
believe it does recognize my password, though, because it redraws the
whole screen when I use the right one, and just blanks out the username
and password if I use the wrong one. (You probably have to have a slow
computer like mine to see the difference.) I've contacted dlink
support about this, but after about six emails, all they could
recommend was reinstalling the firmware. It didn't help.

Airman Thunderbird wrote:
> Just upgraded the firmware, and a new wrinkle added, the login password
> gets lost somewhere. The default user and password don't work. Once I
> reset to defaults with the button in back, I can login. Replace all
> settings including password, everything's fine for a while, then, can't
> login. This has happened twice now. Any ideas?

The original firmware didn't have this problem, but I can't find it
anywhere.

(E-Mail Removed) wrote:
> Not really a solution, but I have the same problem. After about a day
> of uptime, it won't let me log into the configuration utility. I
> believe it does recognize my password, though, because it redraws the
> whole screen when I use the right one, and just blanks out the username
> and password if I use the wrong one. (You probably have to have a slow
> computer like mine to see the difference.) I've contacted dlink
> support about this, but after about six emails, all they could
> recommend was reinstalling the firmware. It didn't help.
>
> Airman Thunderbird wrote:
>> Just upgraded the firmware, and a new wrinkle added, the login password
>> gets lost somewhere. The default user and password don't work. Once I
>> reset to defaults with the button in back, I can login. Replace all
>> settings including password, everything's fine for a while, then, can't
>> login. This has happened twice now. Any ideas?
>

I'd rather stick with the newer firmware anyway. Coincidentally, the
only time my router ever locked up was the morning the new firmware
became available that fixed the lockup problem.

If I really need to log into the router, I only need to cycle the
power. (Unplug it for about ten seconds.) Then I can log in normally
again. The router only takes a few seconds to boot up. Of course,
that erases the logs, so if you were logging in to check them, you're
outta luck.

Scott


Airman Thunderbird wrote:
> The original firmware didn't have this problem, but I can't find it
> anywhere.
>
> (E-Mail Removed) wrote:
> > Not really a solution, but I have the same problem. After about a day
> > of uptime, it won't let me log into the configuration utility. I
> > believe it does recognize my password, though, because it redraws the
> > whole screen when I use the right one, and just blanks out the username
> > and password if I use the wrong one. (You probably have to have a slow
> > computer like mine to see the difference.) I've contacted dlink
> > support about this, but after about six emails, all they could
> > recommend was reinstalling the firmware. It didn't help.
> >
> > Airman Thunderbird wrote:
> >> Just upgraded the firmware, and a new wrinkle added, the login password
> >> gets lost somewhere. The default user and password don't work. Once I
> >> reset to defaults with the button in back, I can login. Replace all
> >> settings including password, everything's fine for a while, then, can't
> >> login. This has happened twice now. Any ideas?
> >

Yeah, you're right. I contacted Dlink, and they said I needed to take to
a live tech. Not really worth the time or aggravation. Just wish they
had told me they were working on a fix.

Actually, mine does seem to restart more now, and it keeps telling me
about these "twinge" attacks, which I've never seen in any of my other
routers.

(E-Mail Removed) wrote:
> I'd rather stick with the newer firmware anyway. Coincidentally, the
> only time my router ever locked up was the morning the new firmware
> became available that fixed the lockup problem.
>
> If I really need to log into the router, I only need to cycle the
> power. (Unplug it for about ten seconds.) Then I can log in normally
> again. The router only takes a few seconds to boot up. Of course,
> that erases the logs, so if you were logging in to check them, you're
> outta luck.
>
> Scott
>
>
> Airman Thunderbird wrote:
>> The original firmware didn't have this problem, but I can't find it
>> anywhere.
>>
>> (E-Mail Removed) wrote:
>>> Not really a solution, but I have the same problem. After about a day
>>> of uptime, it won't let me log into the configuration utility. I
>>> believe it does recognize my password, though, because it redraws the
>>> whole screen when I use the right one, and just blanks out the username
>>> and password if I use the wrong one. (You probably have to have a slow
>>> computer like mine to see the difference.) I've contacted dlink
>>> support about this, but after about six emails, all they could
>>> recommend was reinstalling the firmware. It didn't help.
>>>
>>> Airman Thunderbird wrote:
>>>> Just upgraded the firmware, and a new wrinkle added, the login password
>>>> gets lost somewhere. The default user and password don't work. Once I
>>>> reset to defaults with the button in back, I can login. Replace all
>>>> settings including password, everything's fine for a while, then, can't
>>>> login. This has happened twice now. Any ideas?
>

Does it show these "twinge" attacks in the log? I assume you're seeing
this in the log before your router refuses to let you log in. Or is
there some other way to view or save the log?

Airman Thunderbird wrote:
> Yeah, you're right. I contacted Dlink, and they said I needed to take to
> a live tech. Not really worth the time or aggravation. Just wish they
> had told me they were working on a fix.
>
> Actually, mine does seem to restart more now, and it keeps telling me
> about these "twinge" attacks, which I've never seen in any of my other
> routers.
>
> (E-Mail Removed) wrote:
> > I'd rather stick with the newer firmware anyway. Coincidentally, the
> > only time my router ever locked up was the morning the new firmware
> > became available that fixed the lockup problem.
> >
> > If I really need to log into the router, I only need to cycle the
> > power. (Unplug it for about ten seconds.) Then I can log in normally
> > again. The router only takes a few seconds to boot up. Of course,
> > that erases the logs, so if you were logging in to check them, you're
> > outta luck.
> >
> > Scott
> >
> >
> > Airman Thunderbird wrote:
> >> The original firmware didn't have this problem, but I can't find it
> >> anywhere.
> >>
> >> (E-Mail Removed) wrote:
> >>> Not really a solution, but I have the same problem. After about a day
> >>> of uptime, it won't let me log into the configuration utility. I
> >>> believe it does recognize my password, though, because it redraws the
> >>> whole screen when I use the right one, and just blanks out the username
> >>> and password if I use the wrong one. (You probably have to have a slow
> >>> computer like mine to see the difference.) I've contacted dlink
> >>> support about this, but after about six emails, all they could
> >>> recommend was reinstalling the firmware. It didn't help.
> >>>
> >>> Airman Thunderbird wrote:
> >>>> Just upgraded the firmware, and a new wrinkle added, the login password
> >>>> gets lost somewhere. The default user and password don't work. Once I
> >>>> reset to defaults with the button in back, I can login. Replace all
> >>>> settings including password, everything's fine for a while, then, can't
> >>>> login. This has happened twice now. Any ideas?
> >

Yeah, that's the weird thing. Occasionally, I can get in the router. And
yes, the twinges are in the log.

(E-Mail Removed) wrote:
> Does it show these "twinge" attacks in the log? I assume you're seeing
> this in the log before your router refuses to let you log in. Or is
> there some other way to view or save the log?
>
> Airman Thunderbird wrote:
>> Yeah, you're right. I contacted Dlink, and they said I needed to take to
>> a live tech. Not really worth the time or aggravation. Just wish they
>> had told me they were working on a fix.
>>
>> Actually, mine does seem to restart more now, and it keeps telling me
>> about these "twinge" attacks, which I've never seen in any of my other
>> routers.
>>
>> (E-Mail Removed) wrote:
>>> I'd rather stick with the newer firmware anyway. Coincidentally, the
>>> only time my router ever locked up was the morning the new firmware
>>> became available that fixed the lockup problem.
>>>
>>> If I really need to log into the router, I only need to cycle the
>>> power. (Unplug it for about ten seconds.) Then I can log in normally
>>> again. The router only takes a few seconds to boot up. Of course,
>>> that erases the logs, so if you were logging in to check them, you're
>>> outta luck.
>>>
>>> Scott
>>>

I just checked mine, and it had two twinge attacks. It's been running
all day, and both twinge attacks were in the past hour. What a
coincidence. BTW, I rebooteded it today, I guess that's why I can
still log into it.

Airman Thunderbird wrote:
> Yeah, that's the weird thing. Occasionally, I can get in the router. And
> yes, the twinges are in the log.
>
> (E-Mail Removed) wrote:
> > Does it show these "twinge" attacks in the log? I assume you're seeing
> > this in the log before your router refuses to let you log in. Or is
> > there some other way to view or save the log?
> >
> > Airman Thunderbird wrote:
> >> Yeah, you're right. I contacted Dlink, and they said I needed to take to
> >> a live tech. Not really worth the time or aggravation. Just wish they
> >> had told me they were working on a fix.
> >>
> >> Actually, mine does seem to restart more now, and it keeps telling me
> >> about these "twinge" attacks, which I've never seen in any of my other
> >> routers.
> >>
> >> (E-Mail Removed) wrote:
> >>> I'd rather stick with the newer firmware anyway. Coincidentally, the
> >>> only time my router ever locked up was the morning the new firmware
> >>> became available that fixed the lockup problem.
> >>>
> >>> If I really need to log into the router, I only need to cycle the
> >>> power. (Unplug it for about ten seconds.) Then I can log in normally
> >>> again. The router only takes a few seconds to boot up. Of course,
> >>> that erases the logs, so if you were logging in to check them, you're
> >>> outta luck.
> >>>
> >>> Scott
> >>>

The D-link rep I talked to acted like nobody else had reported the
problems with logging into the router after about a day of uptime. I
wonder if we can narrow down what we have in common that makes ours act
this way. I've changed the default IP address of the router, because
that address is already taken on my network. I've also changed the
admin username and password, but I've seen another post from someone
who experimented with that, and it didn't make any difference. I have
external ping responses disabled. I have gaming mode disabled.

(E-Mail Removed) wrote:
> I just checked mine, and it had two twinge attacks. It's been running
> all day, and both twinge attacks were in the past hour. What a
> coincidence. BTW, I rebooteded it today, I guess that's why I can
> still log into it.
>
> Airman Thunderbird wrote:
> > Yeah, that's the weird thing. Occasionally, I can get in the router. And
> > yes, the twinges are in the log.
> >
> > (E-Mail Removed) wrote:
> > > Does it show these "twinge" attacks in the log? I assume you're seeing
> > > this in the log before your router refuses to let you log in. Or is
> > > there some other way to view or save the log?
> > >
> > > Airman Thunderbird wrote:
> > >> Yeah, you're right. I contacted Dlink, and they said I needed to take to
> > >> a live tech. Not really worth the time or aggravation. Just wish they
> > >> had told me they were working on a fix.
> > >>
> > >> Actually, mine does seem to restart more now, and it keeps telling me
> > >> about these "twinge" attacks, which I've never seen in any of my other
> > >> routers.
> > >>
> > >> (E-Mail Removed) wrote:
> > >>> I'd rather stick with the newer firmware anyway. Coincidentally, the
> > >>> only time my router ever locked up was the morning the new firmware
> > >>> became available that fixed the lockup problem.
> > >>>
> > >>> If I really need to log into the router, I only need to cycle the
> > >>> power. (Unplug it for about ten seconds.) Then I can log in normally
> > >>> again. The router only takes a few seconds to boot up. Of course,
> > >>> that erases the logs, so if you were logging in to check them, you're
> > >>> outta luck.
> > >>>
> > >>> Scott
> > >>>

I'm not near the router right now, and of course I can't log in 'cause
it's acting up, but I forwarded this message to myself and Monday I'll
check settings. I do know I changed the IP to 192.168.1.1, and I have
internet access enabled. All I can remember about non-defaults.

(E-Mail Removed) wrote:
> The D-link rep I talked to acted like nobody else had reported the
> problems with logging into the router after about a day of uptime. I
> wonder if we can narrow down what we have in common that makes ours act
> this way. I've changed the default IP address of the router, because
> that address is already taken on my network. I've also changed the
> admin username and password, but I've seen another post from someone
> who experimented with that, and it didn't make any difference. I have
> external ping responses disabled. I have gaming mode disabled.
>