HELP: Loss of Sync / dropped connections..

[svcarter]

Since late june / July I've been suffering a increasing number of "loss of Synchronisations" / diconeections, everything used to be what I d come to expect of F2S but of late things seems to be degenerating considerabley.

Have checked all internal connections . MF's etc, rebooted router, (Netgear DG834G, re-flasehed etc,
Account: adslxxxxxxxxxx@f2sgw6
PPPoa(PPP over ATM)
Multiplex Method: VC-Based
VPI: 0
VCI: 38)


But still no joy. What is going on?)

I'm not a guru on broadband but soemthing is not right here

PLease help!

E.g. See excert from todays router log:

Sun, 2006-09-24 15:36:56 - Loss of synchronization :459 Sun, 2006-09-24 15:37:10 - Initialize LCP.
Sun, 2006-09-24 15:37:10 - LCP is allowed to come up.
Sun, 2006-09-24 15:37:26 - Loss of synchronization :460 Sun, 2006-09-24 15:38:11 - Initialize LCP.
Sun, 2006-09-24 15:38:11 - LCP is allowed to come up.
Sun, 2006-09-24 15:38:26 - Loss of synchronization :461 Sun, 2006-09-24 15:38:56 - Loss of synchronization :462 Sun, 2006-09-24 15:39:12 - Initialize LCP.
Sun, 2006-09-24 15:39:12 - LCP is allowed to come up.
Sun, 2006-09-24 15:39:56 - Loss of synchronization :463 Sun, 2006-09-24 15:40:12 - Initialize LCP.
Sun, 2006-09-24 15:40:13 - LCP is allowed to come up.
Sun, 2006-09-24 15:40:26 - Loss of synchronization :464 Sun, 2006-09-24 15:41:13 - Initialize LCP.
Sun, 2006-09-24 15:41:13 - LCP is allowed to come up.
Sun, 2006-09-24 15:41:26 - Loss of synchronization :465 Sun, 2006-09-24 15:41:56 - Loss of synchronization :466 Sun, 2006-09-24 15:42:14 - Initialize LCP.
Sun, 2006-09-24 15:42:14 - LCP is allowed to come up.
Sun, 2006-09-24 15:42:56 - Loss of synchronization :467 Sun, 2006-09-24 15:43:15 - Initialize LCP.
Sun, 2006-09-24 15:43:15 - LCP is allowed to come up.
Sun, 2006-09-24 15:43:26 - Loss of synchronization :468 Sun, 2006-09-24 15:44:16 - Initialize LCP.
Sun, 2006-09-24 15:44:16 - LCP is allowed to come up.
Sun, 2006-09-24 15:44:26 - Loss of synchronization :469 Sun, 2006-09-24 15:44:56 - Loss of synchronization :470

[acidtechno]

Please help by providing more router stats.

example of mine at the moment:

DSL Status: Up
DSL Modulation Mode: GDMT
DSL Path Mode: INTERLEAVED
Downstream Rate: 4736 Kbps
Upstream Rate: 448 Kbps
Downstream Margin: 4 db
Upstream Margin: 18 db
Downstream Line Attenuation: 53
Upstream Line Attenuation: 31

things to think about:

> local exchange a busy one , in need of upgrade ( red ) ?
> happens more at peak evening hours and weekends?
> possibly faulty router, ability to try another modem?
> tried connecting only with router plugged into test socket on bt master socket?
> possibly faulty BT hardware somewhere along the line / exchange ?

[aos101]

Originally Posted by acidtechno

> local exchange a busy one , in need of upgrade ( red ) ?

When an exchange goes red it means there is shortage of bandwidth at peak times. A shortage of bandwidth would only cause slow speeds, it wouldn't cause you to lose sync with the exchange.

I agree though router stats would be useful. The show statistics button under router status should give the line stats. Also you should remember, losing sync means your router cannot talk to your local exchange. If you are on an IPStream connection then sync is something F2S have no control over, and it will be the same with other ISPs. It is affected by the quality of your phone line and local interference, both things your ISP has no control over.

[svcarter]

Acid, thanks for interest.

After power cycling the router 3 times over an hour I've eventually got a connection (although this has already dropped (loss of synch once...)

ADSL Link Downstream
Connection Speed 3008 kbps
Line Attenuation 55 db
Noise Margin 7 db
ADSL Link Upstream
Connection Speed 448 kbps
Line Attenuation 15.5 db
Noise Margin 16 db

PPPoa(PPP over ATM)
Multiplex Method: VC-Based
VPI: 0
VCI: 38)

I dont know what else I can get, this is all from the Router.

Timing of problems seems to vary, although I use is maily in evenings / week ends.
I live in a small town, and dont belive it's very bizzy networking wise, the Exchange,
info from f2s:

BT major service outage details..
No outages have been found that may affect your connection.

Exchange capacity details: 01531631716 at LEDBURY

The capacity at the LEDBURY exchange is currently showing as Amber
This may cause speed issues on your ADSL Broadband connection

The target upgrade date for LEDBURY is: 2006-03-23
No idea if this has been done?

Historic BT outages for 01531631716

2006-01-14 18:15:00 : EDGE ROUTE SWITCH 21 MANCHESTER 4 - LOSS OF SERVICE
2005-11-16 13:46:00 : LONDON FARADAY ATM NODE 5 - PARTIAL LOSS OF SERVICE

Historic Exchange capacity details: 01531631716 at LEDBURY

Date: 2006-03-13 - Status: AMBER
Date: 2006-01-11 - Status: GREEN
Date: 2006-01-03 - Status: RED
Date: 2005-06-29 - Status: GREEN

[acidtechno]

Originally Posted by aos101

When an exchange goes red it means there is shortage of bandwidth at peak times. A shortage of bandwidth would only cause slow speeds, it wouldn't cause you to lose sync with the exchange.

oh right I see, but could a red exchange also cause a lower sync?

as for svcarter's case, his exchange is green.

Originally Posted by svcarter

ADSL Link Downstream
Connection Speed 3008 kbps
Line Attenuation 55 db
Noise Margin 7 db
ADSL Link Upstream
Connection Speed 448 kbps
Line Attenuation 15.5 db
Noise Margin 16 db

I live in a small town, and dont belive it's very bizzy

The target upgrade date for LEDBURY is: 2006-03-23
No idea if this has been done?

