X.400 messages from Exchange 2003 to Isode 15 aren't relayed.

mark_667
mark_667 used Ask the Experts™
on
When I try to send an X.400 message from Exchange Server 2003 to an Adjacent MTA (which test binds successfully to Exchange) I can see an assosciation being made in the adjacent MTAs logs but that's it. Can anyone shed any light on what's happening in the attached event log entries from the Exchange machine?
Exchange-event-log-entries.txt
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
You say : When I try to send an X.400 message from Exchange Server 2003 to an Adjacent MTA (which test binds successfully to Exchange). Does it mean that you succeed to connect from Isode to Exchange ?
You have the check the connection from Exchange to Isode. It is a network problem
Try a ping, and then a telnet on 102 port from Exchange to Isode.
Don't you have a firewall that deny X400 port ?

Author

Commented:
>Does it mean that you succeed to connect from Isode to Exchange ?
Yes.

It's an X.400 problem, not a networking one. Pinging works fine in both directions. I can't telnet to Isode from the Exchange server on port 102 but I can't do that on ones that work with it either. Neither machine have got firewalls enabled.
Exchange Server => Isode : telnet 102 port KO
Other running Server ==> Isode : telnet 102 port KO
==> I think that Isode isn't configured to use 102 port. Can you check with netstat
Can you check telnet from Isode to Exchange on 102 port ? (and check also port used on Exchange)
Success in ‘20 With a Profitable Pricing Strategy

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Author

Commented:
Isode to Exchange also didn't work, it also failed from a working machine to Isode so I'm not reading too much into that.

I've attached the netstat output of all Isode related processes.
Isode-connections.txt
netstat shows that Isode is listening on 102 port. You have a firewall problem ! Check local firewall on your servers and allow 102 ports in both direction

Author

Commented:
As I can send to the Exchange MTA the problem's somewhere on the Exchange connector for the Isode MTA but I've given up trying to find where. As GillesT has been the only one to respond he gets the points.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial