Re: SMTPSVC - Event 2012 and 2013

anonymous_at_discussions.microsoft.com
Date: 08/31/04 

Date: Tue, 31 Aug 2004 12:02:37 -0700

Hi Tony,

You're right it doesn't seem to be a permanent fix and I
can understand why you would be leary about charging the
metabase to fix this issue... I would be afraid that it
would break something else!

I found a DNS diagnotic tool available on the Exchange
2003 website that may help you find out where the problem
is:

http://www.microsoft.com/downloads/details.aspx?
FamilyId=76CBC76B-54E8-4330-8713-
2005705A4045&displaylang=en

I haven't tried the tool myself so I can't promise
anything! I just hope it will help!

Best of luck

>-----Original Message-----
>Hello,
>Is restarting the mta a permanent fix or temporary? I
have restarted the
>servers several times since they were configured so I am
not sure that this
>solution really addresses the long term problem.
>
>I read that q-article and it disucces udp and tcp... I
have never heard of
>such a problem prior to Windows Server 2003... I am
leary of changing my
>metabase to fix this error...
>
>Thanks
>
>"Ninon Chassé" wrote:
>
>> Hello Tony,
>>
>> Did you investigate error 6527 at www.EventID.net ?
>> http://eventid.net/display.asp?
eventid=6527&eventno=1799&source=DNS&phase=1
>>
>> More specifically, I would check what Adrian Grigorof
is saying, if I were
>> you... Have you tried to restart the MTA service as
Jeff Ealy did, it seems
>> to have solved his problem with errors 2012 / 2013?
>>
>> As for me the events 2012 and 2013 haven't showed up
again so I tend to
>> believe that the problem was my ISP not my system!
>>
>> Best of luck in finding a solution!
>>
>> Ninon
>>
>> "tony adduci" <tony adduci@discussions.microsoft.com>
wrote in message
>> news:0371B466-60B9-4BFE-96A5-
9698AEC6D8F2@microsoft.com...
>> > Hello,
>> > I am also having these problems in my event viewer.
I have two exchange
>> > servers and two windows domains on one internal
subnet and they are haivng
>> a
>> > hard time periodically delivering mail between the
two of them. I also get
>> > that error: SMTP could not connect to any DNS server"
>> >
>> > I added secondary zones to each server one for
eachothers domain and that
>> > doesn't seem to help. I also see timeout errors
relating to DNS in my
>> event
>> > viewer...
>> >
>> > That error is: 6527 zone companyname.com expired
before it could obtain a
>> > successful zone transfer or update from a master
server....
>> >
>> > Any ideas?
>> >
>> > "Ninon Chassé" wrote:
>> >
>> > > Hi Jeff!
>> > >
>> > > Are your logs still clear of these errors?
>> > >
>> > > Ninon
>> > >
>> > > "Jeff Ealy" <jealy@omniumworldwide.com> wrote in
message
>> > > news:eauKEO4iEHA.1712@TK2MSFTNGP09.phx.gbl...
>> > > > Weird.. I had a different issue this morning and
stopped the MTA
>> service.
>> > > > Since I stopped it, none of the 2012 or 2013
errors have appeared.
>> > > >
>> > > > Jeff
>> > > > "Ninon Chassé"
<anonymous@discussions.microsoft.com> wrote in message
>> > > > news:024201c48ae1$65735b30$a301280a@phx.gbl...
>> > > > Hi Antonio,
>> > > >
>> > > > No, I haven't found anything yet and these
errors showed
>> > > > up only twice since this Exchange 2003/Windows
2003
>> > > > Server was put into production, a year ago. I
haven't
>> > > > noticed any problems with e-mails delivery, the
queue is
>> > > > clean and I haven't received any complaints from
the
>> > > > users.
>> > > >
>> > > >
>> > > > The only things I've noticed today is that my
ISP had or
>> > > > are having problems with their DNS servers.
>> > > >
>> > > > If I find anything, I'll post back.
>> > > >
>> > > > Thanks
>> > > >
>> > > > Ninon
>> > > >
>> > > > >-----Original Message-----
>> > > > >hi Ninon...
>> > > > >
>> > > > >I'm having exactly the same problem and I'm
having email
>> > > > delivery problems...
>> > > > >emails sent to at least one domain (all others
work
>> > > > fine) stayed queued
>> > > > >until a timeout occurs with this error
message: "SMTP
>> > > > could not connect to
>> > > > >any DNS server"
>> > > > >
>> > > > >I searched on the internet and found a site
with some
>> > > > answers to event ID
>> > > > >2013
>> > > > >(http://www.eventid.net/displayqueue.asp?
>> > > > eventid=2013&eventsource=smtpsvc)
>> > > > >where somebody posted this comment about the
problem:
>> > > > >"By default Windows 2003 uses UDP for DNS
queries. This
>> > > > can be changed in
>> > > > >the metabase. The following link should give
you all
>> > > > the details you need to
>> > > > >change to the DNS queries to TCP.
>> > > > >330070 XADM: Mail May Not Be Delivered When DNS
>> > > > Resolution Uses Only the UDP"
>> > > > >
>> > > > >so, I searched Microsoft KB database and found
the
>> > > > KB330070 article
>> > > > >(http://support.microsoft.com/default.aspx?
scid=kb;en-
>> > > > us;330070)
>> > > > >however, it only applies to Windows Server 2000
with IIS
>> > > > 4.0 or 5.0 (I'm
>> > > > >having this problem in a Windows Server 2003
with IIS
>> > > > 6.0)...
>> > > > >
>> > > > >So, I'm still looking for an answer...
>> > > > >
>> > > > >Have you come up with any development?
>> > > > >
>> > > > >
>> > > > >"Ninon ChassÃf©" wrote:
>> > > > >
>> > > > >> Thank you for your reply, Jeff.
>> > > > >>
>> > > > >> I noticed the same thing as you about mail
flow.
>> > > > >> However, something I noticed the first time
the error
>> > > > >> showed up was that our Internet connection
was down.
>> > > > >>
>> > > > >> I'll be keeping a closer look on my logs to
see if I
>> > > > can
>> > > > >> find a relation somewhere.
>> > > > >>
>> > > > >> Ninon
>> > > > >
>> > > > >.
>> > > > >
>> > > >
>> > > >
>> > >
>> > >
>> > >
>>
>>
>>
>.
>