Error Number: 0x800ccc0e when I try to get messages

[Gerard Forns]

Hello,

I am a postmaster of our network and I am having some problems with
Outlook 2000 and our pop3 server.

The problem is that randomly, Outlook's users can not download their
mail because they get the error number 0x800ccc0e when they try to
send amd receive mail.

We are using Microsoft Outlook 2000 SP-3 (9.0.0.6627) and our server
is a Linux Debian running a 2.4.27 kernel. I have tried with ipop3d
and in.qpopper as a pop3 daemons and with both I get the error.

There is no firewall between them and this is the tcpdump capture from
the server (our pop3 server runs at port 40110, but I have tried also
the 110 and it doesn't work).

$:/etc/postfix# tcpdump -n 'host <client IP> and port 40110'
tcpdump: listening on eth0
16:30:31.217256 <client IP>.1434 > <server IP>.40110: S
3418456809:3418456809(0) win 16384 <mss 1460,nop,nop,sackOK> (DF)
16:30:31.217273 <server IP>.40110 > <client IP>.1434: . ack 3341426009
win 5840 (DF)
16:30:34.177483 <client IP>.1434 > <server IP>.40110: S
3418456809:3418456809(0) win 16384 <mss 1460,nop,nop,sackOK> (DF)
16:30:34.177500 <server IP>.40110 > <client IP>.1434: . ack 1 win 5840
(DF)
16:30:40.212368 <client IP>.1434 > <server IP>.40110: S
3418456809:3418456809(0) win 16384 <mss 1460,nop,nop,sackOK> (DF)
16:30:40.212386 <server IP>.40110 > <client IP>.1434: . ack 1 win 5840
(DF)


Otherwise, when I get this error, I open a cmd and if I make a telnet
to that port I can connect with no problem. This is the captured data:


$:/etc/postfix# tcpdump -n 'host <client IP> and port 40110'
tcpdump: listening on eth0
16:47:59.471658 <client IP>.1531 > <server IP>.40110: S
68725281:68725281(0) win 16384 <mss 1460,nop,nop,sackOK> (DF)
16:47:59.471676 <server IP>.40110 > <client IP>.1531: S
3881857622:3881857622(0) ack 68725282 win 5840 <mss
1460,nop,nop,sackOK> (DF)
16:47:59.472058 <client IP>.1531 > <server IP>.40110: . ack 1 win
17520 (DF)
16:47:59.474869 <server IP>.40110 > <client IP>.1531: P 1:48(47) ack 1
win 5840 (DF)
16:47:59.622646 <client IP>.1531 > <server IP>.40110: . ack 48 win
17473 (DF)


The problem is solved killing the OUTLOOK.EXE proccess and restart
Outlook.

I don't know if it's a problem on Outlook or our Debian server, but
the other clients that use Thunerbird or mozilla don't have this
problem.

Thank you,

Gerard Forns

 

[Brian Tillman]

The problem is that randomly, Outlook's users can not download their
mail because they get the error number 0x800ccc0e when they try to
send amd receive mail. ....snip...
There is no firewall between them and this is the tcpdump capture from
the server

Another usefule diagnostic would be to enable logging on the server and in
the client to see what SMTP passes between them, if any, or what transpires
during the handshake attempt.

 

[Gerard Forns]

Ok Brian...

I have just enabled pop3 logging and tonight it has frozen another
time:

This is the output of my log:

The first connection works correctly and the second one, fails with
time out error, the language of my outlook is spanish (sorry):

POP3: 22:41:07 [db] Conectando a "my.mail.server" en el puerto 40110.
POP3: 22:41:07 [rx] +OK POP3 my.mail.server 2004.89 server ready
POP3: 22:41:07 [tx] USER gforns
POP3: 22:41:07 [rx] +OK User name accepted, password please
POP3: 22:41:07 [tx] PASS ********
POP3: 22:41:07 [rx] +OK Mailbox open, 0 messages
POP3: 22:41:07 [tx] STAT
POP3: 22:41:07 [rx] +OK 0 0
POP3: 22:41:07 [tx] QUIT
POP3: 22:41:07 [rx] +OK Sayonara
POP3: 22:41:07 [db] Conexi?n a "" cerrada.

POP3: 22:45:07 [db] Conectando a "my.mail.server" en el puerto 40110.
POP3: 22:45:28 [db] err: WSAGETSELECTEVENT = 0x10, WSAGETSELECTERROR =
10060
POP3: 22:45:28 [db] ERROR: "Fall? la conexi?n con el servidor.",
hr=2148322318
POP3: 22:45:28 [db] Conectando a "my.mail.server" en el puerto 40110.
POP3: 22:45:29 [db] srv_name = "my.mail.server" srv_addr = 84.88.0.2
POP3: 22:45:50 [db] err: WSAGETSELECTEVENT = 0x10, WSAGETSELECTERROR =
10060
POP3: 22:45:50 [db] ERROR: "Fall? la conexi?n con el servidor.",
hr=2148322318
POP3: 22:49:29 [db] Conectando a "my.mail.server" en el puerto 40110.
POP3: 22:49:29 [db] srv_name = "my.mail.server" srv_addr = 84.88.0.2
POP3: 22:49:50 [db] err: WSAGETSELECTEVENT = 0x10, WSAGETSELECTERROR =
10060
POP3: 22:49:50 [db] ERROR: "Fall? la conexi?n con el servidor.",
hr=2148322318

I have "googled" this error and I haven't been able to get any answear
to solve this problem. Some people tells that is a network error, or
that the server is slow, but we have recently migrated to a Dual Xeon
server and is connected directly to our network.

Any suggestion?

Thank's a lot,

...Gerard Forns..

 

[Brian Tillman]

POP3: 22:45:07 [db] Conectando a "my.mail.server" en el puerto 40110.
POP3: 22:45:28 [db] err: WSAGETSELECTEVENT = 0x10, WSAGETSELECTERROR > =
10060

10060 is, indeed, "connection timed out". First, try increasing the server
timeout value on the Advanced tab of the account properties pages. Then try
repeatedly connecting by hand with a telnet command to port 40110 and see if
the server times out on any of those. If it does, the problem is either in
the network components or the server and not in Outlook.

 

[Gerard Forns]

Ohhh sorry...

I think I have solved the problem... there was an access-list on our
router's interface that was blocking some outbound ports (like
tcp/4444) due to virus and worms alarms, and Outlook was using them.

I don'k know why outlook doesn't change port number when it gets a
time-out error. And persists trying to connect with that port.

So... thank's for your help, and sorry for my mistake...


....Gerard

POP3: 22:45:07 [db] Conectando a "my.mail.server" en el puerto 40110.
POP3: 22:45:28 [db] err: WSAGETSELECTEVENT = 0x10, WSAGETSELECTERROR > =
10060

10060 is, indeed, "connection timed out". First, try increasing the server
timeout value on the Advanced tab of the account properties pages. Then try
repeatedly connecting by hand with a telnet command to port 40110 and see if
the server times out on any of those. If it does, the problem is either in
the network components or the server and not in Outlook.