Re: xexch50 - server performance reports...After SP2

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

Cris,

It's a typical response from an exchange server when the name doesn't match.

--
Claus
"Cris Hanna [SBS-MVP]" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message news:9B3782B0-1335-4FC4-B00A-0BCE55D5F8EE@xxxxxxxxxxxxxxxx
So why would there be a request to authenicate first error if its just a
case of connecting to another server for delivering mail if its just a
case of name mismatch?
should that be "anonymous"?

--
Cris Hanna [SBS-MVP]
------------------------------
Please do not contact me directly, only respond in the Newsgroups
MVPs do not work for Microsoft
------------------------------
Send via Windows Mail on Vista Ultimate connected to SBS 2003 R2
"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:%23448s$YwHHA.484@xxxxxxxxxxxxxxxxxxxxxxx
None of my servers are doing it but than, none of my servers have W2K3
SP2 installed. I will wait another month or so before updating.

There are numerous reasons for the XEXCH50 to come up. One of the most
common ones is that your virtual SMTP server doesn't have the correct
FQDN (needs to be the same as the one your MX record points to).

--
Claus
"Teneo" <not@xxxxxxxx> wrote in message
news:uSmXIhYwHHA.1168@xxxxxxxxxxxxxxxxxxxxxxx
Many thanks Claus,

It would be nice to know why post SP2 servers are doing this, I wonder
if non SP2 have this entry... will post back.


"Claus" <cjobes@xxxxxxxxxxxxx> wrote in message
news:OadmtaYwHHA.3720@xxxxxxxxxxxxxxxxxxxxxxx
As a workaround you can suppress XEXCH50 calls

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SMTPSVC\XEXCH50
If your don't see that subkey, create it.
Create a DWORD value with the name SuppressExternal and give it a value
of 1.


--
Claus
"Teneo" <not@xxxxxxxx> wrote in message
news:OClFzCYwHHA.484@xxxxxxxxxxxxxxxxxxxxxxx
All servers (SBS 2003 NOT R2) updated with SP2 have been giving this
error:- (delivering to another exchange 2003, not an ISP pop3 mailbox)

This is an SMTP protocol error log for virtual server ID 1, connection
#122. The remote host "xxx.xxx.xxx.xxx", responded to the SMTP command
"xexch50" with "504 Need to authenticate first ". The full command
sent was "XEXCH50 1052 2 ". This will probably cause the connection to
fail.

The time of the reported error relates to an email that was actually
delivered.

All servers yet to have SP2 applied not reporting this error.

Anyone know what configuration has changed for SP2 servers to send
XECH50 commands when this should only be going between exchange
servers in the same domain.











.

Relevant Pages

  • Re: Applying SBS 2k3 SP1
    ... You do not need W2K3 SP2 for IMF. ... you can remain at SP1 for SBS and for W2K3 and still can upgrade Exchange to ... another tip here about upgrading SBS 2003 to SP2. ... I have applied Windows 2003 Sp2 to all the servers and also Exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: Upgrade to SP2 after DST 2007
    ... You will need to apply the Exchange 2003 sp2 cdo patch. ... need to upgrade our servers to SP2. ... with the SP2 patches or will I be ok since I ran the SP1 patches? ...
    (microsoft.public.exchange.admin)
  • xexch50 - server performance reports...After SP2
    ... (delivering to another exchange 2003, ... The time of the reported error relates to an email that was actually ... Anyone know what configuration has changed for SP2 servers to send XECH50 ... commands when this should only be going between exchange servers in the same ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Errors
    ... Does SP2 apply to the Exchange in SBS 2003 Standard? ... All Domain Controller Servers in use are ... These events are normally logged at boot on a SBS machine. ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA - Windows 7 - Red Cross
    ... got it on all 6 SBS 2003 servers that I manage (and we had the Red X ... The problem is that it is for Exchange 2003, with a min of Exchange SP2 ... I have an SBS 2003 server, and my users access their email via OWA ...
    (microsoft.public.windows.server.sbs)