Originally posted by max@Dec 10 2005, 09:59 PM
...Use a network monitor to see what kind of and how many packets are being sent across. If its too much then you connection _will_ choke.
[snapback]35168[/snapback]
Thanx, max. Will d/l and check. In the meantime, just to let all you guys know, I sent a mail on December 10, to the DGM (BB), DGM (VAS) and Exec Director, Delhi about the problem and how 1504 was just giving me complaint nos. and nothing else. A field engineer called and visited us on Monday! Spent quite some time...and came to the conclusion that the line needed to be checked which they are in the process of doing today. Will know in a couple of hours as to what happens.So, an email to the top bosses does work. Second or third time for me.
[/quote]
An update:
Sent off screen shots showing packet losses on a DNS server ping to the DGM (BB), GM (VAS) and ED Delhi. Two 'field engineers' landed up last evening to find:
1. Port set at 256 for a 512K connection. Set right immediately.
2. Very high result for insulation parameter on the line - 783 instead of the normal 16. That's what's causing the packet loss and resultant slowing down or choking of the connection. They are working on this and I think I did notice some improvement towards the evening tho' I've take the precaution of informing the three senior gentlemen in MTNL Delhi that they need to get their line staff on the job.
Will keep you guys up to date. Moral of the story, if things don't move, pester the higher ups with emails. It seems to work in Delhi
This website uses affiliate links. This means that if you click on a link and make a purchase, we may receive a commission. This does not affect the price you pay for the product.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.