Email Problems / Blocked ports?

cmk · 04-12-2007, 11:11

Do NTL/Virgin Media block ports at all? I've a Go Daddy hosting account which is throwing a fit and they're saying it could be my ISP. The error does incorporate AVG which is my anti virus and their forums have given me things to try so I'm covering all options.

So here goes....

This is what I posted on the AVG forums.

Quote:

As part of my GoDaddy account I have a number of POP3 accounts. I've not needed to use them until now but it would seem AVG is blocking them somehow and I can't work out why. I've setup the account in OE6 and GoDaddy have confirmed the settings are correct but still I get the following error.

The server responded with an error. Account: 'C (webestry.biz)', Server: 'pop.secureserver.net', Protocol: POP3, Server Response: '-ERR AVG POP3 Proxy Server: Cannot connect to the mail server!', Port: 110, Secure(SSL): No, Server Error: 0x800CCC90, Error Number: 0x800CCC90

I've scoured the net for a solution and tried a few options including adding the server details to AVG but it wont let me as it states the port is already in use which is correct. I've also tried to telnet to the server but that fails also.

As you can see from the error there's an AVG reference hence me posting this here. I've tried turning off AVG and removing the open files in task manager but get no joy. I've also tried disabling the server in AVG but get the following message.

The connection to the server has failed. Account: 'C (webestry.biz)', Server: 'pop.secureserver.net', Protocol: POP3, Port: 110, Secure(SSL): No, Socket Error: 10065, Error Number: 0x800CCC0E

I was hoping adding a server would solve it but as I've said above it wont let me and I can't change the current one as it's for my ISP. I've other non-ISP emails set up and they work fine. I'm not sure it is an AVG thing to be honest but have to check all the options. GoDaddy say they think it's my ISP but a friend had similar problems but on the SMTP side which he fixed. We've had no jot with the POP3 one though.

Any help gratefully appreciated.

Cheers

The full thread is at http://forum.grisoft.cz/freeforum/re...backpage=2,sv=

As you can see they're talking SMTP when the error clearly states a POP3 problem. I can send ok from the account. It just wont receive. I've tried to telnet to the server and get the following....

Quote:

-ERR AVG POP3 Proxy Server: Cannot connect to the mail server!

Connection to host lost.

As you can see there's the AVG reference again. I've tried setting up a seperate server reference in AVG but all that tells me is that the port is already in use and wont let me.

So basically I'm hitting brick walls.

Any advice appreciated and any further info needed then please shout up.

Cheers

C

AbyssUnderground · 04-12-2007, 11:32

Try disabling the POP3 checker on AVG and trying again. POP is not blocked, I can guarantee that as a fact. Neither is SMTP.

cmk · 04-12-2007, 11:35

I tried that and got a different error message as I've said above.

For the record Go Daddy say to use 80 for SMTP and 110 for POP.

AbyssUnderground · 04-12-2007, 12:23

Quote:

Originally Posted by cmk

I tried that and got a different error message as I've said above.

Whoops, missed that. Can you ping the POP address? Maybe the POP server is down?

cmk · 04-12-2007, 13:04

If I ping secureserver.net I get....

Quote:

Pinging pop.secureserver.net [64.202.165.92] with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for 64.202.165.92:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

If the POP server was down for as long as I've been trying to sort this I'd have heard of more instances of people having problems to be fair.

I guess one option is to uninstall AVG and see what that throws out if anything at all. Thing is I've not heard of there being an issue between Go Daddy and AVG. I don't know anyone else using them along with an NTL/Virgin Media connection so I'm kind of thinking it's something to do with that. The AVG reference in the OE error message contradicts that a slight though.

bayonet · 04-12-2007, 13:55

I had an issue with the AVG smtp server and Zone Alarm outbound mail try turning the AVG smtp checker off

cmk · 04-12-2007, 14:06

I'll try it but look at the error message. It's the POP server.

AbyssUnderground · 04-12-2007, 16:48

That tells you its probably a DNS error. Try changing your DNS servers to openDNS and try again. If not, try using a proxy. Its just getting stuck in the transition from your pc to the pop server. Maybe do a tracert to it as well if it even works.

brundles · 04-12-2007, 17:36

Are you using any firewall software? I've seen something similar before where the firewall blocks the AVG proxy which in turn kills your POP access from the mail client.

cmk · 06-12-2007, 10:23

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

cmk · 07-12-2007, 09:41

AVG are now refusing to help saying it's not a problem with their software.

http://forum.grisoft.cz/freeforum/re...backpage=2,sv=

I posted the above results to Go Daddy who to be fair are usually very good techie wise and got the following which I'm a little reluctant to try due to being left wide open security wise.

Quote:

We apologize for any inconvenience or confusion, however, it does not appear that you are able to reach the pop server at pop.secureserver.net. Please attempt to temporarily disable your Anti Virus, Firewall, or any other Internet Security Software as it appears something on your computer is preventing access from resolving pop.secureserver.net to an IP address.

Any help appreciated.

Cheers

**Paul** · 07-12-2007, 11:05

From a dos prompt, try

Quote:

telnet pop.secureserver.net 110

what happens ?

cmk · 07-12-2007, 11:30

-ERR AVG POP3 Proxy Server: Cannot connect to the mail server!

Connection to host lost.

Toto · 07-12-2007, 11:33

Looks like you need to look at AVG again.

cmk · 07-12-2007, 11:39

That's what I've been thinking but their forum is dodging it saying it's not their issue because when I disable AVG I still get an error albeit a different one.

Full AVG forums thread - http://forum.grisoft.cz/freeforum/re...backpage=2,sv=

One of their techies said "Ok... if you are still getting errors even when AVG's email scanner is disabled... those must be fixed first and that is beyond the scope of the forum... we will try to help if its only related to AVG but in this case it isn't."

to which I posted....

" I see your point but what about when I try telnet pop.secureserver.net 110 and get the following....

-ERR AVG POP3 Proxy Server: Cannot connect to the mail server!

Connection to host lost.

Is that not AVG related then."

I await their response.

The maddening thing is I've other emails all setup and working fine which would usually point to the hosting company. The majority of errors refer to AVG apart fromt he one when I disable it which I can then see what they're saying about it not being AVGs fault.

It's all doing my head in. My next test is setting it up on the laptop which I'm going to do on site later while working.

Anything else anyone can come up with would be appreciated.