Clavik
Advanced Member | Редактировать | Профиль | Сообщение | ICQ | Цитировать | Сообщить модератору
MAKSIM_FILIPPOV
1. Проверь telnet'ом коннект на 25 порт на этот хост и на другие.
2. Что с отправкой на другие серваки? Также нет коннекта на 25 порт?
Цитата: Thu 2009-03-05 10:52:39: * Winsock Error 10053 Соединение отменено.
Thu 2009-03-05 10:52:39: Ошибка соединения сокета |
Цитата: 1. Ping the remote host you were connected to. If it doesn't respond, it might be off-line or there may be a network problem along the way. If it does respond, then this problem might have been a transient one (so you can reconnect now), or the server application you were connected to might have terminated (so you might not be able to connect again).
2. Ping a local host to verify that your local network is still functioning (if on a serial connection, see next step)
3. Ping your local router address. If you're on a serial connection, your local router is the IP address of the host you initially logged onto with SLIP or PPP.
4. Ping a host on the same subnet as the host you were connected to (if you know one). This will verify that the destination network is functioning.
5. Try a "traceroute" to the host you were connected to. This won't reveal too much unless you know the router addresses at the remote end, but it might help to identify if the problem is somewhere along the way. |
Что-то фильтрует скорее всего или неправильная настройка сетки.
С Alt-n:
Цитата: How can I prevent Winsock error 10053?
KBA-01510
Question
Winsock error 10053 seems to be occuring on SMTP mail to and from MDaemon.
Answer
Winsock error 10053 usually occurs with routers, firewalls and proxies. Are you using any of these? If you're using a router, please be sure that the MTU setting is at 1500. Then, see if this resolves your issue. If not, double check the MTU setting on the MDaemon server (the MTU setting is in the registry).
Here's more on Winsock 10053:
WSAECONNABORTED (10053) Software caused connection abort
A connection abort was caused internal to your host machine. The software caused a connection abort because there is no space on the socket's queue and the socket cannot receive further connections.
WinSock description: The error can occur when the local network system aborts a connection. This would occur if WinSock aborts an established connection after data retransmission fails (receiver never acknowledges data sent on a datastream socket).
TCP/IP scenario: A connection will timeout if the local system doesn't receive an (ACK)nowledgement for data sent. It would also timeout if a (FIN)ish TCP packet is not ACK'd (and even if the FIN is ACK'd, it will eventually timeout if a FIN is not returned). |
|
