Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SMTP Service smptsvc Error 2012 and 2013 1

Status
Not open for further replies.
adamroof

adamroof

Programmer
Nov 5, 2003
1,107
US
No luck on ms site to find out what to do, maybe others have had this....(i x'd out my internal ip!)
*********
event 2012 -
SMTP could not connect to the DNS server 'x.x.x.x'. The protocol used was 'UDP'. It may be down or inaccessible.

event 2013 -
SMTP could not connect to any DNS server. Either none are configured, or all are down.
***********
All dns looks good, only problem im having is email to one domain gets stuck in the SMTP queue.
 
Sort by date Sort by votes
Sorry to be a tease - but I am having the same problem. I have searched all over the net for a solution or a hint as to why it's happening and this is as close as I've come. Your comment about mail to one domain getting stuck sounded familiar. I don't know if it's related, but I have one domain that for no real reason I can find which returns an NDR. This is the NDR:
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<server.domain.local #5.7.1 smtp;550 5.7.1 Delivery not authorized, message refused>

But there is no event the corresponds with the events 2013 & 2012 to give any indication of the the real problem. Not on the Exchange 2003 server where the 2012 & 2013 events log, nor on the 2003 Server which handles the local DNS...

Any help would be greatly appreciated!
 
Upvote 0 Downvote
My last 2012 event was on 6/13/04. Why it stopped is unknown. A couple of things was done, we disconnected from an old nt4.0 domain, cleaned up all dns errors, filtered SMTP to only allow addresses in the directory, offline defrag, but most of that was done prior to 6/13...
wish i had more info for ya.
 
Upvote 0 Downvote
pkirill,

Sounds like you have been put on an RBL. Declude.com or ORDB.org. Put in your IP address and see if you are listed. That may be why you are not able to send mail to that domain.

May be a start...

Rook
 
Upvote 0 Downvote
I'm having the same exact problem.

I'm not on any Black list, iv'e checked ..

Since a while, (After no change on the server) i'm having 2012 and 2013 from SMTPSVC. It's getting very frustrating because i've search a lot the web, and all I see is people having the issue, but no solution to it ...

Anyone can help out ?

Any idea would be appreciated ...

(exch2k3 on win2k3)

- Security is a never ending job.
 
Upvote 0 Downvote
1. Check your DNS configuration. What DNS server does exchange attempt to connect to? Does it exist? is it the right one?
2. Take a trace. What protocols are used? what responses are received? Does Exchange try UDP first then fail to try TCP upon receiving a truncated response? Does the UDP request make it past the router/firewall?


Off the top of my head, I'd guess that it's related to one of the following:


There's not enough information (NEI) in your post to be more specific.
 
Upvote 0 Downvote
- I don't run Symantec the server.
- I'm not blacklisted, as far as I know.
- My DNS server are good, (I can nslookup and resolve) i've tried 2 from my ISP, and my internal one wich is synching with the root. --) Same error.
- The firewall is allowing UDP and TCP, but when i'm monitoring I only see UDP passing. So TCP is not used ...
- The server havn't been upgraded from 2k. It's was a clean install of 2k3.

I'm sorry about the missing info. Your right, it's hard to help when info is missing :(

I've looked at your solution, I think it's not applying to my existing case. Maybe the last, ill check deeper the settings ...

Thanks a lot for the reply.

Any other ideas ?

- Security is a never ending job.
 
Upvote 0 Downvote
Take a trace. If you are sending UDP first, and the distant site's firewall is set to limit UDP packet to 512 [AOL], then you'll se it in the trace. Your DNS server does not contain records for every domain. If you want to look up a record for say, AOL.com, your DNS server looks up the root hint for .com and forwards the request to one of the root servers. The forwarding goes on and on until finally the request is forwarded to a server that is authorative for the distant domain. You stated that you are seeing that you are only passing UDP. I'm betting the UDP response is truncated on the distant end; a common scenario [828263]. In that you have no control over the firewall at the distant end, I'd go with the solution in 820284 so that the SMTP service will use the truncated response to complete the delivery.

 
Upvote 0 Downvote
Thanks xmsre for your relevant post.

Iv'e just done the 820284 and still having the same result.

Do you think I need to reboot the server ?

thanks again ...

- Security is a never ending job.
 
Upvote 0 Downvote
I believe that requires an IIS restart. You could reboot, whichever is easiest for you.

 
Upvote 0 Downvote
Hummm.

Ive done everything on this post and nothing helps.

But if anyone is having the same trouble, I highly recommand to try those things suggested by other posters up there. It really make sense ...

But in my case, it did not solve the problem. The only way I found to get trough was to configure my exchange server as an DNS server (internal) and to forward DNS queries to other DNS on my network, and the one of my isp if the internal one doesn't answer ...

In the SMTP config I put the local adresse on the exchange server (now dns) to answer to DNS queries ...

After done this, all the messages are going out, and no error are found in the event log ...

Go figure, I double checked everything ...

Thanks again all for your help.



- Security is a never ending job.
 
Upvote 0 Downvote
Also consider thoses links if you use a PIX in front of your exchange server ...
(Some may apply also to other firewall ...)




Sry for posting all that info but I really had a bad time with that problem and if it can help anyone, ill be pleased !!!

LAterz


- Security is a never ending job.
 
Upvote 0 Downvote
Having the same Event ID:2013, SMTP could not connect to any DNS server. Either none are configured, or all are down.
can someone tell me why it's doing this and how to fix the problem?

Thanks
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

m245
  • Locked
  • Question
Adding a disclaimer for all outgoing emails in Exchange 2013 Standard Edition
Replies
0
Views
2K
m245
m245
david jackson
  • Locked
  • Question
Extract only the subject and recipients from a mailbox
Replies
0
Views
2K
david jackson
david jackson
Rohit Bareja
  • Locked
  • Question
View and access only own records, and not the records by others on SharePoint.
Replies
3
Views
2K
garysm
garysm
sysadmin2018
  • Locked
  • Question
Exchange 2013 Mailflow
Replies
0
Views
97
sysadmin2018
sysadmin2018
watsson7278
  • Locked
  • Question
USB Error
Replies
1
Views
118
strongm
strongm

Part and Inventory Search

Sponsor

Back
Top