Tot Connection

[basjke]

Below is my modem status from the last 12 hours and it is like this for at least the last 6 months if not more.Technicians from TOT have been at my home trillion times always checking all the equipment inside my home only to find out that there isn't anything wrong.After that they flee as rats fleeing a sinking ship to never return.After calling the service line for a few weeks some other technicians will come to my home,return the same procedure and again flee as rats to never return.Everything inside my home has replaced,I have 4 modems,the modem is connected straight to the TOT box outside my house.Cable length approx. 4 meters.This cable has been changed to a new one at least 3 times by the technicians.

I have no other choice as TOT is the only isp available in my area.What can I do other then throw with things inside my place.

Sun, 2009-07-19 13:34:30 - Initialize LCP.

Sun, 2009-07-19 13:34:30 - LCP is allowed to come up.

Sun, 2009-07-19 13:34:31 - PAP authentication success

Sun, 2009-07-19 13:37:41 - Initialize LCP.

Sun, 2009-07-19 13:37:41 - LCP is allowed to come up.

Sun, 2009-07-19 13:37:41 - PAP authentication success

Sun, 2009-07-19 13:40:21 - LCP down.

Sun, 2009-07-19 13:43:25 - Initialize LCP.

Sun, 2009-07-19 13:43:25 - LCP is allowed to come up.

Sun, 2009-07-19 13:43:26 - PAP authentication success

Sun, 2009-07-19 13:46:58 - Initialize LCP.

Sun, 2009-07-19 13:48:04 - LCP is allowed to come up.

Sun, 2009-07-19 13:48:04 - PAP authentication success

Sun, 2009-07-19 13:49:21 - Initialize LCP.

Sun, 2009-07-19 13:49:21 - LCP is allowed to come up.

Sun, 2009-07-19 13:49:23 - PAP authentication success

Sun, 2009-07-19 13:51:41 - LCP down.

Sun, 2009-07-19 13:52:31 - Initialize LCP.

Sun, 2009-07-19 13:52:31 - LCP is allowed to come up.

Sun, 2009-07-19 13:52:31 - PAP authentication success

Sun, 2009-07-19 13:57:21 - LCP down.

Sun, 2009-07-19 13:57:23 - Initialize LCP.

Sun, 2009-07-19 13:58:24 - LCP is allowed to come up.

Sun, 2009-07-19 13:58:24 - PAP authentication success

Sun, 2009-07-19 14:11:14 - LCP down.

Sun, 2009-07-19 14:12:25 - Initialize LCP.

Sun, 2009-07-19 14:12:26 - LCP is allowed to come up.

Sun, 2009-07-19 14:12:26 - PAP authentication success

Sun, 2009-07-19 14:13:56 - LCP down.

Sun, 2009-07-19 14:15:23 - Initialize LCP.

Sun, 2009-07-19 14:18:25 - LCP is allowed to come up.

Sun, 2009-07-19 14:18:25 - Initialize LCP.

Sun, 2009-07-19 14:20:11 - LCP is allowed to come up.

Sun, 2009-07-19 14:20:12 - PAP authentication success

Sun, 2009-07-19 14:21:31 - LCP down.

Sun, 2009-07-19 14:21:41 - Initialize LCP.

Sun, 2009-07-19 14:25:59 - LCP is allowed to come up.

Sun, 2009-07-19 14:25:59 - PAP authentication success

Sun, 2009-07-19 14:35:59 - LCP down.

Sun, 2009-07-19 14:36:02 - Initialize LCP.

Sun, 2009-07-19 14:39:49 - LCP is allowed to come up.

Sun, 2009-07-19 14:39:49 - PAP authentication success

Sun, 2009-07-19 15:12:30 - Initialize LCP.

Sun, 2009-07-19 15:12:30 - LCP is allowed to come up.

Sun, 2009-07-19 15:12:30 - PAP authentication success

Sun, 2009-07-19 15:43:20 - LCP down.

Sun, 2009-07-19 15:43:28 - Initialize LCP.

Sun, 2009-07-19 15:43:29 - LCP is allowed to come up.

Sun, 2009-07-19 15:43:29 - PAP authentication success

Sun, 2009-07-19 15:48:09 - LCP down.

Sun, 2009-07-19 15:49:25 - Initialize LCP.

