Exchange 2003 Ent Ed Sp1
Windows 2003 Server
thanks,
Zev
This discusses ways for the remote org to handle exch50 communication to
your org.
Your second option is to update your firewall software. Later versions of
ISA server handle the Exch50 command.
Your final option is to disable the Exch50 sink on your side. You should
only consider this if your receiving server is acting a Gateway server and
does not handle intraorg traffic between other Exchange servers. Since the
full effect is not documented and this configuration is not supported, you
should thoroughly test this before deploying.
To disable Exch50 on your server use the following steps:
C:\>cd "Program Files\Exchsrvr\bin"
C:\Program Files\Exchsrvr\bin>regsvr32 /u peexch50.dll
C:\Program Files\Exchsrvr\bin>iisreset
You can confirm EXCH50 is disabled by using "telnet localhost 25"
Issue the command, "ehlo anydomain"
Observere that "250-XEXCH50" no longer appears in the ehlo response.
Note: to reenable the EXCH50 sink ussue the command "regsvr32 peexch50.dll"
--
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.
"Zev" <Z...@zev.zev> wrote in message
news:%23XIvSnM...@TK2MSFTNGP15.phx.gbl...
Finally, unregistering the .DLL has solved my problems.
many thanks,
Zev
"Matt Kuzior [MSFT]" <mat...@online.microsoft.com> wrote in message
news:%237ohya0...@tk2msftngp13.phx.gbl...