Your stats are similar to mine but you probably live a bit further away from your exchange than I do to mine. I also live near a small town, exchange serving 100 or so more lines than yours does.

http://www.samknows.com/broadband/search.php

That upgrade probably happened, F2S might not be totally up to date with that info.

Zen have a checker also

http://status.zensupport.co.uk/exchanges/

I put your number into there and it gives green status for previous dates.

Last date being 4th September 2006 GREEN

have you tested sync using the bt master test socket only yet?

another thing that's good to try is another modem, if you have or can borrow one.

[aos101]

Originally Posted by acidtechno

oh right I see, but could a red exchange also cause a lower sync?

as for svcarter's case, his exchange is green.

Don't think it would. Your sync speed is determined by your line quality and noise on the line, so a shortage of bandwidth at the exchange shouldn't affect that.

The F2S exchange checker has very out of date data (I don't know why they even have it on the site now, it just looks unprofessional). Also the outage checker is broken, and has been for months and months and months and ...

[acidtechno]

months and months and years and decades and centuries and ..

sorry

[svcarter]

AcidT,

Not tested from master socket as it will be a bit of a pig, having to shift router etc from upstairs to master socket which is downstatir at the the other end of the house.

Will have to wait untill I can get laptop from work, then just shift the router

Have had BB for over 2 years without the number of problems I'm getting over the last couple of months.

Went to Max ~ Feb- April of this year and it was initailly great, then late june things seem to start getting worse .
Nothing with my set up, equipment or cabling has changed at all, so feel something external must be going on?

Have been around the house checking all sockets and filters still in place and today have tried with nothing else on the telephone lines but the router, no improvement. ???? .

How can I find out if it is the line at all?

Cheers.

[acidtechno]

try and find out if any other people in your street or at least your town are suffering from the same problems you are.

I know you say nothing has changed with your equipment but there is a chance the modem has developed a fault.

About the line I think you can probably report your situation to F2S and they will have to get BT to investigate what might be causing it. I've heard that if this involves coming to your house as part of the investigation (I don't know if house also includes outside on the street) then you will be charged £50 call out if it turns out it's your fault and not BT. I'm sure you can get all the info from F2S but others here can say more on this I expect.

I know it's a pain but you will have to test everything before BT are to investigate. F2S will tell or ask if you have connected to the test socket on master for any change in performance.

[svcarter]

Acid,

Thx, I raised the problem with F2s TS last Wednesday but so far have only had an (automated) e-mail reply...
I did send an update with my growing dissatisfaction yesterday though...
I will test via master socket tonight using a laptop, and see if the routers figures are any better (will post), although of course it will benefit from another reboot in the process. And I have no earlier figures to compare it to.
The one chap I knew had broadband on the street left several months ago ( told you I lived in a small ' rural' town, shoudl keep any contention, should I ever connect, down)
Last night my session playing BF2 was dropped 5 times, it's really ******* useless!
My Concern is that it may be line and not F2S, so moving would not improve things, although this will be difficult to prove as a consumer?

Are there any usefull bits of software that can be run client-end to show where the problem / line problem is?

[John R]

Before 6th September 2004, the limits were 41dB on both 1Mbps & 2Mbps products, and 60dB for 0.5Mbps. Additionally before 24th September 2003, the 512kbps line loss limit was 55dB.

Stats relating to adsl on a line. I know they date back a bit but since MAX was introduced Bt have tightened them up again.

Line Attenuation 55 db
Noise Margin 7 db

So looking at your stats, they are not too good. Switching back to fixed speed could result in 512 or 1 meg at best. If you could get it to sync with a noise margin of 10db you might get a ore stable line, would result in lower sync, but thats is the lesser of the 2 evils....
What is your voice side like ? If it is noisy then that may well be the best way forward to see if you can get it sorted.

[acidtechno]

I'm not aware of any software that can help identify problems with your line. Your router can tell you everything you need to know usually through the browser interface.

From reading of other peoples experiences I think it is best to phone F2S to get things sorted faster than trying the e-mail support as it is not always very quick in response times, terrible really. You can PM Andrew who works at F2S who comes to this site often, he could get your situation fast tracked maybe.

http://www.freedom2support.net/forums/member.php?u=3515

John, he did say his connection using MAX was fine at first for the first couple of months, so there is no reason why he can't enjoy a MAX connection, the amount of times he is losing sync indicates a problem somewhere? it can't suddenly be his line stats.

[acidtechno]

Originally Posted by John R

If you could get it to sync with a noise margin of 10db you might get a ore stable line, would result in lower sync

Are BT able to change and set that?

[acidtechno]

Originally Posted by svcarter

I will test via master socket tonight using a laptop, and see if the routers figures are any better (will post), although of course it will benefit from another reboot in the process. And I have no earlier figures to compare it to.
The one chap I knew had broadband on the street left several months ago ( told you I lived in a small ' rural' town, shoudl keep any contention, should I ever connect, down)
Last night my session playing BF2 was dropped 5 times, it's really ******* useless!
My Concern is that it may be line and not F2S, so moving would not improve things, although this will be difficult to prove as a consumer?

Remember that to test from the master socket properly you have to unscrew the faceplate which will reveal a test socket to plug into directly.

Since the person you knew on your street with bb has left your only other option is to do a door to door if you feel brave enough to see if anyone else has got problems similar to you, but it's not necessary.

It's probably a BT issue that is causing the problems and is definitely nothing to do with F2S if it's you losing DSL/exchange sync in addition to sync to F2S, it's strange that your MAX connection was fine for a couple of months and then has been bad thereafter.

BT are the experts and should find something wrong if there is something wrong somewhere at the exchange or in the street in the pit of snakes.

BF2 is not a good game to be in to get all those disconnections loss of score, all that loading..

[svcarter]

Cheers All,

Yeah , I know I have to dismantle the wall socket to get at the required one ;-)

