In the spirit of leaving no stone unturned, while I'm skeptical it could be a NIC issue, we just changed to a completely different NIC (the box has two) and using the other one instead, we get exactly the same picture. 110 and 8383 yes, 25 no.
~Simon -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Simon Dodd Sent: Tuesday, November 27, 2007 9:02 AM To: [email protected] Subject: RE: [IMail Forum] Requesting some speedy advice on send error 10054 I saw that; I got _that_ far at least. ;) But as I said in my earlier email, it doesn't match up in anything but error number. That article pertains to a situation where the "Question/Problem ... [is that m]y NIC seems to be going to sleep. The box cannot be pinged nor can it ping the outside world unless rebooted. The only place I see errors in my logs are in SYSMMDD.TXT...." As I said, the box is pingable, and both POP and webmail are running fine, and can be accessed locally and remotely. So that article can't apply. I've never heard of a problem with the NIC that affected traffic to port 25 only while leaving everything else working just fine. ~Simon -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Wolf Sent: Tuesday, November 27, 2007 8:56 AM To: [email protected] Subject: Re: [IMail Forum] Requesting some speedy advice on send error 10054 http://support.ipswitch.com/kb/IM-20020812-DM01.htm ----- Original Message ----- From: "Simon Dodd" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Tuesday, November 27, 2007 7:50 AM Subject: [IMail Forum] Requesting some speedy advice on send error 10054 I can't telnet to the server on port 25 (including from the local machine) and I'm getting lots and lots of this in the logs: 11:27 08:46 SMTPD(000A00C0) send error 10054 11:27 08:46 SMTPD(000600F8) send error 10054 11:27 08:46 SMTPD(000A00C0) send error 10054 This persists after restarting both the service and the server. Admittedly my search has not been exhaustive because this is something of a fire that needs put out, but everything I've had a chance to glance at thusfar in the list archives and googling indicates it's a problem with the NIC -- but I don't see how this can be when the box is consistently pingable and both POP and webmail work. Any ideas? Regards, Simon Dodd, Hostmaster, Joink Internet E: [EMAIL PROTECTED] T: +1 (812) 234 5100 x116 F: +1 (812) 234 5144 ------------------------ "In Critical and baffling situations, it is always best to return to first principle and simple action" - Sir Winston Churchill To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
