IDNetters Forums

Technical News & Discussion => IDNet Help => Topic started by: houseparty on Nov 14, 2006, 13:20:25

Title: too all
Post by: houseparty on Nov 14, 2006, 13:20:25
hi
anyone have a disconnection anout 10 mins ago?

thanks
Title: Re: too all
Post by: Thar on Nov 14, 2006, 13:31:46
Connection dropped at 13:23 for me but was up again within a minute or so.
Title: Re: too all
Post by: Bill on Nov 14, 2006, 13:34:09
Mine dropped at about 1:10 >:(, came back up a few minutes later
Title: Re: too all
Post by: houseparty on Nov 14, 2006, 13:35:40
Quote from: Thar on Nov 14, 2006, 13:31:46
Connection dropped at 13:23 for me but was up again within a minute or so.

yes wasnt off for long, but i was wondering if it was my end no not, as i thought these problems where fixed now.

thanks for repling
Title: Re: too all
Post by: Bill on Nov 14, 2006, 13:43:22
According to my time sync program, it looks like I had a drop about 12:45 as well.
Title: Re: too all
Post by: BassoProfundo on Nov 14, 2006, 13:50:24
Odd, according to my router logs, no disconnects seen here.
Title: Re: too all
Post by: Nerval on Nov 14, 2006, 13:52:49
No, no drop here either.
Title: Re: too all
Post by: cavillas on Nov 14, 2006, 14:36:30
No drop here either.
Title: Re: too all
Post by: stevelondon on Nov 14, 2006, 14:38:26
None here either
Title: Re: too all
Post by: golden on Nov 14, 2006, 15:18:06


none here
Title: Re: too all
Post by: Meerkat on Nov 14, 2006, 15:29:54
Me also - authentication failure at 13.23.40  -  and re-authentication at 13.26.51!!
Title: Re: too all
Post by: Rik on Nov 14, 2006, 16:02:28
I was down at 13:20:56 for 8 seconds. Curious that there's such a timing spread...
Title: Re: too all
Post by: Simon_idnet on Nov 14, 2006, 16:30:41
Hi All

There have not been any events within our network to cause any connections to drop.

If anyone is experiencing prolonged difficulties please contact Support and we'll test your line for you.

Regards
Simon
Title: Re: too all
Post by: Rik on Nov 14, 2006, 16:36:21
Thanks for the reassurance, Simon. It looked too time-spread to be an IDNet issue, just BT playing with jumpers again.  :)