Sun, 2009-07-19 15:49:25 - LCP is allowed to come up.

Sun, 2009-07-19 15:49:45 - PAP authentication success

Sun, 2009-07-19 15:52:05 - LCP down.

Sun, 2009-07-19 15:52:30 - Initialize LCP.

Sun, 2009-07-19 15:52:30 - LCP is allowed to come up.

Sun, 2009-07-19 15:52:30 - PAP authentication success

Sun, 2009-07-19 15:57:12 - Initialize LCP.

Sun, 2009-07-19 15:57:12 - LCP is allowed to come up.

Sun, 2009-07-19 15:57:12 - PAP authentication success

Sun, 2009-07-19 16:36:42 - LCP down.

Sun, 2009-07-19 16:36:44 - Initialize LCP.

Sun, 2009-07-19 16:36:45 - LCP is allowed to come up.

Sun, 2009-07-19 16:36:45 - PAP authentication success

Sun, 2009-07-19 16:39:05 - LCP down.

Sun, 2009-07-19 16:39:09 - Initialize LCP.

Sun, 2009-07-19 16:39:14 - LCP is allowed to come up.

Sun, 2009-07-19 16:39:14 - PAP authentication success

Sun, 2009-07-19 16:51:54 - LCP down.

Sun, 2009-07-19 16:51:57 - Initialize LCP.

Sun, 2009-07-19 16:51:57 - LCP is allowed to come up.

Sun, 2009-07-19 16:51:57 - PAP authentication success

Sun, 2009-07-19 16:53:17 - LCP down.

Sun, 2009-07-19 16:53:20 - Initialize LCP.

Sun, 2009-07-19 16:53:25 - LCP is allowed to come up.

Sun, 2009-07-19 16:53:26 - PAP authentication success

Sun, 2009-07-19 17:17:55 - LCP down.

Sun, 2009-07-19 17:18:44 - Initialize LCP.

Sun, 2009-07-19 17:18:45 - LCP is allowed to come up.

Sun, 2009-07-19 17:18:45 - PAP authentication success

Sun, 2009-07-19 17:20:05 - LCP down.

Sun, 2009-07-19 17:20:08 - Initialize LCP.

Sun, 2009-07-19 17:20:18 - LCP is allowed to come up.

Sun, 2009-07-19 17:20:21 - PAP authentication success

Sun, 2009-07-19 17:32:08 - LCP down.

Sun, 2009-07-19 17:32:39 - Initialize LCP.

Sun, 2009-07-19 17:32:39 - LCP is allowed to come up.

Sun, 2009-07-19 17:32:39 - PAP authentication success

Sun, 2009-07-19 18:20:16 - Administrator login successful - IP:192.168.1.2

Sun, 2009-07-19 18:21:17 - Initialize LCP.

Sun, 2009-07-19 18:21:17 - LCP is allowed to come up.

Sun, 2009-07-19 18:21:17 - PAP authentication success

Sun, 2009-07-19 18:35:37 - LCP down.

Sun, 2009-07-19 18:36:56 - Initialize LCP.

Sun, 2009-07-19 18:36:56 - LCP is allowed to come up.

Sun, 2009-07-19 18:36:57 - PAP authentication success

Sun, 2009-07-19 18:47:59 - Initialize LCP.

Sun, 2009-07-19 18:47:59 - LCP is allowed to come up.

Sun, 2009-07-19 18:47:59 - PAP authentication success

Sun, 2009-07-19 19:00:56 - Initialize LCP.

Sun, 2009-07-19 19:00:56 - LCP is allowed to come up.

Sun, 2009-07-19 19:00:56 - PAP authentication success

Sun, 2009-07-19 19:08:34 - Initialize LCP.

Sun, 2009-07-19 19:08:34 - LCP is allowed to come up.

Sun, 2009-07-19 19:08:34 - PAP authentication success

Sun, 2009-07-19 19:16:44 - LCP down.

Sun, 2009-07-19 19:17:11 - Initialize LCP.

Sun, 2009-07-19 19:17:11 - LCP is allowed to come up.

Sun, 2009-07-19 19:17:11 - PAP authentication success

Sun, 2009-07-19 19:22:48 - Administrator login successful - IP:192.168.1.2

Sun, 2009-07-19 19:24:41 - LCP down.

Sun, 2009-07-19 19:24:44 - Initialize LCP.

