on 30-06-2013 12:14
From few days Internet connection is really bad. Can't work with this connection at all. My kids can't play any games to. All works fine and after few mins its gone fore few mins and comming back again. Can you tell me please how i can check it? Where i should ping? So far i did found some analyse web where i did it:
on 30-06-2013 12:16
Summary of Noteworthy Events + –
Major Abnormalities –
Minor Aberrations –
Address-based Tests + –
Direct TCP access to remote FTP servers (port 21) is allowed.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP3 servers (port 110) is allowed.
Direct TCP access to remote RPC servers (port 135) is allowed.
Direct TCP access to remote NetBIOS servers (port 139) is allowed.
Direct TCP access to remote IMAP servers (port 143) is allowed.
Direct TCP access to remote SNMP servers (port 161) is allowed.
Direct TCP access to remote HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is allowed.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote OpenVPN servers (port 1194) is allowed.
Direct TCP connections to remote PPTP Control servers (port 1723) succeed, but do not receive the expected content.
on 30-06-2013 12:17
The client received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
Direct TCP access to remote TOR servers (port 9001) is allowed.
UDP connectivity (?): OK
Traceroute (?): OK
Path MTU (?): OK
Hidden Proxy Detection (?): OK
Network Access Link Properties –
Network performance (?): Latency: 110 ms, Loss: 0.0%
TCP connection setup latency (?): 100ms
Background measurement of network health (?): no transient outages
Network bandwidth (?): Upload 860 Kbit/s, Download 9.6 Mbit/s
Network buffer measurements (?): Uplink 150 ms, Downlink is good
HTTP Tests –
Address-based HTTP proxy detection (?): OK
Content-based HTTP proxy detection (?): OK
HTTP proxy detection via malformed requests (?): OK
Filetype-based filtering (?): OK
HTTP caching behavior (?): OK
DNS Tests –
Restricted domain DNS lookup (?): OK
You appear to be using OpenDNS as your DNS resolver. OpenDNS acts as a Man-in-the-Middle for some servers, returning the address of one of their servers that acts as an intermediary, rather than the final result. As a result, 2 lookups appear to be anomalous.
90 of 90 popular names were resolved successfully. Show all names.
23 popular names have a mild anomaly. The ownership suggested by the reverse name lookup does not match our understanding of the original name. The most likely cause is the site's use of a Content Delivery Network. Show all names.
2 popular names have a mild anomaly: we are unable to find a reverse name associated with the IP address provided by your ISP's DNS server. This is most likely due to a slow responding DNS server or misconfiguration on the part of the domain owner. Show all names.
on 30-06-2013 12:17
You appear to be using OpenDNS. OpenDNS, by default, deliberately returns addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 22.214.171.124, which resolves to hit-nxdomain.dlinksearch.com. You can inspect the resulting HTML content here.
This is central to OpenDNS's business model. In order to support an otherwise free service, OpenDNS presents the users with advertisements whenever they make a typo in their web browser. You can disable this behavior through the OpenDNS Dashboard.
The big problem with this behavior is that it can potentially break any network application which relies on DNS properly returning an error when a name does not exist.
The following lists your DNS server's behavior in more detail.
Another problem with the DNS server is its response to a server failure. Instead of properly returning an error when it cannot contact the DNS authority, the DNS server returns an address of 126.96.36.199. Since transient failures are quite common this can be significantly disruptive, turning a transient failure into a wrong answer without any notification to the application doing the name lookup.
The DNS resolver you are using deliberately manipulates results. This can prove problematic, as you will be unable to contact an IPv6-only site: the DNS resolver is giving incorrect results for a system which has only an IPv6 address. We expected the client to only receive cafe:babe:66:0:0:0:0:1 (an IPv6 address), instead it received the following address: 188.8.131.52.
Your DNS resolver is not on Google's IPv6 "whitelist", which means that Google does not enable IPv6 access to their services for you.
Network Security Protocols + –
Host Properties + –
Uploaded data (?): OK
on 30-06-2013 12:17
I dont know if its any info for you but it didnt happen before for me and i didnt made any new changes to my hardware or software. From that what i know there ware some maintenence at 16.06.13 if i good remember. After that i did reset my router like it was in e-mail and all did work fine till last 3 days. Please let me know if there are any works going on in this area.
on 30-06-2013 15:01
Did another test to one of the game servers:
Tracing route to 184.108.40.206 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 31 ms 31 ms 30 ms oxfd-bam-1.network.virginmedia.net [220.127.116.11]
3 * * 31 ms oxfd-core-2a-xe-1111-2.network.virginmedia.net [18.104.22.168]
4 33 ms 35 ms 36 ms brhm-bb-1c-ae4-0.network.virginmedia.net [22.214.171.124]
5 * * 35 ms manc-bb-1d-ae9-0.network.virginmedia.net [126.96.36.199]
6 55 ms 119 ms 54 ms ams2-ic-1-ae0-0.network.virginmedia.net [188.8.131.52]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * 190 ms border1.po1-20g-bbnet1.lax010.pnap.net [184.108.40.206]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
What i did noutice there are breakes from internet each few mins and dont know why.
on 01-07-2013 14:11
I have been looking at your connection and it does seem shocking, I can see quite a few drops in connections. I have had a look and can not see any local outages that would affect you.
I would at this point urge you to do the following
Connect your filter into the test / master socket
change your filter
Ensure that no other socket in the house is in use
remove any telephone extension leads
plug only your router and one phone into the filter
check for any noise on your phone line
Once doing the above, if you are still getting drops in connection I would advise to call into our faults department on 151 from a VM line or 0845 454 2222 from any other line
on 01-07-2013 18:11
I just had chat with one of your team members on the phone from tech sup i think level 1 or sometheing and he did mark my connection as "faulty" and pass to BT. I should wait to 72h for update but for me atm from time when my internet is working when i do test on www.speedtest.net my download is max 6mb where before that issue i had 11mb for around 3 years. I understand if there is something wrong with connection dl speed can drop down but if it wil stay like that i will need to change my ISP. Im happy customer for around 3 years now with constant 11mb download what is all what i need and now its drops to half of my speed and above that its dropping of each few mins and i do pay 37 pounds each month for adsl where other ISP offer less for the same speed with half term half price. I would be really happy if you could look after my case because i would really like to stay with VM as i had no issues for around 3 years till now.
Waiting till any futhere update from you and will keep you posted with any update i can. If there is anything what you think i could check please let me know.
on 01-07-2013 20:05
Another update. Yestarday i did test by phone line what speed i can get with my line and it did show me 11mb dl and now when i did it it did show me max i can get 4.45bm and its for my exchange to my home. Its looks like there is something wrong.