Mails for sending are stuck in a queue

Mails for sending are stuck in a queue (Full Version)

All Forums >> [Microsoft Exchange 2000] >> Message Routing

Message

tcs -> Mails for sending are stuck in a queue (26.Jul.2006 9:59:17 AM)
Hi all Got a problem with a client running Exchange 2000. They are receiving mail in OK but anything being sent is stuck in the queue. The server has been rebooted and all the neccessary services have started OK. There aren't any errors in Event Viewer. Where can I start looking? Are there any test's I can do to see where its falling over? I'm an Exchange newbie so any help appreciated!!!

malkeet -> RE: Mails for sending are stuck in a queue (19.Aug.2006 1:38:12 PM)
Hello TCS, What kind of mails are getting struck in the queue. Are mails pretaining to subject domain are piling the queue or its for the domains. Also advise what kind of internet connectivity ur using for relaying the mails. regards malkeet

khowlette -> RE: Mails for sending are stuck in a queue (22.Aug.2006 11:17:39 PM)
Hi Ken Guess who, I suppose its you know you again. Use the SMTPDiag tool, freebie from MS and this gives you a good insite to whats going on. Keith

srei -> I have the same problem. What to do? (4.Oct.2006 2:47:57 PM)
Hi all! I have the same problem, outgoing messages are stuck in queue and are not being delivered to the recipients. I have tested with SmtpDiag, and here's what it shows: Searching for Exchange external DNS settings. Computer name is SRV0. VSI 1 has the following external DNS servers: 195.222.130.67,195.222.142.34 Checking SOA for perm.ru. Checking external DNS servers. Checking TCP/UDP SOA serial number using DNS server [195.222.130.67]. TCP test succeeded. UDP test failed. Serial number: 2006100402 Checking TCP/UDP SOA serial number using DNS server [195.222.142.34]. TCP test succeeded. UDP test failed. Serial number: 2006100402 Checking internal DNS servers. Checking TCP/UDP SOA serial number using DNS server [10.0.1.1]. Failed: DNS server [10.0.1.1] may be down. Checking TCP/UDP SOA serial number using DNS server [127.0.0.1]. Failed: DNS server [127.0.0.1] may be down. Checking TCP/UDP SOA serial number using DNS server [195.222.130.67]. TCP test succeeded. UDP test failed. Serial number: 2006100402 SOA serial number match: Passed. ... And then MX records were checked, and the program has connected to the remote port 25. 195.222.130.67 is our ISP's IP-address of their DNS-server, which we are using. I'm wondering why our own DNS-Server doesn't answer to the DNS-queries. Well then I've opened TELNET and sent a testing email to an outside server, it was send and delivered correctly at the moment. So I see, that our server connects to outside servers on port 25 normally through telnet, but the Exchange 2000 Server doesn't do that. What can I do to figure out the problem?

khowlette -> RE: Mails for sending are stuck in a queue (5.Oct.2006 2:32:25 PM)
Hi Did you run the SMTP diag on your Exchange server. Check that you internal DNS servers are forwarding to the ISP. Set you exchange servers DNS to your internal DNS servers. Did you telnet from the Exchange server, this should confirm if its a firewall problem. Telnet to the ISP on port 25 if you get no response they are blocking you. Are you using a smart host in your SMTP server setting. Try taking this out. Your ISP may be blocking mail relay from your exchange server, so you will need to talk to them and get them to allow relaying from your server. You may also need to have a pointer record for your MX record. e.g. if your domain is somedomain.com and the MX returns mail.somedomain.com you'll need a PTR record for mail.somedomain.com. Some ISP's and site won't allow you to send mail unless you have a PTR record. Hope this helps

srei -> RE: Mails for sending are stuck in a queue (6.Oct.2006 6:58:43 AM)
Hi khowlette! Thank you for your replying. Yes, I confirm that SmtpDiag has been run on the Exchange Server. Actually, it's our one and only server, which acts as Domain Controller, DNS server, Mail Server, File Server and all other roles. Windows 2000 Server + ISA 2000 Server + Exchange 2000 Server. I am not so skilled at DNS, so I'm not sure if it's configured properly, everything was working and now outgoing mail is stuck in queue for some unknown reason without any modifications. I've checked what's set in the DNS Server snap-in. It accepts DNS queries from all interfaces, so it shows that all IP addresses of the server are included. Then it performs DNS queries to two DNS servers of our ISP, thoser are 195.222.130.67 and 195.222.142.34 Though if I run nslookup and type any LAN host, it returns the reply quickly, but if I type any external internet host (by IP or by name) it returns "DNS request timed out. timeout was 2 seconds. *** Request to srv0.razv.local timed-out." Trying to set the IP of ISP's DNS Server as second parameter for nslookup query doesn't help also, the request is timed out anyway. Although if I type any hostname in a web-brouser, it opens pages normally, which means that DNS queries initiated by a web-brouser are performed correctly. In "Default SMTP Virtual Server" -> "Properties" -> "Delivery" -> "Advanced" external DNS servers are configured as those two IPs of our ISP. Connecting to 25 port of any server via telnet is performed smoothly, I've sent messages to our server and to internet mail servers this way, and they were delivered. We are not using any smarthost. Where do I check if we have a PTR record? http://www.dnsstuff.com/tools/lookup.ch?name=razv.ru&type=PTR It says that we haven't one, if I have understood it right.

srei -> NetDiag (6.Oct.2006 7:31:59 AM)
DNS test . . . . . . . . . . . . . : Failed [WARNING] Cannot find a primary authoritative DNS server for the name 'srv0.razv.local.'. [ERROR_TIMEOUT] The name 'srv0.razv.local.' may not be registered in DNS. [FATAL]: The DNS registration for 'srv0.razv.local' is incorrect on all DNS servers. PASS - All the DNS entries for DC are registered on DNS server '10.0.1.1' and other DCs also have some of the names registered. [WARNING] The DNS entries for this DC cannot be verified right now on DNS server 195.222.130.67, ERROR_TIMEOUT. PASS - All the DNS entries for DC are registered on DNS server '127.0.0.1' and other DCs also have some of the names registered.

srei -> Problems is solved! It was a DNS & VPN related problem. (6.Oct.2006 10:10:19 AM)
I am glad to report that I have solved the problem. The DNS server was configured to accept queries only from predefined IP addresses of the server itself (DNS server, Exchange 2000 Server, Domain Controller and everything else on one machine). When some VPN client has connected to the server, a new additional IP which wasn't listed in DNS server was taken, and since then all queries from Exchange, and from nslookup, and from every other application were made as from that new IP. That's why they were declined, and that's why Exchange couldn't send out any message. Right now I am checking out "Routing and Remote Access" to find out how to get rid of such a strange behavior when a machine takes an additional IP. Probably command prompt applications NETSH and ROUTE will help me with that. I hope that this report will be userful for the readers. :)

Page: [1]