Sun, 2009-07-19 19:24:44 - LCP is allowed to come up.

Sun, 2009-07-19 19:24:44 - PAP authentication success

Sun, 2009-07-19 19:29:14 - LCP down.

Sun, 2009-07-19 19:30:10 - Initialize LCP.

Sun, 2009-07-19 19:31:11 - Initialize LCP.

Sun, 2009-07-19 19:32:11 - LCP is allowed to come up.

Sun, 2009-07-19 19:32:12 - PAP authentication success

Sun, 2009-07-19 19:38:10 - Initialize LCP.

Sun, 2009-07-19 19:38:10 - LCP is allowed to come up.

Sun, 2009-07-19 19:38:10 - PAP authentication success

Sun, 2009-07-19 19:39:30 - LCP down.

Sun, 2009-07-19 19:39:45 - Initialize LCP.

Sun, 2009-07-19 19:40:45 - Initialize LCP.

Sun, 2009-07-19 19:41:01 - LCP is allowed to come up.

Sun, 2009-07-19 19:41:01 - PAP authentication success

Sun, 2009-07-19 19:42:23 - Initialize LCP.

Sun, 2009-07-19 19:42:23 - LCP is allowed to come up.

Sun, 2009-07-19 19:42:25 - PAP authentication success

Sun, 2009-07-19 19:42:31 - Administrator login successful - IP:192.168.1.2

Sun, 2009-07-19 21:15:13 - LCP down.

Sun, 2009-07-19 21:15:30 - Initialize LCP.

Sun, 2009-07-19 21:16:41 - LCP is allowed to come up.

Sun, 2009-07-19 21:16:41 - PAP authentication success

Sun, 2009-07-19 21:26:11 - LCP down.

Sun, 2009-07-19 21:30:59 - Initialize LCP.

Sun, 2009-07-19 21:30:59 - LCP is allowed to come up.

Sun, 2009-07-19 21:30:59 - PAP authentication success

Sun, 2009-07-19 21:31:26 - Send out NTP request to time-e.netgear.com

Sun, 2009-07-19 21:33:01 - Initialize LCP.

Sun, 2009-07-19 21:33:02 - LCP is allowed to come up.

Sun, 2009-07-19 21:33:02 - PAP authentication success

Sun, 2009-07-19 21:33:09 - Send out NTP request to time-f.netgear.com

Sun, 2009-07-19 21:34:44 - Send out NTP request to time-e.netgear.com

Sun, 2009-07-19 21:38:22 - LCP down.

Sun, 2009-07-19 21:39:38 - Initialize LCP.

Sun, 2009-07-19 21:39:38 - LCP is allowed to come up.

Sun, 2009-07-19 21:39:58 - PAP authentication success

Sun, 2009-07-19 21:43:22 - Send out NTP request to time-f.netgear.com

Sun, 2009-07-19 21:48:18 - LCP down.

Sun, 2009-07-19 21:48:40 - Initialize LCP.

Sun, 2009-07-19 21:48:45 - LCP is allowed to come up.

Sun, 2009-07-19 21:48:45 - PAP authentication success

Sun, 2009-07-19 21:53:19 - Send out NTP request to time-e.netgear.com

Sun, 2009-07-19 21:55:35 - LCP down.

Sun, 2009-07-19 21:55:40 - Initialize LCP.

Sun, 2009-07-19 21:55:46 - LCP is allowed to come up.

Sun, 2009-07-19 21:55:46 - PAP authentication success

Sun, 2009-07-19 22:02:22 - Send out NTP request to time-f.netgear.com

Sun, 2009-07-19 22:19:56 - Send out NTP request to time-e.netgear.com

Sun, 2009-07-19 22:28:26 - LCP down.

Sun, 2009-07-19 22:29:42 - Administrator login successful - IP:192.168.1.2

Sun, 2009-07-19 22:30:07 - Initialize LCP.

Sun, 2009-07-19 22:30:08 - LCP is allowed to come up.

Sun, 2009-07-19 22:30:08 - PAP authentication success

Sun, 2009-07-19 22:36:48 - LCP down.

Sun, 2009-07-19 22:37:14 - Initialize LCP.

Sun, 2009-07-19 22:37:15 - LCP is allowed to come up.

