Re: Event ID: 2012 / 2013 SMTPSVC [ANNOYING ANNOYING ANNOYING]

From: RandyH (RHollaw_at_HotMail.com)
Date: 05/03/04


Date: Mon, 3 May 2004 13:52:46 -0400

Adding the PTR record did not help. Event ID's 2012 and 2013 are filling up
the logs every hour on the hour....

HOTFIX HOTFIX HOTFIX........

"RandyH" <RHollaw@HotMail.com> wrote in message
news:%23YOJmEfLEHA.3944@tk2msftngp13.phx.gbl...
> Thanks, I ran ipconfig/registerdns although I had A records for the
machine,
> what I did just notice that there wasn't a PTR record for that machine,
I've
> added the PTR record to DNS, we shall see.
>
> Thanks Richard for your post!!!
>
> fyi, i rebooted the exch srvr yesterday morning, i was getting sick of all
> the red and yellow events filling up my logs, since rebooting, the error
> hasn't been recorded, but i've noticed that before on previous reboots. I
> will see if the error returns....................
>
> "Richard Roddy [MSFT]" <rroddy@online.microsoft.com> wrote in message
> news:Dz5$XKeLEHA.1136@cpmsftngxa10.phx.gbl...
> > I found the following in a prior support case. See if any of this helps
at
> > all in figuring out what might be going on:
> >
> > *** Problem Description ***
> > 1. We are receiving Events 2013 and 2012 for the SMTPSVC in the System
Log
> > of an
> > Exchange 2003 server
> > Event Type: Error
> > Event Source: smtpsvc
> > Event Category: None
> > Event ID: 2013
> > Date: 11/3/2003
> > Time: 8:17:09 AM
> > User: N/A
> > Computer: SERVERNAME
> > Description:
> > SMTP could not connect to any DNS server. Either none are configured, or
> > all are
> > down.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 7c 26 00 00 |&..
> >
> > Event Type: Warning
> > Event Source: smtpsvc
> > Event Category: None
> > Event ID: 2012
> > Date: 11/3/2003
> > Time: 8:17:09 AM
> > User: N/A
> > Computer: SERVERNAME
> > Description:
> > SMTP could not connect to the DNS server '10.250.1.55'. The protocol
used
> > was
> > 'UDP'. It may be down or inaccessible.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: d5 04 00 00 Õ... .
> >
> > 2. We are also getting these events on the Exchange 2003 server and on
the
> > DNS
> > server for the domain:
> > Event Type: Information
> > Event Source: DnsApi
> > Event Category: None
> > Event ID: 11160
> > Date: 11/3/2003
> > Time: 10:42:19 AM
> > User: N/A
> > Computer: SERVERNAME
> > Description:
> > The system failed to register pointer (PTR) resource records (RRs) for
> > network
> > adapter
> > with settings:
> >
> > Adapter Name : {AA5ABF3D-3F13-4BE7-BA1E-5C40F618DAE5}
> > Host Name : SERVERNAME
> > Adapter-specific Domain Suffix : office.compunet1.com
> > DNS server list :
> > 10.250.1.55
> > Sent update to server : 192.175.48.1
> > IP Address : 10.250.1.56
> >
> > The reason that the system could not register these RRs was because of a
> > security
> > related problem. The cause of this could be (a) your computer does not
> have
> > permissions to register and update the specific DNS domain name set for
> > this
> > adapter, or (b) there might have been a problem negotiating valid
> > credentials with
> > the DNS server during the processing of the update request.
> >
> > You can manually retry DNS registration of the network adapter and its
> > settings by
> > typing "ipconfig /registerdns" at the command prompt. If problems still
> > persist,
> > contact your DNS server or network systems administrator.
> >
> > For more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 39 23 00 00 9#..
> >
> >
> >
> >
>
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
> > <>
> > *** Resolution ***
> >
> > 1. We analyzed MPS reports taken from both domain controllers in the
> domain
> > and the
> > Exchange 2003 server.
> > 2. All looked clean except for a couple obsolete domain A records for a
> > domain
> > controller that was no longer in the domain.
> > 3. We deleted the obsolete domain A records for the domain controller
that
> > no
> > longer existed.
> > 4. We also removed DNS from a secondary DC (which the customer did not
> want
> > it to
> > be a DNS server any longer).
> > 5. After the above actions, the missing PTR records populated.
> > 6. The Event IDs 2012 and 2013 are no longer occurring in the System Log
> of
> > the
> > Exchange 2003 server.
> >
> >
> > Thanks,
> > Richard Roddy
> > Microsoft Exchange Support
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > --------------------
> > >Reply-To: "RandyH" <RHollaw@HotMail.com>
> > >From: "RandyH" <RHollaw@HotMail.com>
> > >References: <ubNDkCFLEHA.3808@TK2MSFTNGP12.phx.gbl>
> > <408E7636.80722B06@nomail.phxint.please.ru>
> > <#IA$YmGLEHA.2400@tk2msftngp13.phx.gbl>
> > <408F721F.F8C82C1E@nomail.phxint.please.ru>
> > >Subject: Re: Event ID: 2012 / 2013 SMTPSVC [ANNOYING ANNOYING ANNOYING]
> > >Date: Wed, 28 Apr 2004 08:06:54 -0400
> > >Lines: 18
> > >Organization: http://www.Randy.Hollaway.com
> > >X-Priority: 3
> > >X-MSMail-Priority: Normal
> > >X-Newsreader: Microsoft Outlook Express 6.00.2800.1409
> > >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
> > >Message-ID: <##oXLlRLEHA.1144@TK2MSFTNGP12.phx.gbl>
> > >Newsgroups: microsoft.public.exchange.admin
> > >NNTP-Posting-Host: 15.002-ridc-1.fwb.nauticom.net 66.212.158.16
> > >Path:
> >
>
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12
> > phx.gbl
> > >Xref: cpmsftngxa10.phx.gbl microsoft.public.exchange.admin:424682
> > >X-Tomcat-NG: microsoft.public.exchange.admin
> > >
> > >Thanks, I've watched that before. Nothing I've come across actually
> > >addressess this error. I know from the emails I get from other ppl,
that
> I
> > >am not the only one getting this error.
> > >
> > >
> > >"Kirill S. Palagin" <kpalagin@nomail.phxint.please.ru> wrote in message
> > >news:408F721F.F8C82C1E@nomail.phxint.please.ru...
> > >> See if this webcast helps
> > >> http://support.microsoft.com/default.aspx?scid=kb;en-us;324759
> > >>
> > >> RandyH wrote:
> > >>
> > >> > absolutely.
> > >> >
> > >> > <snip>
> > >>
> > >
> > >
> > >
> >
>
>



Relevant Pages

  • Re: Win2k3 Active Directory dns, dhcp errors. All linked together but cant figure it out.
    ... The Security System detected an authentication error for the server ... see Help and Support Center at ... SMTP could not connect to the DNS server '127.0.0.1'. ... source domain controller to an IP address. ...
    (microsoft.public.windows.server.active_directory)
  • Re: RENDOM /end fails
    ... see Help and Support Center at ... DNS server IP address: 154.15.251.166 ... For computers and users to locate this domain controller, ... This is not a recommended security configuration. ...
    (microsoft.public.windows.server.active_directory)
  • Re: WAY OVER MY HEAD
    ... and wireless, that points to an issue on the server, probably hardware. ... Les Connor [SBS MVP] ... see Help and Support Center at ... DNS server list: ...
    (microsoft.public.windows.server.sbs)
  • WAY OVER MY HEAD
    ... see Help and Support Center at ... Les Connor [SBS MVP] ... DNS server list: ... Sent update to server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Swing migration Q?: problem joining new DC to temp domain
    ... the new kit and support. ... Pay for a new swing kit tailored to your current scenario (as you said, ... I dig all old source server names out of dns. ...
    (microsoft.public.windows.server.sbs)