Re: Error 1722 Event ID 9322

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Jim (Jim.Hammar_at_intec.us)
Date: 02/10/04 

Date: Tue, 10 Feb 2004 11:01:27 -0800

Added host entry
Can ping by FQDN to both servers.
Also RPing fails on both servers

>-----Original Message-----
>This is most likely a DNS related issue. With SP4, we
depend more on DNS
>than WINS resolution.
>
>You mention you can ping by name, is that NetBIOS name or
FQDN (i.e.
>server.domain.com)?
>
>Try adding an entry in the host file with the FQDN of the
destination server
>(try this on both servers).
>
>279537 XCON: Post-Service Pack 3 MTA Bindback String
Changes
>http://support.microsoft.com/?id=279537
>
>--
>Cheers,
>
>Steve Antonio
>Microsoft Exchange Support
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>Note: Please do not reply to this e-mail address. It is
used for newsgroup
>purposes only.
>
>
>"Jim" <Jim.Hammar@intec.us> wrote in message
>news:dd7101c3eff7$febdfb90$a001280a@phx.gbl...
>> BTB - It's a w2k box with Exchagne 5.5 connecting to
>> another w2k box with 5.5 both SP4
>> >-----Original Message-----
>> >Can anyone give me guidance on this error beyond what
is
>> >in Technet.
>> >I can ping by name. I can Net view. I can Net use. I
have
>> >added a record to both DNS and LMHost file. I have
>> >rebooted till I feel like a cowboy. I have reloaded the
>> OS.
>> >I have changed NIC cards. Any help greatly appreciated.
>> >
>> >An interface error has occurred. An MtaBindBack over
RPC
>> >has failed. Locality Table (LTAB) index: 4, NT/MTA
error
>> >code: 1722. Comms error 1722, Bind error 0,
>> > Remote Server Name INTECDALEX1, Protocol String
>> >ncacn_ip_tcp:intecdalex1.chasdal[1047] [BASE IL
INCOMING
>> >RPC 41 507] (14)
>> >.
>> >
>
>
>
>.
>

Relevant Pages

  • Event ID 13508
    ... I can ping all servers using FQDN. ... The File Replication Service is having trouble enabling replication from ...
    (microsoft.public.windows.server.active_directory)
  • Re: Error Joining Domain - Service Not Responding in Timely Fashio
    ... Make sure that the servers are able to ping ... > problem with your DNS or your DNS search scope. ... FQDN and NetBIOS name. ...
    (microsoft.public.win2000.active_directory)
  • Re: the dsa operation is unable to proceed because of a dns lookup failure
    ... All servers are connected to the domain and pingable. ... You can ping all servers from each other by FQDN ex: ... >use the Domain Controller with the AD integrated DNS ...
    (microsoft.public.win2000.active_directory)
  • Re: Duplicate SPN - but unsure how to fix!
    ... FQDN of the SQL servers is used. ... Computer DNS: SQL01.child.domain.net ... Both your SQL01 servers should have SPNs registered in their FQDNs. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Duplicate SPN - but unsure how to fix!
    ... I dont think you should have a problem if the FQDN of the SQL servers is used. ... the SPNs are registered correctly and the errors or event id: 11 are generated when the netbios name is used to request the service ticket. ... Computer DNS: SQL01.child.domain.net ...
    (microsoft.public.windows.server.active_directory)