Sun, 2009-07-19 22:37:15 - PAP authentication success

Sun, 2009-07-19 22:44:25 - LCP down.

Sun, 2009-07-19 22:44:35 - Initialize LCP.

Sun, 2009-07-19 22:44:35 - LCP is allowed to come up.

Sun, 2009-07-19 22:44:36 - PAP authentication success

Sun, 2009-07-19 22:54:36 - Send out NTP request to time-f.netgear.com

Sun, 2009-07-19 23:21:55 - LCP down.

Sun, 2009-07-19 23:22:02 - Initialize LCP.

Sun, 2009-07-19 23:22:02 - LCP is allowed to come up.

Sun, 2009-07-19 23:22:02 - PAP authentication success

Sun, 2009-07-19 23:22:26 - Administrator login successful - IP:192.168.1.2

Sun, 2009-07-19 23:23:22 - LCP down.

Sun, 2009-07-19 23:23:25 - Initialize LCP.

Sun, 2009-07-19 23:27:43 - LCP is allowed to come up.

Sun, 2009-07-19 23:27:43 - PAP authentication success

Sun, 2009-07-19 23:49:53 - LCP down.

Sun, 2009-07-19 23:49:58 - Initialize LCP.

Sun, 2009-07-19 23:49:58 - LCP is allowed to come up.

Sun, 2009-07-19 23:49:58 - PAP authentication success

Sun, 2009-07-19 23:51:38 - LCP down.

Sun, 2009-07-19 23:53:03 - Initialize LCP.

Sun, 2009-07-19 23:53:04 - LCP is allowed to come up.

Sun, 2009-07-19 23:53:04 - PAP authentication success

Mon, 2009-07-20 00:03:44 - LCP down.

Mon, 2009-07-20 00:04:56 - Initialize LCP.

Mon, 2009-07-20 00:04:56 - LCP is allowed to come up.

Mon, 2009-07-20 00:04:56 - PAP authentication success

Mon, 2009-07-20 00:07:04 - Initialize LCP.

Mon, 2009-07-20 00:07:05 - LCP is allowed to come up.

Mon, 2009-07-20 00:07:05 - PAP authentication success

Mon, 2009-07-20 00:08:53 - Send out NTP request to time-e.netgear.com

Mon, 2009-07-20 00:19:27 - Initialize LCP.

Mon, 2009-07-20 00:19:28 - LCP is allowed to come up.

Mon, 2009-07-20 00:19:28 - PAP authentication success

Mon, 2009-07-20 00:20:48 - LCP down.

Mon, 2009-07-20 00:20:50 - Initialize LCP.

Mon, 2009-07-20 00:20:50 - LCP is allowed to come up.

Mon, 2009-07-20 00:20:50 - PAP authentication success

Mon, 2009-07-20 00:25:20 - LCP down.

Mon, 2009-07-20 00:25:23 - Initialize LCP.

Mon, 2009-07-20 00:26:29 - LCP is allowed to come up.

Mon, 2009-07-20 00:26:29 - PAP authentication success

Mon, 2009-07-20 00:28:59 - LCP down.

Mon, 2009-07-20 00:29:12 - Initialize LCP.

Mon, 2009-07-20 00:29:12 - LCP is allowed to come up.

Mon, 2009-07-20 00:29:12 - PAP authentication success

Mon, 2009-07-20 00:40:32 - LCP down.

Mon, 2009-07-20 00:41:23 - Initialize LCP.

Mon, 2009-07-20 00:41:23 - LCP is allowed to come up.

Mon, 2009-07-20 00:41:23 - PAP authentication success

Mon, 2009-07-20 00:44:43 - LCP down.

Mon, 2009-07-20 00:49:14 - Initialize LCP.

Mon, 2009-07-20 00:49:14 - LCP is allowed to come up.

Mon, 2009-07-20 00:49:14 - PAP authentication success

Mon, 2009-07-20 00:52:25 - Initialize LCP.

Mon, 2009-07-20 00:52:26 - LCP is allowed to come up.

Mon, 2009-07-20 00:52:26 - PAP authentication success

Mon, 2009-07-20 00:55:26 - LCP down.

Mon, 2009-07-20 00:59:52 - Initialize LCP.

Mon, 2009-07-20 00:59:52 - LCP is allowed to come up.

Mon, 2009-07-20 00:59:52 - PAP authentication success

