I'm having a problem sending mail. The mail is just sitting in the queue and says that the remote server did not respond to a connection attempt. I've run an NSLOOKUP for MX records for those domains, found them, did a telnet in and sent mail ok. originally i was havinga DNS problem, because an nslookup/mail test failed. I assumed the issue had to do with this, but upon fixing the DNS issue im still having this problem. Symantec Mail Security is installed as well, but im not seeing anything that would indicate a problem with this. I am able to get mail just fine, just not able to send it. what is the next step and finding out why exactly the queue is saying it cant connect? Thanks Justin

What is the version of Exchange? Did this just start happening or a new install? HAve you tried to disable AV? Are you passing off to a smarthost or is this server delivery directly to the internet?Tim Harrington - Catapult Systems - http://HowDoUC.blogspot.com

sorry, thought i put the version. its 2003 SP2. This just started to happen. its been installed for some time. I dont typically manage the machine and was told that nothing major changed (filter rules are added some time, but its a standard procedure) I will try to disable the AV and see if that has any impact. no, its direct to the net. Thanks Justin

i stopped the mail security process and there doesnt seem to be any difference. is there a log or something i can use to see what is going on with the queues? All i get is the queue in a retry state and it telling me the remote server didnt respond. is there a way to see what the remote server was?

Hello jrich, AS u told that Symantec Mail security is installed on the server 1) Checked the Symantec software on the server Disabled the Internet Auto-Protect feature on Symantec Antivirus 2) If possible then uninstalled the Symantec software and reboot the server 3) on Win2003 server then ran command on CMD -- Netsh int ip set chimney DISABLED 4) On the DNS console à DNS server propertyà Add the IP 4.2.2.2 on the Forwarders Ran command on CMD -- ipconfig /flushdns & ipconfig /registerdns 5) Also checked the Network card on the server & also the Binding or of NIC card should be correct 6) Run iisreset on CMD on the exchange server It will fix the issue. EXCHANGE2010, MCSE, MCTS, MCSA MESSAGING, CCNA & GNIIT

So i turned on diagnostic logging and i get this... "Message delivery to the host '69.147.125.65' failed while delivering to the remote domain 'yahoo.com' for the following reason: The remote server did not respond to a connection attempt." so i tried to telnet to 69.147.125.65 on port 25 and get a connection failed doing an NSLOOKUP i get a handful of mail servers back, basically a-k of n.mx.mail.yahoo.com, oddly, none of those resolve to the address above. it does resolve as a yahoo address tho: ir1.fp.vip.re1.yahoo.com I just rebooted the server and it seems to be fine now... not really sure what happened, but it was getting some bad DNS info from some place... Thanks

Hello jrich, Did you tried the steps provided by me (PKT_) ? I already told that it was because of DNS or Network issues that way i provided those steps. Please do that and then also contact your ISP & checked with them also. It will help you.EXCHANGE2010, MCSE, MCTS, MCSA MESSAGING, CCNA & GNIIT

On Fri, 20 Aug 2010 20:45:31 +0000, jrich wrote: > > >i stopped the mail security process and there doesnt seem to be any difference. > >is there a log or something i can use to see what is going on with the queues? Not with the queues, but there's the SMTP protocol log. Check the SMTP Virtual Server's property page to see if you have loggin enabled and where the log files are written. I'd also check ALL the boxes on the advanced tab of the logging properties. The small amount of information logged by default is usually insufficient to help very much. >All i get is the queue in a retry state and it telling me the remote server didnt respond. is there a way to see what the remote server was? If the machine doesn't accept a connection there won't be anything in the log file. As a quick check, you can use "telnet <ip-address> 25" from the Exchange server. Get the IP address from the nslookup of the domain's MX record(s). You should bet a 220 banner of the connection's successful. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

<I just rebooted the server and it seems to be fine now... not really sure what happened, but it was getting some bad DNS info from some place...> From the symptoms, it sounds like it could also be bad route information.[string](0..33|%{[char][int](46+("686552495351636652556262185355647068516270555358646562655775 0645570").substring(($_*2),2))})-replace " "

Hi Justin, This symptom can occur by incorrect DNS record and it’s highly recommended to perform PKT’s suggestions if the mail still hangs at queue. If the issue persists, I suggest you refer to the following article to diagnose Exchange 2003 Related SMTP and DNS Problems via SMTPDIAG. http://www.msexchange.org/tutorials/SMTPDIAGdiagnose-Exchange-2003-SMTP-DNS.html Thanks.Novak Wu-MSFT