Can't utilize Exchange 2007 receive connector from another Windows server

Hi, we are running Exchange 2007 SP1 and having a problem with the receive connector.  We'd like to be able to permit relaying through the Exchange server IP for any system on the network.  I have set up the receive connector and configured it to use port 25, to allow all network ranges to connect, and experimented with various authentication and permission groups settings.  Unfortunately, I cannot use this receive connector from 2 other Windows 2003 servers - I get an error when trying that the connection is refused, and I cannot telnet to port 25 on the Exchange server IP.  I have set up a separate receive connector utilizing port 587, tried all permutations of authentication settings (basic, Windows integrated, etc.) and tried all combinations of permission groups settings, specifically making sure Anonymous users CAN connect.  No progress on this.

What's interesting is that I CAN telnet to port 25 on the Exchange server from my Windows XP workstation.  I can telnet to the separate receive connector as well.  So, it seems like the receive connectors are working OK, but the Windows servers just can't talk to them.  I have checked firewall settings (no firewalls on any of these systems), security event logs, Receive Connector logs, but don't seem to be able to find the cause of this.  Restarted the Transport service many times as well.

Anyone have any ideas on why a Windows 2003 server can't use the receive connector but a Windows XP workstation can?  My only theory is that it has something to do with the XP workstation being a MAPI client with Outlook, etc. and it is somehow being seen as a trusted connection, whereas the Windows 2003 servers are being rejected.

Thanks in advance for any assistance anyone can provide-

jonathanchapmanAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

RammesteinCommented:
Check for windows firewall on windows 2003 machine.

ALso,here ur main concern is telnet or allowing relaying for the entire network??
0
muzzi_inCommented:
Try this, it should resolve your issue, as far as relay is concern...

http://msexchangeteam.com/archive/2006/12/28/432013.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
muzzi_inCommented:
any update...
0
jonathanchapmanAuthor Commented:
Sorry for the delay, guys - doing some further testing.  It turns out this was not an Exchange 2007 problem at all  but rather the antivirus program that was running on the servers - it had a setting to block bulk email transmissions to prohibit worm activity; this setting was preventing the servers from transmitting legitimate mail to the receive connector on the Exchange server.  I'll accept multiple solutions here since your answers were correct (and both related to how this was solved) - thanks!!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.