Mon, 2009-07-20 00:59:59 - Administrator login successful - IP:192.168.1.2

Edited July 19, 2009 by basjke

[NHJ]

when you have a synchro, tell us your line value.

[basjke]

when you have a synchro, tell us your line value.

Not sure what you mean with line synchro

But my figures are line attenuation 19/3.5 db

noise margin 25/20 db but this jumps around like crazy between 29 and 1 db.So one moment it can be 28 db 5 seconds later it can be 3db and the next 5 seconds 23 db again.

Modem gets disconnected every 5 to 10 minutes and when it reconnects the upstream can be any figure between 150kbps and 512 kbps.

[webfact]

LCP = protocol for initiating, authenticating, errors and session terminating.

Check with your ISP user name and pw. There could be a conflict. Ask them to provide you a new username and password

It may be a DSLAM issue as well.

Edited July 20, 2009 by webfact

[Tewkes]

I had exactly the same problem about a year ago with my connection. Had engineers out reporting no faults and had good numbers on the noise margin and attenuation.

Went on for months until i tried swapping out my Netgear router (DG834Gv1) for the TOT supplied one at which point all was resolved.

I assumed it was a hardware error although there was no obvious failure apart from the constant disconnects and so I bought a new model Netgear router (DG834Gv5) as I liked the integrated WiFi, firewall setup. Since then I've had no problems.

Now it could be that the line magically fixed itself just when i replaced the router but seems unlikely to me.

I notice from your logs that you had an update to the netgear time server. Would it be a fair assumption to assume you have a netgear router? If so might be possible you have the same problem I did.

Whatever thought my experiences might help.

[basjke]

I had exactly the same problem about a year ago with my connection. Had engineers out reporting no faults and had good numbers on the noise margin and attenuation.

Went on for months until i tried swapping out my Netgear router (DG834Gv1) for the TOT supplied one at which point all was resolved.

I assumed it was a hardware error although there was no obvious failure apart from the constant disconnects and so I bought a new model Netgear router (DG834Gv5) as I liked the integrated WiFi, firewall setup. Since then I've had no problems.

Now it could be that the line magically fixed itself just when i replaced the router but seems unlikely to me.

I notice from your logs that you had an update to the netgear time server. Would it be a fair assumption to assume you have a netgear router? If so might be possible you have the same problem I did.

Whatever thought my experiences might help.

Yes I have the same router as you but other then that I have the TOT modem,a other modem that the TOT technicians use and I have tried out a d-link modem.All give the same result.

[Tewkes]

Given problems across a whole load of different routers and manufactures I would say it almost certainly a problem with the physical line you are on.

You mentioned that you had rapidly changing noise margin and attenuation and across a wide range of values. If that is the case on all the routers you have tried then that would reinforce a line problem.

It sounds like with that sort of variation on noise the DSLAM is constantly trying to negotiate a speed with your router eventually gives ups on getting a stable speed times outs and resets. The fact your upstream connection varies upon reconnect would also support this.

Problem is therefore almost certainly either a fault with the DSLAM which should be obvious to TOT and easy to fix or a fault with the phone line which should again be obvious if they run some noise and attenuation test. Fixing the line would be a much bigger job for TOT though which might explain why they saying nothing is wrong.

Unfortunately don't think there will be a quick fix to this given TOT normal speed of operations. All i would say would be keep complaining that the phone line is no good and highlight the variations in the attenuation and noise as I'd say this is where the problem is.

[basjke]

Had the TOT technicians at my home again late afternoon today and they located the problem,it was my modem.

They installed one of their own modems to test out for one day.Now here comes the funny thing that always happens when I get really upset and shortly after that they will locate the problem inside my home.

In the first 2 hours 50 minutes after the modem was installed the connection was cut 11 times.After that no disconnections anymore.Last disconnection was 5 hours ago.

This same thing happened at least 4 times in the past when they detected the problem but after about 1 week the same problems return.

I really wonder how they do this magic trick.The way I understand it is that they are able to give you a decent connection but they just refuse to do so,or they have some lines without problem and if you get upset to much they link you temporarily to one of those lines.Until the next customer in your area gets upset.

[basjke]

Update:Technicians from TOT came back wednesday and admitted that the problem was with their own line.They would fix it today friday.Called them this morning and they said they would fix the line today.

