Re: Winsock Error 10066.. maybe MTU related proble (General questions)

by Amedeo, Thursday, April 16, 2009, 16:44 (5701 days ago) @ wodSupport

Amedeo,
wodSmtpServer does nothing special related to winsock.. (cut)..
..you should perform some MTU related tests .. (cut)
Kreso

In these days i've done lots of tests, then i've turned my two testing PCs (1->WinXP-SP3 and 2->Win2k3-SP2 R2 Server) to their default values (netsh winsock reset && netsh int ip reset) and tested again.

I cannot find any 'logic consequence' ..so i can say that maybe mtu (and related params) doesn't relates the problem (was the unic clue i found googling about similar problems).

As said in past message, i've done a little 'trap' by which i can report myself the problem/event.
App send me back a message in which i can see (tipically):

---------------------------------------------------
Winsock ErrorCode: 10060
Winsock ErrorText: The current connection has timeout.
Relay.State: 0
Relay.StateText: Not yet connected - waiting.
Relay.RetryCount: 4
Relay.LastResponse: 354 Enter mail, end with CRLF.CRLF
---------------------------------------------------

In my little app, after 4 retry, i give up and send back to the sender a NDR (and a debug message to me if winsock error occurs).

So.. the smtp dialog is ok, when it's time to submit the message (354 Enter mail, end with CRLF.CRLF) there is not connection ?!? ..surely caused by the winsock error.

If u have ideas .. thanx