PDA

View Full Version : One for Jonathan 'Guru' Kay please


Ray
December 5th 03, 03:15 PM
I have the exact same problem and I recently figured out
what was causing it. I have Dlink DI-624 router and when
I reboot my computer, sometimes (frequently, but not
always) it assigns the DHCP address, then the router
reboots. I have DSL, so it drops the PPPoE connection
when the router reboots. The router only takes about 30
seconds to finish rebooting and it tries to re log into
PPPoE, but apparently my ISP is in some unknown state at
that time which will not allow a log in to happen. After
about two minutes, any packets sent to my router cause it
to try to log into PPPoE again and it is successful, so
everything works fine. DLink is currently researching
this, but they can't reproduce it. I have three XP
computers and it happens on all of them a lot (guessing
at 50% of the reboots).
So, that may or may not be your problem but it is
something to check.
Goodluck.
>-----Original Message-----
>Hi again Jon
>
>I'm having a few problems with Windows Messenger
4.7.2009 in Win XP, when
>booting. I'm running a permanently connected DG814
router and auto-login
>when I start the PC. I also use Norton Internet Security
2003.
>
>Messenger appears to try to connect then gives up. If I
then right click and
>try to connect to my account, I am presented with a
message indicating
>"Signing in to .NET Messenger Service failed because the
password is
>incorrect or the sign-in name does not exist. If you
have forgotten your
>password, click Help in the main window, and then click
Help Topics."
>[Retry][Cancel]
>
>If I subsequently re-enter the password, it connects OK.
>
>Interestingly enough, if I log out, without shutting
down and then log in
>again, Messenger connects fine, so it suggests some kind
of timing issue
>related to setting up the network when booting.
>
>Any ideas on this one - all help greatly appreciated.
>
>Regards,
>
>Russ
>
>
>.
>

Russell Higgins
December 5th 03, 03:15 PM
Hi Ray

Thanks for the ideas - I'm not really sure it's an issue for me. I've got
fixed IP addresses on the two PCs here and I'm not aware of any outages on
the router. Until the recent firmware upgrades, the router was showing
uptime, and was staying up for a couple of weeks without any disconnections.

Cheers

Russ

"Ray" > wrote in message
...
> I have the exact same problem and I recently figured out
> what was causing it. I have Dlink DI-624 router and when
> I reboot my computer, sometimes (frequently, but not
> always) it assigns the DHCP address, then the router
> reboots. I have DSL, so it drops the PPPoE connection
> when the router reboots. The router only takes about 30
> seconds to finish rebooting and it tries to re log into
> PPPoE, but apparently my ISP is in some unknown state at
> that time which will not allow a log in to happen. After
> about two minutes, any packets sent to my router cause it
> to try to log into PPPoE again and it is successful, so
> everything works fine. DLink is currently researching
> this, but they can't reproduce it. I have three XP
> computers and it happens on all of them a lot (guessing
> at 50% of the reboots).
> So, that may or may not be your problem but it is
> something to check.
> Goodluck.
> >-----Original Message-----
> >Hi again Jon
> >
> >I'm having a few problems with Windows Messenger
> 4.7.2009 in Win XP, when
> >booting. I'm running a permanently connected DG814
> router and auto-login
> >when I start the PC. I also use Norton Internet Security
> 2003.
> >
> >Messenger appears to try to connect then gives up. If I
> then right click and
> >try to connect to my account, I am presented with a
> message indicating
> >"Signing in to .NET Messenger Service failed because the
> password is
> >incorrect or the sign-in name does not exist. If you
> have forgotten your
> >password, click Help in the main window, and then click
> Help Topics."
> >[Retry][Cancel]
> >
> >If I subsequently re-enter the password, it connects OK.
> >
> >Interestingly enough, if I log out, without shutting
> down and then log in
> >again, Messenger connects fine, so it suggests some kind
> of timing issue
> >related to setting up the network when booting.
> >
> >Any ideas on this one - all help greatly appreciated.
> >
> >Regards,
> >
> >Russ
> >
> >
> >.
> >

Google