I must say that they did a really good job since the connection has only been cut 54 timesbetween 9 am this morning and now 7 pm.

Been cut twice while typing this post.Viva the thai adsl.

[brianinbangkok]

My guess is your phone line is bad. Request a new line and get ADSL on that line , make sure u get a new line so do not cancel the old one yet.

I had the same kind of problems on my TOT ADSL Gold cyber for about a year.

I noticed that TOT had installed a new exchange for phone lines near my house and got the TOT guys working on it to talk to the service people for TOT ADSL and get me a line out of that exchange box 500 meters from my house.

They got me a new line and that pretty much fixed 99% of my problems.

Also at the moment changing your contract will get you the cheaper monthly rates from TOT.

[mommysboy]

when you have a synchro, tell us your line value.

Not sure what you mean with line synchro

But my figures are line attenuation 19/3.5 db

noise margin 25/20 db but this jumps around like crazy between 29 and 1 db.So one moment it can be 28 db 5 seconds later it can be 3db and the next 5 seconds 23 db again.

Modem gets disconnected every 5 to 10 minutes and when it reconnects the upstream can be any figure between 150kbps and 512 kbps.

I sympathise, many posters who might help, just muddy waters with throw away lines like this without explanation. I for one hope their head caves in.

[webfact]

when you have a synchro, tell us your line value.

Not sure what you mean with line synchro

But my figures are line attenuation 19/3.5 db

noise margin 25/20 db but this jumps around like crazy between 29 and 1 db.So one moment it can be 28 db 5 seconds later it can be 3db and the next 5 seconds 23 db again.

Modem gets disconnected every 5 to 10 minutes and when it reconnects the upstream can be any figure between 150kbps and 512 kbps.

I sympathise, many posters who might help, just muddy waters with throw away lines like this without explanation. I for one hope their head caves in.

This issue can have many reasons - my guess:

Before crossing the ADSL signal to telephone line, Media provider have to check and consider the signal in each line with your line.

The Media Provider checks the ADSL port at DSLAM. The reason that your line diconnects can be caused by many factors such as:

1. Quality of outdoor cable from DSLAM to Drop Wire at your site. (your signal swings heavily)

2. The contradiction of ADSL signal in telephone line.

I think that wans't checked properly!

In case you increase the ADSL speed in your telephone line, the signal noise ratio drops and you may experience the disconnected problem, error in line and ADSL signal can not syncronize at speed. - disconnect!

A lower ADSL speed may solve the issue!

Edited July 24, 2009 by webfact

[basjke]

Lucky it is much better again today.I can now stay connected for an average of 48 seconds since 9 this morning.Made a call to the 1100 service number and the lady at the other side assured me that TOT as soon as they are aware of a problem they will fix it straight away.

Didn't know if I had to laugh or cry when she said that.

[khunjake]

A had a similar problem and I checked a very simple thing on my router which fixed it. Make sure your ADSL modulation type is set to "DMT".

[coalminer]

Lucky it is much better again today.I can now stay connected for an average of 48 seconds since 9 this morning.Made a call to the 1100 service number and the lady at the other side assured me that TOT as soon as they are aware of a problem they will fix it straight away.

Didn't know if I had to laugh or cry when she said that.

FWIW, I have been trough the same TOT/TT&T/CAT Telecom troubles as you and help was always like a drop of water on a hot plate.

I purchased one of these EDGE Modems which works with a regular SIM Card for a few Baht.

I can use this Edge card everywhere I am wthout the need for a Wi-Fi connection or whatever.

Even in the car while dfiving and connected to Google Maps.

And the speed?

The speed of the EDGE card is almost as good as the International Internet connections of a Thai ADSL and te fact that I am never been disconnected with my EDGE Modem makes it worth a zillion times.

[thaibkk]

the modem has a sync problem... as an ex-adsl expert in my own country, low tech technicians do not have to try to explain me otherwise... it happens a lot on saturdays/sundays but also during the week... sync problem or simple connected but 0 kb / sec for many hours...

had no choice and took an EDGE backup, that seems to work as badly as the TOT adsl line...

[basjke]

After 2 years complaining to deaf ears they yesterday finally replaced the last end of the cable to my house.The speed has improved a lot and I'm now 19 hours online without any disconnection.Hiha.