It too seems really strange that it was all fine for quite a while then started degenerating }:-(

I gather that SNR of 6db is the lowest limit ( although the router has shown lower than this time to time, now and in teh past, but performance seemed unaffected) It does vary, must depend on how hard the wind is blowing (although how that would affect undergroud cabling eludes me)

Given where I'm at with this and the frustration of being totaly dependant on others £50 would be small change to get back to where I was with reliability and performance.

Will carry out master socket tests tonight:
Get current stats.
Reboot router where it is, see if it's still loosing synch.
Get stats.
If so repeart using Master sckt...
see what happend and get stats from Router.

Will post

( What a way to spend a night)


If only there was a sensible way to strike up a dialogue with BT over this......


PS with BF2 yup it's a real b****r, team mates really appreciate it, particularly when you're a pilot

[acidtechno]

you're right it can go lower than 6, mine has gone down to 0 before It's underground cabling in my street area, but I've no idea if part of it is overground to get to the exchange.

There is a sensible way to get BT involved, through F2S if it is only ADSL problems.

If your voice line has problems also then I think you can contact BT directly instead of going through F2S. Which is what John mentioned but failed to clarify in his post.

[svcarter]

Voice is fine...perhaps in this case .

Will check out via master socket, and if not good will then drop a note to AndrewR as suggested.

[John R]

Originally Posted by acidtechno

If your voice line has problems also then I think you can contact BT directly instead of going through F2S. Which is what John mentioned but failed to clarify in his post.

Yep, any voice faults go staright to BT 151 i think it is... Adsl go via isp.... Better to ring them despite the cost as you can explain it a lot better, and tell them just what you have tried.

Lines can deteriate over time, and underground ones can be worse than overhead as they get flooded and eaten away by rodents.

[svcarter]

So after much effort pre, during and post use of Master socket, nothing seemed conclusive to me?

(Sorry for the long note, but I hope someone can highlight what / where the problem might be)

Odd that yesterday there were no drops until I started and use the connection?

Results below.



Wife powercycled router as it dropping conections…….

Sun, 2002-09-08 13:00:22 - Initialize LCP.
Sun, 2002-09-08 13:00:22 - LCP is allowed to come up.
Sun, 2002-09-08 13:00:26 - CHAP authentication success
Sun, 2002-09-08 13:00:35 - Send out NTP request to time-g.netgear.com
Mon, 2006-09-25 15:02:50 - Receive NTP Reply from time-g.netgear.com
Mon, 2006-09-25 15:04:20 - LCP down.
Mon, 2006-09-25 15:04:27 - Initialize LCP.
Mon, 2006-09-25 15:04:27 - LCP is allowed to come up.
Mon, 2006-09-25 15:05:27 - Initialize LCP.
Mon, 2006-09-25 15:05:27 - LCP is allowed to come up.
Mon, 2006-09-25 15:05:33 - Loss of synchronization :1
Mon, 2006-09-25 15:06:28 - Initialize LCP.
Mon, 2006-09-25 15:06:28 - LCP is allowed to come up.
Mon, 2006-09-25 15:06:31 - CHAP authentication success
Mon, 2006-09-25 15:09:01 - LCP down.
Mon, 2006-09-25 15:09:14 - Initialize LCP.
Mon, 2006-09-25 15:09:14 - LCP is allowed to come up.
Mon, 2006-09-25 15:09:33 - Loss of synchronization :2
Mon, 2006-09-25 15:10:15 - Initialize LCP.
Mon, 2006-09-25 15:10:15 - LCP is allowed to come up.
Mon, 2006-09-25 15:10:18 - CHAP authentication success
Mon, 2006-09-25 15:02:15 - Router start up
Mon, 2006-09-25 17:54:08 - LCP down.
Mon, 2006-09-25 17:54:33 - Initialize LCP.
Mon, 2006-09-25 17:54:33 - LCP is allowed to come up.
Mon, 2006-09-25 17:54:37 - Loss of synchronization :3
Mon, 2006-09-25 17:55:34 - Initialize LCP.
Mon, 2006-09-25 17:55:34 - LCP is allowed to come up.
Mon, 2006-09-25 17:55:38 - CHAP authentication success
Mon, 2006-09-25 18:07:43 - Administrator login successful - IP:192.168.0.2


System Up Time 03:06:06
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 75 63 0 9 29 00:12:40
LAN 10M/100M 1908 1584 0 102 20 03:06:02
WLAN 54M 459 0 0 11 0 03:05:52


ADSL Link Downstream Upstream
Connection Speed 3136 kbps 448 kbps
Line Attenuation 55 db 15.5 db
Noise Margin 6 db 16 db




Tuned off and moved to Master socket…..

18:46-20060925


System Up Time 00:02:34
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 71 73 0 61 103 00:02:04
LAN 10M/100M 130 0 0 202 0 00:02:30
WLAN 54M 372 366 0 973 300 00:02:20


ADSL Link Downstream Upstream
Connection Speed 3040 kbps 448 kbps
Line Attenuation 56 db 15.5 db
Noise Margin 7 db 17 db


Not exacly any great difference?


System Up Time 01:09:35
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 21281 30194 0 1095 7602 01:09:05
LAN 10M/100M 208 0 0 12 0 01:09:31
WLAN 54M 33919 24964 0 8038 1192 01:09:21


ADSL Link Downstream Upstream
Connection Speed 3040 kbps 448 kbps
Line Attenuation 56 db 15.5 db
Noise Margin 4 db 17 db



Got 3 Loss of synchs over 3 hours not bad considering…..


Post back on normal tellephone socket point, AFTER re-connecting all MFs and phones
Note without filters only got a DS of 1600, then as I added MFs and phones, on rebooting the router each time managed to get it back to the following worse than original start point !???



System Up Time 00:01:38
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 14 14 0 17 44 00:00:43
LAN 10M/100M 384 314 0 1712 423 00:01:34
WLAN 54M 73 0 0 266 0 00:01:24


ADSL Link Downstream Upstream
Connection Speed 2336 kbps 448 kbps
Line Attenuation 54 db 15.5 db
Noise Margin 7 db 16 db




Tried direct BT access using :
Username = bt_test@startup_domain
Password = (Blank)

If this authenticates, and your can browse to a single website (http://www.bt.net/digitaldemo)
Which I was able to get to , however

Sun, 2002-09-08 13:00:20 - Initialize LCP.
Sun, 2002-09-08 13:00:20 - LCP is allowed to come up.
Sun, 2002-09-08 13:00:32 - CHAP authentication success
Sun, 2002-09-08 13:00:34 - Administrator login successful - IP:192.168.0.2
Sun, 2002-09-08 13:00:35 - Send out NTP request to time-g.netgear.com
Sun, 2002-09-08 13:01:32 - LCP down.
Sun, 2002-09-08 13:01:49 - Loss of synchronization :1
Sun, 2002-09-08 13:01:49 - Initialize LCP.
Sun, 2002-09-08 13:01:49 - LCP is allowed to come up.
Sun, 2002-09-08 13:01:52 - CHAP authentication success


System Up Time 00:05:14
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 28 27 0 10 9 00:03:20
LAN 10M/100M 1323 1184 0 1894 528 00:05:10
WLAN 54M 108 0 0 116 0 00:05:00


ADSL Link Downstream Upstream
Connection Speed 2304 kbps 448 kbps
Line Attenuation 55 db 15.5 db
Noise Margin 7 db 16 db



On setting back to F2S

System Up Time 00:08:16
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 76 100 0 294 2335 00:00:40
LAN 10M/100M 2368 2010 0 2312 569 00:08:12
WLAN 54M 251 0 0 179 0 00:08:02


ADSL Link Downstream Upstream
Connection Speed 2304 kbps 448 kbps
Line Attenuation 55 db 15.5 db
Noise Margin 7 db 16 db

So cant be much to with F2S network?

After being left overnight

System Up Time 16:55:59
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 998 1199 0 20 114 02:14:43
LAN 10M/100M 16178 11982 0 237 23 16:55:55
WLAN 54M 1613 0 0 9 0 16:55:45


ADSL Link Downstream Upstream
Connection Speed 2400 kbps 448 kbps
Line Attenuation 55 db 15.5 db
Noise Margin 9 db 16 db


And

Mon, 2002-09-09 05:00:01 - Send E-mail Success!
Mon, 2002-09-09 05:55:11 - Administrator login successful - IP:192.168.0.2

No losses of Synch ?:-)

Turned router off, ~08:30 during the day,

Turned on ~ 19:20
Then got:

Sun, 2002-09-08 13:00:22 - Initialize LCP.
Sun, 2002-09-08 13:00:22 - LCP is allowed to come up.
Sun, 2002-09-08 13:00:32 - CHAP authentication success
Sun, 2002-09-08 13:00:45 - Send out NTP request to time-g.netgear.com
Wed, 2006-09-27 19:22:13 - Receive NTP Reply from time-g.netgear.com
Wed, 2006-09-27 19:26:29 - LCP down.
Wed, 2006-09-27 19:26:36 - Initialize LCP.
Wed, 2006-09-27 19:26:36 - LCP is allowed to come up.
Wed, 2006-09-27 19:27:36 - Initialize LCP.
Wed, 2006-09-27 19:27:36 - LCP is allowed to come up.
Wed, 2006-09-27 19:27:46 - Loss of synchronization :1
Wed, 2006-09-27 19:28:37 - Initialize LCP.
Wed, 2006-09-27 19:28:37 - LCP is allowed to come up.
Wed, 2006-09-27 19:28:41 - CHAP authentication success
Wed, 2006-09-27 19:21:28 - Router start up
Wed, 2006-09-27 19:46:50 - LCP down.
Wed, 2006-09-27 19:46:59 - Initialize LCP.
Wed, 2006-09-27 19:46:59 - LCP is allowed to come up.
Wed, 2006-09-27 19:47:19 - Administrator login successful - IP:192.168.0.2
Wed, 2006-09-27 19:47:46 - Loss of synchronization :2
Wed, 2006-09-27 19:47:59 - Initialize LCP.
Wed, 2006-09-27 19:48:00 - LCP is allowed to come up.
Wed, 2006-09-27 19:49:00 - Initialize LCP.
Wed, 2006-09-27 19:49:00 - LCP is allowed to come up.
Wed, 2006-09-27 19:49:04 - CHAP authentication success
Wed, 2006-09-27 19:55:43 - LCP down.
Wed, 2006-09-27 19:55:52 - Initialize LCP.
Wed, 2006-09-27 19:55:52 - LCP is allowed to come up.
Wed, 2006-09-27 19:56:47 - Loss of synchronization :3
Wed, 2006-09-27 19:56:53 - Initialize LCP.
Wed, 2006-09-27 19:56:53 - LCP is allowed to come up.
Wed, 2006-09-27 19:57:53 - Initialize LCP.
Wed, 2006-09-27 19:57:53 - LCP is allowed to come up.
Wed, 2006-09-27 19:57:57 - CHAP authentication success
Wed, 2006-09-27 20:02:17 - LCP down.
Wed, 2006-09-27 20:02:25 - Initialize LCP.
Wed, 2006-09-27 20:02:25 - LCP is allowed to come up.
Wed, 2006-09-27 20:02:37 - Administrator login successful - IP:192.168.0.2
Wed, 2006-09-27 20:03:17 - Loss of synchronization :4
Wed, 2006-09-27 20:03:26 - Initialize LCP.
Wed, 2006-09-27 20:03:26 - LCP is allowed to come up.
Wed, 2006-09-27 20:04:27 - Initialize LCP.
Wed, 2006-09-27 20:04:27 - LCP is allowed to come up.
Wed, 2006-09-27 20:04:30 - CHAP authentication success
Wed, 2006-09-27 20:15:20 - LCP down.
Wed, 2006-09-27 20:15:26 - Initialize LCP.
Wed, 2006-09-27 20:15:26 - LCP is allowed to come up.
Wed, 2006-09-27 20:16:17 - Loss of synchronization :5
Wed, 2006-09-27 20:16:27 - Initialize LCP.
Wed, 2006-09-27 20:16:27 - LCP is allowed to come up.
Wed, 2006-09-27 20:17:28 - Initialize LCP.
Wed, 2006-09-27 20:17:28 - LCP is allowed to come up.
Wed, 2006-09-27 20:17:31 - CHAP authentication success
Wed, 2006-09-27 22:45:48 - Administrator login successful - IP:192.168.0.2


System Up Time 03:25:14
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 7801 9201 0 180 889 02:29:10
LAN 10M/100M 36568 29208 0 1954 389 03:25:10
WLAN 54M 478 0 0 11 0 03:25:00


ADSL Link Downstream Upstream
Connection Speed 1856 kbps 448 kbps
Line Attenuation 55 db 15.5 db
Noise Margin 9 db 16 db

Lord knows why the speed dropped so much?

Gee I'm gettign fed up with this..............

Oh and not a sausage from the support case I raised over a week ago

[bens2short]

Did you ever get this problem sorted? I have the exact same problem with the exact same router. However if i change to my standalone modem it works fine without and loss of connection. Hope you have got it sorted and if you do let me know how you sorted it, cheers, Ben.

[svcarter]

Brief update.

LCP down, Loss of syncrhronisation numerous times an hour goes on.
Connection speed had improved from <2M to on average 2.5 - 3.4 M (given the alledged cable distance from the exchange (which I can walk to in 10 minutues) is as good as it ever was. However;
Last week-end in the pouring rain connection speed got down to 160k !!! and after the rain stopped, after several hours, increase to ~450K, purely coincindental?
However ever since then actual download speeds (between lcp drops/ loss of synchs) have been abismal, between 6 - 30 K (dear old modem is better!).

Anyway thanks to AcidT and Andy R, BT have confirmed a fault at the exchange.
Double 'however' BT/Openreach, are not going to look at it until 9th October, pretty damned poor I say. Just whish there was cable in the area.

As to the router, without having a spare I can't say weather it is it or not and am not exactly keen to spen £ replacing it just to see. Particualrly when BY have confirmed a 'fault'

I have to say I'm not impressed with not having BB for such a time

SUppose I have to wait until after the 9th (assuming BT do something) .... and see what happens.

Options, take my router to someone in a totally different area that has BB. and try it there, find someon who has a router I can borrow and try it here....

[acidtechno]

yeah would be good if you can try another router.

But with this terrible performance I'm thinking it is just a BT fault only. And since BT have admitted there is, I think you shouldn't be thinking about spending money on anything else just yet.

Sit tight and let them find and fix whatever is wrong because it's giving you continous disconnections and crappy speeds.

[svcarter]

From KITZ site have managed to get this out of the Netger:
(Dosn't mean too much to me, appart from my connection speed ( is good for me) and not interleaved !!


BusyBox v0.61.pre (2005.09.27-08:20+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

[FONT="Courier New

BusyBox v0.61.pre (2005.09.27-08:20+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

# cat /proc/avalanche/avsar_modem_stats

AR7 DSL Modem Statistics:
--------------------------------
[DSL Modem Stats]
US Connection Rate: 448 DS Connection Rate: 3168
DS Line Attenuation: 55 DS Margin: 6
US Line Attenuation: 31 US Margin: 17
US Payload : 1872 DS Payload: 3264
US Superframe Cnt : 6704 DS Superframe Cnt: 6704
US Transmit Power : 0 DS Transmit Power: 0
LOS errors: 0 SEF errors: 0
Frame mode: 3 Max Frame mode: 0
Trained Path: 1 US Peak Cell Rate: 1056
Trained Mode: 3 Selected Mode: 1
ATUC Vendor Code: 414C4342 ATUC Revision: 1
Hybrid Selected: 1 Trellis: 1
Showtime Count: 196 DS Max Attainable Bit Rate: 3168
BitSwap: 1 US Max Attainable Bit Rate: n/a

[Upstream (TX) Interleave path]
CRC: 26 FEC: 1360 NCD: 0
LCD: 0 HEC: 340

[Downstream (RX) Interleave path]
CRC: 912 FEC: 16676 NCD: 0
LCD: 0 HEC: 0

[Upstream (TX) Fast path]
CRC: 0 FEC: 0 NCD: 1
LCD: 0 HEC: 0

[Downstream (RX) Fast path]
CRC: 0 FEC: 0 NCD: 0
LCD: 0 HEC: 0

[ATM Stats]
[Upstream/TX]
Good Cell Cnt: 39
Idle Cell Cnt: 120380


[Downstream/RX)]
Good Cell Cnt: 68
Idle Cell Cnt: 829376
Bad Hec Cell Cnt: 14145
Overflow Dropped Cell Cnt: 0

[SAR AAL5 Stats]
Tx PDU's: 199410
Rx PDU's: 244173
Tx Total Bytes: 18127405
Rx Total Bytes: 258200139
Tx Total Error Counts: 0
Rx Total Error Counts: 17288


[OAM Stats]
Near End F5 Loop Back Count: 0
Near End F4 Loop Back Count: 0
Far End F5 Loop Back Count: 0
Far End F4 Loop Back Count: 0
#
#
#[/FONT]

[svcarter]

(Sorry for the long post / logs)
Well BT's Openreach person attended to the junction outside the house, saying it was a cable fault, full of water causing some 'battery contact' or some such, but as he was not a broadband engineer he could not test anything but voice (which I've not noticed any problems with).

Anyway since then, some sample data from this evening.

Still gettign drops ( )

On getting home several hours later
Had a DS speed of 3200 with snr of between 7 & 0.

A couple of disconnects see log of Mon 9-10-06 @19:44

DS Dropped to 2266, SNR 9 db


Mon, 2006-10-09 15:48:42 - Loss of synchronization :245 Mon, 2006-10-09 15:48:43 - CHAP authentication success Mon, 2006-10-09 16:17:12 - Loss of synchronization :246 Mon, 2006-10-09 16:17:23 - LCP down.
Mon, 2006-10-09 16:17:24 - Initialize LCP.
Mon, 2006-10-09 16:17:24 - LCP is allowed to come up.
Mon, 2006-10-09 16:17:28 - CHAP authentication success Mon, 2006-10-09 16:51:38 - LCP down.
Mon, 2006-10-09 16:51:44 - Initialize LCP.
Mon, 2006-10-09 16:51:44 - LCP is allowed to come up.
Mon, 2006-10-09 16:52:43 - Loss of synchronization :247 Mon, 2006-10-09 16:52:45 - Initialize LCP.
Mon, 2006-10-09 16:52:45 - LCP is allowed to come up.
Mon, 2006-10-09 16:53:45 - Initialize LCP.
Mon, 2006-10-09 16:53:45 - LCP is allowed to come up.
Mon, 2006-10-09 16:53:49 - CHAP authentication success Mon, 2006-10-09 17:11:59 - LCP down.
Mon, 2006-10-09 17:12:06 - Initialize LCP.
Mon, 2006-10-09 17:12:06 - LCP is allowed to come up.
Mon, 2006-10-09 17:12:14 - Loss of synchronization :248 Mon, 2006-10-09 17:13:07 - Initialize LCP.
Mon, 2006-10-09 17:13:07 - LCP is allowed to come up.
Mon, 2006-10-09 17:13:10 - CHAP authentication success Mon, 2006-10-09 18:47:59 - Administrator login successful - IP:192.168.0.2 Mon, 2006-10-09 18:51:50 - LCP down.
Mon, 2006-10-09 18:51:52 - Initialize LCP.
Mon, 2006-10-09 18:51:52 - LCP is allowed to come up.
Mon, 2006-10-09 18:51:55 - CHAP authentication success Mon, 2006-10-09 18:53:15 - LCP down.
Mon, 2006-10-09 18:53:17 - Initialize LCP.
Mon, 2006-10-09 18:53:17 - LCP is allowed to come up.
Mon, 2006-10-09 18:53:20 - CHAP authentication success Mon, 2006-10-09 19:15:50 - LCP down.
Mon, 2006-10-09 19:15:57 - Initialize LCP.
Mon, 2006-10-09 19:15:57 - LCP is allowed to come up.
Mon, 2006-10-09 19:16:24 - CHAP authentication success Mon, 2006-10-09 19:16:46 - Loss of synchronization :249

Rebooted just in case........

Rebooted router

System Up Time 00:01:20

ADSL Link Downstream Upstream
Connection Speed 2688 kbps 448 kbps
Line Attenuation 55 db 15.5 db
Noise Margin 6 db 17 db



Sun, 2002-09-08 13:00:22 - Initialize LCP.
Sun, 2002-09-08 13:00:22 - LCP is allowed to come up.
Sun, 2002-09-08 13:00:25 - Administrator login successful - IP:192.168.0.2
Sun, 2002-09-08 13:00:26 - CHAP authentication success
Sun, 2002-09-08 13:00:35 - Send out NTP request to time-g.netgear.com
Mon, 2006-10-09 19:44:51 - Receive NTP Reply from time-g.netgear.com
Mon, 2006-10-09 19:47:49 - Administrator login successful - IP:192.168.0.2
Mon, 2006-10-09 19:44:16 - Router start up
Mon, 2006-10-09 19:56:11 - LCP down.
Mon, 2006-10-09 19:56:22 - Initialize LCP.
Mon, 2006-10-09 19:56:22 - LCP is allowed to come up.
Mon, 2006-10-09 19:56:34 - Loss of synchronization :1
Mon, 2006-10-09 19:56:47 - CHAP authentication success
Mon, 2006-10-09 20:00:36 - LCP down.
Mon, 2006-10-09 20:00:43 - Initialize LCP.
Mon, 2006-10-09 20:00:43 - LCP is allowed to come up.
Mon, 2006-10-09 20:01:35 - Loss of synchronization :2
Mon, 2006-10-09 20:01:43 - Initialize LCP.
Mon, 2006-10-09 20:01:44 - LCP is allowed to come up.
Mon, 2006-10-09 20:02:44 - Initialize LCP.
Mon, 2006-10-09 20:02:44 - LCP is allowed to come up.
Mon, 2006-10-09 20:02:48 - CHAP authentication success
Mon, 2006-10-09 20:20:24 - UDP Packet - Source:221.209.110.48,33645 Destination:83.67.12.13,1026 - [DOS]
Mon, 2006-10-09 20:33:58 - LCP down.
Mon, 2006-10-09 20:34:06 - Initialize LCP.
Mon, 2006-10-09 20:34:06 - LCP is allowed to come up.
Mon, 2006-10-09 20:35:05 - Loss of synchronization :3
Mon, 2006-10-09 20:35:07 - Initialize LCP.
Mon, 2006-10-09 20:35:07 - LCP is allowed to come up.
Mon, 2006-10-09 20:35:25 - CHAP authentication success
Mon, 2006-10-09 20:35:56 - Administrator login successful - IP:192.168.0.2
Mon, 2006-10-09 20:40:55 - LCP down.
Mon, 2006-10-09 20:41:01 - Initialize LCP.
Mon, 2006-10-09 20:41:01 - LCP is allowed to come up.
Mon, 2006-10-09 20:42:02 - Initialize LCP.
Mon, 2006-10-09 20:42:02 - LCP is allowed to come up.
Mon, 2006-10-09 20:43:03 - Initialize LCP.
Mon, 2006-10-09 20:43:03 - LCP is allowed to come up.
Mon, 2006-10-09 20:44:03 - Initialize LCP.
Mon, 2006-10-09 20:44:04 - LCP is allowed to come up.
Mon, 2006-10-09 20:45:05 - Initialize LCP.
Mon, 2006-10-09 20:45:05 - LCP is allowed to come up.
Mon, 2006-10-09 20:46:05 - Initialize LCP.
Mon, 2006-10-09 20:46:05 - LCP is allowed to come up.
Mon, 2006-10-09 20:47:05 - Loss of synchronization :4
Mon, 2006-10-09 20:47:06 - Initialize LCP.
Mon, 2006-10-09 20:47:06 - LCP is allowed to come up.
Mon, 2006-10-09 20:47:19 - CHAP authentication success
Mon, 2006-10-09 20:51:18 - LCP down.
Mon, 2006-10-09 20:51:41 - Initialize LCP.
Mon, 2006-10-09 20:51:41 - LCP is allowed to come up.
Mon, 2006-10-09 20:52:06 - Loss of synchronization :5
Mon, 2006-10-09 20:52:42 - Initialize LCP.
Mon, 2006-10-09 20:52:42 - LCP is allowed to come up.
Mon, 2006-10-09 20:52:46 - CHAP authentication success
Mon, 2006-10-09 21:23:15 - UDP Packet - Source:221.209.110.48,54911 Destination:83.67.12.13,1026 - [DOS]
Mon, 2006-10-09 21:46:06 - LCP down.
Mon, 2006-10-09 21:46:29 - Initialize LCP.
Mon, 2006-10-09 21:46:30 - LCP is allowed to come up.
Mon, 2006-10-09 21:46:37 - Loss of synchronization :6
Mon, 2006-10-09 21:46:48 - CHAP authentication success
Mon, 2006-10-09 22:06:38 - LCP down.
Mon, 2006-10-09 22:06:46 - Initialize LCP.
Mon, 2006-10-09 22:06:46 - LCP is allowed to come up.
Mon, 2006-10-09 22:07:37 - Loss of synchronization :7
Mon, 2006-10-09 22:07:47 - Initialize LCP.
Mon, 2006-10-09 22:07:47 - LCP is allowed to come up.
Mon, 2006-10-09 22:08:48 - Initialize LCP.
Mon, 2006-10-09 22:08:48 - LCP is allowed to come up.
Mon, 2006-10-09 22:08:51 - CHAP authentication success
Mon, 2006-10-09 22:22:01 - LCP down.
Mon, 2006-10-09 22:22:09 - Initialize LCP.
Mon, 2006-10-09 22:22:09 - LCP is allowed to come up.
Mon, 2006-10-09 22:23:10 - Initialize LCP.
Mon, 2006-10-09 22:23:10 - LCP is allowed to come up.
Mon, 2006-10-09 22:23:37 - Loss of synchronization :8
Mon, 2006-10-09 22:24:11 - Initialize LCP.
Mon, 2006-10-09 22:24:11 - LCP is allowed to come up.
Mon, 2006-10-09 22:24:17 - CHAP authentication success
Mon, 2006-10-09 22:41:07 - LCP down.
Mon, 2006-10-09 22:41:33 - Initialize LCP.
Mon, 2006-10-09 22:41:33 - LCP is allowed to come up.
Mon, 2006-10-09 22:41:38 - Loss of synchronization :9
Mon, 2006-10-09 22:41:39 - CHAP authentication success
Mon, 2006-10-09 23:01:16 - Administrator login successful - IP:192.168.0.2
Mon, 2006-10-09 23:07:04 - Administrator login successful - IP:192.168.0.2



(Speed tests from ZDnet)


Your line speed:

175.6 Kbps

21.5 K bytes/sec

• download start time: 1160420665003
• download end time: 1160420688237
• download time: 23.234
• download size in thousands of bytes: 500
• estimated line speed (K bits per second): 175.6
• estimated line speed (K bytes per second): 21.5

Your line speed:

133.5 Kbps

16.4 K bytes/sec
• download start time: 1160420836112
• download end time: 1160420866675
• download time: 30.563
• download size in thousands of bytes: 500
• estimated line speed (K bits per second): 133.5
• estimated line speed (K bytes per second): 16.4


Router stats

System Up Time 00:51:17


ADSL Link Downstream Upstream
Connection Speed 2720 kbps 448 kbps
Line Attenuation 54 db 15.5 db
Noise Margin 1 db 17 db


System Up Time 00:52:01

ADSL Link Downstream Upstream
Connection Speed 2720 kbps 448 kbps
Line Attenuation 54 db 15.5 db
Noise Margin 4 db 17 db


System Up Time 00:52:39



ADSL Link Downstream Upstream
Connection Speed 2720 kbps 448 kbps
Line Attenuation 54 db 15.5 db
Noise Margin 6 db 17 db

Your line speed:

104.4 Kbps

12.8 K bytes/sec

• download start time: 1160422676065
• download end time: 1160422715128
• download time: 39.063
• download size in thousands of bytes: 500
• estimated line speed (K bits per second): 104.4
• estimated line speed (K bytes per second): 12.8

[COLOR="Blue"]Current router stats:

System Up Time 03:36:29
ADSL Link Downstream Upstream
Connection Speed 2656 kbps 448 kbps
Line Attenuation 55 db 15.5 db
Noise Margin 6 db 16 db


So things aren't exactly brilliant yet, but a bit better so far .....[COLOR]confused:

[svcarter]

Yesterday, Tuesday, when not used during the day there were no disconnections.

Current stats:

System Up Time 06:31:13
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 1593 1851 0 52 187 01:52:56
LAN 10M/100M 948 273 0 15 1 06:31:09
WLAN 54M 2569 1854 0 67 16 06:30:59


ADSL Link Downstream Upstream
Connection Speed 2144 kbps 448 kbps
Line Attenuation 55 db 15.5 db
Noise Margin 10 db 16 db


SNR Looks good, yet??



Router log from last night:

Sun, 2002-09-08 13:00:23 - Initialize LCP.
Sun, 2002-09-08 13:00:23 - LCP is allowed to come up.
Sun, 2002-09-08 13:00:28 - CHAP authentication success
Sun, 2002-09-08 13:00:28 - Administrator login successful - IP:192.168.0.2
Sun, 2002-09-08 13:00:45 - Send out NTP request to time-g.netgear.com
Sun, 2002-09-08 13:02:08 - LCP down.
Sun, 2002-09-08 13:02:37 - Initialize LCP.
Sun, 2002-09-08 13:02:37 - LCP is allowed to come up.
Sun, 2002-09-08 13:02:49 - Loss of synchronization :1
Sun, 2002-09-08 13:03:37 - Initialize LCP.
Sun, 2002-09-08 13:03:38 - LCP is allowed to come up.
Sun, 2002-09-08 13:03:41 - CHAP authentication success
Sun, 2002-09-08 13:07:18 - Send out NTP request to time-h.netgear.com
Wed, 2006-10-11 01:20:31 - Receive NTP Reply from time-h.netgear.com
Wed, 2006-10-11 01:13:13 - Router start up
Wed, 2006-10-11 01:41:54 - LCP down.
Wed, 2006-10-11 01:42:02 - Initialize LCP.
Wed, 2006-10-11 01:42:02 - LCP is allowed to come up.
Wed, 2006-10-11 01:43:03 - Initialize LCP.
Wed, 2006-10-11 01:43:03 - LCP is allowed to come up.
Wed, 2006-10-11 01:44:04 - Initialize LCP.
Wed, 2006-10-11 01:44:04 - LCP is allowed to come up.
Wed, 2006-10-11 01:45:04 - Initialize LCP.
Wed, 2006-10-11 01:45:05 - LCP is allowed to come up.
Wed, 2006-10-11 01:46:05 - Initialize LCP.
Wed, 2006-10-11 01:46:05 - LCP is allowed to come up.
Wed, 2006-10-11 01:47:06 - Initialize LCP.
Wed, 2006-10-11 01:47:06 - LCP is allowed to come up.
Wed, 2006-10-11 01:48:07 - Initialize LCP.
Wed, 2006-10-11 01:48:07 - LCP is allowed to come up.
Wed, 2006-10-11 01:49:07 - Initialize LCP.
Wed, 2006-10-11 01:49:07 - LCP is allowed to come up.
Wed, 2006-10-11 01:50:08 - Initialize LCP.
Wed, 2006-10-11 01:50:08 - LCP is allowed to come up.
Wed, 2006-10-11 01:51:03 - Loss of synchronization :2
Wed, 2006-10-11 01:51:09 - Initialize LCP.
Wed, 2006-10-11 01:51:09 - LCP is allowed to come up.
Wed, 2006-10-11 01:51:12 - CHAP authentication success
Wed, 2006-10-11 02:10:22 - LCP down.
Wed, 2006-10-11 02:10:37 - Initialize LCP.
Wed, 2006-10-11 02:10:37 - LCP is allowed to come up.
Wed, 2006-10-11 02:10:54 - CHAP authentication success
Wed, 2006-10-11 02:11:03 - Loss of synchronization :3
Wed, 2006-10-11 02:28:04 - LCP down.
Wed, 2006-10-11 02:28:12 - Initialize LCP.
Wed, 2006-10-11 02:28:13 - LCP is allowed to come up.
Wed, 2006-10-11 02:29:03 - Loss of synchronization :4
Wed, 2006-10-11 02:29:13 - Initialize LCP.
Wed, 2006-10-11 02:29:13 - LCP is allowed to come up.
Wed, 2006-10-11 02:30:14 - Initialize LCP.
Wed, 2006-10-11 02:30:14 - LCP is allowed to come up.
Wed, 2006-10-11 02:30:17 - CHAP authentication success
Wed, 2006-10-11 02:42:17 - LCP down.
Wed, 2006-10-11 02:42:26 - Initialize LCP.
Wed, 2006-10-11 02:42:26 - LCP is allowed to come up.
Wed, 2006-10-11 02:43:26 - Initialize LCP.
Wed, 2006-10-11 02:43:26 - LCP is allowed to come up.
Wed, 2006-10-11 02:43:34 - Loss of synchronization :5
Wed, 2006-10-11 02:43:34 - CHAP authentication success
Wed, 2006-10-11 03:05:14 - LCP down.
Wed, 2006-10-11 03:05:23 - Initialize LCP.
Wed, 2006-10-11 03:05:23 - LCP is allowed to come up.
Wed, 2006-10-11 03:06:04 - Loss of synchronization :6
Wed, 2006-10-11 03:06:23 - Initialize LCP.
Wed, 2006-10-11 03:06:23 - LCP is allowed to come up.
Wed, 2006-10-11 03:07:24 - Initialize LCP.
Wed, 2006-10-11 03:07:24 - LCP is allowed to come up.
Wed, 2006-10-11 03:07:28 - CHAP authentication success
Wed, 2006-10-11 04:00:17 - LCP down.
Wed, 2006-10-11 04:00:34 - Initialize LCP.
Wed, 2006-10-11 04:00:34 - LCP is allowed to come up.
Wed, 2006-10-11 04:00:35 - Loss of synchronization :7
Wed, 2006-10-11 04:01:35 - Initialize LCP.
Wed, 2006-10-11 04:01:35 - LCP is allowed to come up.
Wed, 2006-10-11 04:01:41 - CHAP authentication success
Wed, 2006-10-11 04:16:21 - LCP down.
Wed, 2006-10-11 04:16:30 - Initialize LCP.
Wed, 2006-10-11 04:16:30 - LCP is allowed to come up.
Wed, 2006-10-11 04:17:30 - Initialize LCP.
Wed, 2006-10-11 04:17:30 - LCP is allowed to come up.
Wed, 2006-10-11 04:17:36 - Loss of synchronization :8
Wed, 2006-10-11 04:18:31 - Initialize LCP.
Wed, 2006-10-11 04:18:31 - LCP is allowed to come up.
Wed, 2006-10-11 04:18:35 - CHAP authentication success
Wed, 2006-10-11 04:55:14 - LCP down.
Wed, 2006-10-11 04:55:30 - Initialize LCP.
Wed, 2006-10-11 04:55:30 - LCP is allowed to come up.
Wed, 2006-10-11 04:55:36 - Loss of synchronization :9
Wed, 2006-10-11 04:55:37 - CHAP authentication success
Wed, 2006-10-11 05:16:37 - LCP down.
Wed, 2006-10-11 05:16:45 - Initialize LCP.
Wed, 2006-10-11 05:16:45 - LCP is allowed to come up.
Wed, 2006-10-11 05:17:37 - Loss of synchronization :10
Wed, 2006-10-11 05:17:46 - Initialize LCP.
Wed, 2006-10-11 05:17:46 - LCP is allowed to come up.
Wed, 2006-10-11 05:18:47 - Initialize LCP.
Wed, 2006-10-11 05:18:47 - LCP is allowed to come up.
Wed, 2006-10-11 05:18:50 - CHAP authentication success
Wed, 2006-10-11 05:40:40 - LCP down.
Wed, 2006-10-11 05:40:48 - Initialize LCP.
Wed, 2006-10-11 05:40:49 - LCP is allowed to come up.
Wed, 2006-10-11 05:41:49 - Initialize LCP.
Wed, 2006-10-11 05:41:49 - LCP is allowed to come up.
Wed, 2006-10-11 05:41:56 - CHAP authentication success
Wed, 2006-10-11 05:42:07 - Loss of synchronization :11
Wed, 2006-10-11 05:50:16 - LCP down.
Wed, 2006-10-11 05:50:23 - Initialize LCP.
Wed, 2006-10-11 05:50:23 - LCP is allowed to come up.
Wed, 2006-10-11 05:50:37 - Loss of synchronization :12
Wed, 2006-10-11 05:51:24 - Initialize LCP.
Wed, 2006-10-11 05:51:24 - LCP is allowed to come up.
Wed, 2006-10-11 05:51:30 - CHAP authentication success
Wed, 2006-10-11 06:53:54 - UDP Packet - Source:221.209.110.48,49545 Destination:83.67.12.13,1027 - [DOS]
Wed, 2006-10-11 07:38:25 - Administrator login successful - IP:192.168.0.3