But also always ask for their name and ID. Remember that they are just earning some money this way and generally they are not your ennemies :-) So be nice to them. Missing internet stresses people a lot, so never be rude when talking with support guys. This is already the headache of your ISP, it shall replace your phone line to meet the standards. But they also can happen because you get ADSL over an old phone line and the signal is bad. They can happen because your network card went faulty. These can be harder to debug, because there are many factors involved. Tell them exactly what the problem is, if you can figure it out, this will make them understand that you know the tech part and they won't get away with silencing you by providing some silly tech excuse. Never say "internet is not working" or something like that. If they said ten minutes and the problem is not getting fixed, call again after ten minutes. Fix them and tell me how much time do you need for fixing that." Sometimes they will say ten minutes or 30 minutes, just to dodge your call, because most people call once and give up. Call the support and tell them "Your router with this IP (you will see which one in mtr, there will be packet losses there) has issues. This is the situation when you can be more harsh. issues inside your ISP infrastructure.They might happen if some link went down and traffic is temporarily rerouted over a backup link that has lower bandwidth. Such problems don't happen often, because backbone ISPs have better quality. They should work with the upstream provider and settle this. This is not an excuse for your ISP support to turn around angry customers. I will elaborate on them in reverse order: It works like a combination of ping and traceroute - it's like an interactive traceroute.Ī wide class of connectivity issues happens because IP packets loss. There are at least Linux and Windows versions. My favorite tool for debugging networking issues is mtr. Up to a certain point they will be assigned to your ISP, that's the internal infrastructure of your ISP) Look at the output of traceroute and do "whois" against each IP starting with your gateway. the infrastructure of the ISP (you will have to do a little investigation to find this out, because some ISPs don't disclose their network ranges.my connection to the ISP (that's between me and the gateway at the ISP).When debugging a connectivity issue, I split it into three parts: Pardon me for going slightly offtopic, but I felt your pain a couple of years ago and I've developed a workflow which you might find useful. So I am thinking about using one software to record down the connection situation, so that I can present to the technical staff and make sure that they have no excuse not to fix my problem.Įdit: Of course, such software should not record my browsing habit, and must be able to monitor and record the internet connection condition even when I am not online. If I ping the domain name directly (i.e., ping -t in cmd command), I will get a cannot ping message.īecause of the flickery nature of the connection, it's pretty hard to prove to the support staff that internet connection is unstable. I can connect some of the time, but MOST of the time the connection will just drop off ( with the error message unable to resolve host) and after a few minutes, it will resume back. Thanks to the excellent internet connection service offered by one of the best ISP in the world, the internet connection in my area is very, very unstable. It is not currently accepting new answers or interactions. This question and its answers are locked because the question is off-topic but has historical significance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |