The thing is it's only doing this for one account. I've ISP and hostes email working fine so I'm a little loathed to mess with DNS etc. The firewall is set to give AVG full access.
I've done a tracert and got the following.
Quote:
Tracing route to secureserver.net [208.109.132.208]
over a maximum of 30 hops:
1 24 ms 10 ms 7 ms 10.225.32.1
2 20 ms 29 ms 10 ms nott-t2cam1-b-v116.inet.ntl.com [80.4.46.245]
3 11 ms 12 ms 12 ms nott-t3core-1b-ge-012-0.inet.ntl.com [195.182.17
4.237]
4 12 ms 12 ms 15 ms nth-bb-b-so-020-0.inet.ntl.com [213.105.174.173]
5 14 ms 43 ms 11 ms nth-bb-a-ge-000-0.inet.ntl.com [62.253.185.117]
6 22 ms 17 ms 16 ms so-0-0-0-0.loncr4.London.opentransit.net [193.25
1.251.161]
7 102 ms 91 ms 94 ms po10-0.ashcr1.Ashburn.opentransit.net [193.251.2
40.182]
8 110 ms 91 ms 91 ms te10-2.ashse1.Ashburn.opentransit.net [193.251.2
43.142]
9 109 ms 93 ms 90 ms dcp-brdr-01.inet.qwest.net [63.146.26.21]
10 94 ms 91 ms 94 ms dcx-core-01.inet.qwest.net [205.171.251.57]
11 160 ms 160 ms 162 ms phn-core-02.inet.qwest.net [67.14.19.42]
12 161 ms 159 ms 158 ms phv-edge-03.inet.qwest.net [205.171.12.110]
13 162 ms 171 ms 145 ms 63.230.242.110
14 144 ms * * ip-208-109-112-142.ip.secureserver.net [208.109.
112.142]
15 * * * Request timed out.
16 * 146 ms * ip-208-109-112-150.ip.secureserver.net [208.109.
112.150]
17 149 ms 158 ms 147 ms ip-208-109-112-177.ip.secureserver.net [208.109.
112.177]
18 149 ms * * corpweb-v108.prod.mesa1.secureserver.net [208.10
9.132.208]
19 165 ms 152 ms * corpweb-v108.prod.mesa1.secureserver.net [208.10
9.132.208]
20 171 ms 151 ms * corpweb-v108.prod.mesa1.secureserver.net [208.10
9.132.208]
21 151 ms * * corpweb-v108.prod.mesa1.secureserver.net [208.10
9.132.208]
22 * 151 ms * corpweb-v108.prod.mesa1.secureserver.net [208.10
9.132.208]
23 158 ms * * corpweb-v108.prod.mesa1.secureserver.net [208.10
9.132.208]
24 * 148 ms 151 ms corpweb-v108.prod.mesa1.secureserver.net [208.10
9.132.208]
Trace complete.
|
I've also pinged the IP address and got the following. I did it three times due to the hit and miss results.
Quote:
ping 208.109.132.208
Pinging 208.109.132.208 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 208.109.132.208: bytes=32 time=147ms TTL=114
Request timed out.
Ping statistics for 208.109.132.208:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 147ms, Maximum = 147ms, Average = 147ms
ping 208.109.132.208
Pinging 208.109.132.208 with 32 bytes of data:
Reply from 208.109.132.208: bytes=32 time=148ms TTL=114
Request timed out.
Request timed out.
Reply from 208.109.132.208: bytes=32 time=148ms TTL=114
Ping statistics for 208.109.132.208:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 148ms, Maximum = 148ms, Average = 148ms
ping 208.109.132.208
Pinging 208.109.132.208 with 32 bytes of data:
Reply from 208.109.132.208: bytes=32 time=148ms TTL=114
Request timed out.
Reply from 208.109.132.208: bytes=32 time=145ms TTL=114
Request timed out.
Ping statistics for 208.109.132.208:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 145ms, Maximum = 148ms, Average = 146ms
|