9215 usually happens when you have a network link slowness or errors between two Exchange servers usually in different sites. When this happens you may also see the MTA queue pile up for a while. Regards, Raj -----Original Message----- From: Harding, Devon [mailto:dharding@xxxxxxxxxxxxxxxx] Sent: Friday, February 27, 2004 9:37 AM To: [ExchangeList] Subject: [exchangelist] Event ID: 9215 http://www.MSExchange.org/ For some reason my Exchange 2000 server keeps generating event ID error: 9215. I've followed both KB articles Q170056 & Q261251 with no luck. Event ID: 9215 A sockets error 0 on a connect() call was detected. The MTA will attempt to recover the sockets connection. Control block index: 1. [BASE IL TCP/IP DRVR 11 262] (12) What could I do to get rid ofthis? Devon Harding Windows Systems Engineer Southern Wine & Spirits - GSD 954-602-2469 ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Other Internet Software Marketing Sites: Leading Network Software Directory: http://www.serverfiles.com No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security Resource Site: http://www.windowsecurity.com/ Network Security Library: http://www.secinf.net/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------