I have same problem as you, the only difference is that everytime the modem resync, I will lost connection and have to renew IP. This is what I do to restore my connection back. Documentation is important because with it, you can use MCMC to force Telekom to REALLY FIX your problem.

First, you make a report at https://tmbill.tm.net.my/iCoMSWeb/external/CreateCaseServlet - make sure you attach the screenshots of your SNR margins with the report. Make sure that you explained in that report that you have done all those 'neccesary' things such as plugging directly to wall socket, not using splitter, using manual dialer etc. this is important. Then jot down the report number.

Everyday, make a screenshot of your SNR ratio and keep it for MCMC documentation.

After a few days, call the hotline and ask for the status for your report number. The operator should be able to tell you what they have done. They may ask whether you have done all the things in their manual, and reply that you have done so. The operator may or may not create a new report number as they passed the issue to the ground technicians.

From my experience, things that they do includes resetting the port, going to the pole near your house or replace the 'pair' at your port. Make sure you check your status every few days to get the latest info. If your case runs like mine, you may get few more report numbers, I got 5 more in my case. Log all the report numbers you have got.

After a month or so and your problem is still not solved, it is time for you to get a rebate for all your problems. Below is a report I have made....



After that, download the complaint form from the MCMC website, fill it and e-mail/fax it alongside with the copy of request for rebate to MCMC. In my case, I've done both faxing and e-mailing it, just to be sure.

In my case and to their credit, within 24 hours, TMNet did contact me and replied that my request for rebate is approved, and it is an indefinite rebate at that. MCMC also e-mailed me to acknowledge the receipt of the complaint. But as I would rather prefer paying full price for a Streamyx connection that does not blink every time it rains or at night than paying half-price for an unstable connection, I still made calls to the hotline.

A few days later, TMNet Rapid Response Team e-mailed me that they have received the MCMC complaint form and told me that they will try to solve my problem as soon as possible. The very next day, a big contingent of Telekom technicians comes to my housing estate and simply rips out all the cabling there and replace it with new ones. For 2 days all the residents there (and also me) do not have telephone/Internet access. But after the service is restored, my Streamyx service is now much better before the problem started. Now my modem sync with the DSLAM at 2048 down/ 512 upload with 30dB local SNR while the attenuation is a crazy value of 0.5dB only. Before this, my values is almost exactly like yours.

Now I have just finished e-mailing TMNet to stop extending my rebate past September 2007 bill. So you have to be very persistent in trying to get this problem solved.



This post has been edited by asellus: Sep 25 2007, 02:13 AM

More attached images:-



This post has been edited by asellus: Oct 1 2007, 12:59 AM

That is a problem outside your ability to solve. Just make a report to TMNet about the SNR loss.

The DS margin is borderline case. May have problems in rainy cases.

More often than not, there's nothing you can do. Calling TMNet is the solution, tell them you have SNR loss problem.

Try checking for parallel phone lines in your house, and try connecting directly to wall ,socket.

I think e-mailing them is better if you have problems explaining, make sure some screen shots of the SNR values are included.

Your values are OK, thus your problem may lies with TMNet connectivity.


I think you should call 100/130889515 and ask for updates of your case.

In my case they did not, YMMV.

You can't check your SNR thorugh router, in most cases. Have to connect directly to modem.

DHCP relay will take an IP from another DHCP server in the network and assign it on your computer NIC.
DHCP server means that your modem is the DHCP server and it will assign an IP to your computer NIC.

If you connect your modem to your router via WAN, you do not have to do anything especially if your router is the one that dials.

Set the OAM_VCI to 35, that's the correct value.

---

Added on October 28, 2007, 4:09 pmIf refreshing the page or restarting the modem did not solve the problem, I guess it will be a firmware problem. Anyway, I do not think you have SNR loss problem if the line attenuation figures is taken into account.

---

Added on October 28, 2007, 4:13 pmI think the only thing you can do is to make a SNR loss report to TMNet. Not via the useless hotline but via online report at https://tmbill.tm.net.my/iCoMSWeb/external/CreateCaseServlet

Make sure you put those screenshots together with the report.

This post has been edited by asellus: Oct 28 2007, 04:13 PM

I think there's not the fault of your side. Time to call the hotline I think.

I think it is the VCI value, probably it uses 32 when testing, that's why it did not pass the test.

Line attenuation at 33 is not that bad I think.

For rewiring, I think unless it is done from the exchange to your house, probably will not make much difference. If only your house wiring are replaced but the ones outside is not, things will not really change a lot.

If that's the case, you can try changing the wires from the nearest pole to inside your house and see whether it will solve the problem. This will be trial-and-error as the problem can't be narrowed down yet. But with that figures you have, I think the problem lies way further upstream. Has the technician tried switching your port?

SnR margin of 25-31dB.
Line Attenuation of 33dB.
These are good figures.

When I say upstream, it means somewhere far beyond your line, probably nearer the DSLAM/CO instead of your premise where the cause of your problems may lie.

TM and not TMNet is the one who will change it.

Try calling the number TMNet technician have given to you.

It is because your line is brand new. Your value is very much OK.

This post has been edited by asellus: Nov 28 2007, 11:45 PM

Your line is good. Any slowdown should be caused by TMNet itself, not because you have a poor line.

About the system log, I dunno.

But your line is bad, can't even sync to at least 1MB. What is your package?