Getting weird warning in App log with Forefront on MB server

I have used Forefront on Exchange many times in the past on Exchange 2007 and 2010. I am getting this warning relating to smtp in the App log.

Event ID 2064 - Unexpected SMTP server response. Expected: 220, actual: 500, whole response: 500 5.3.3 Unrecognized command

I found the article below which addresses this supposedly. I was a little concerned about creating another Receive Connector in Exchange just for Forefront. I never had to do this in the past. Yes, our default RC does have anonymous enabled. I need it this way to accept inbound emails just like the article states. Was wondering if anyone else ran into this problem and found another way to resolve it? It appears to be an issue with Forefront on the MB server trying to send notifications using the CAS. I am not getting any email alerts from the MB servers regarding scanning, updates etc.....

http://johanveldhuis.nl/en/forefront-protection-for-exchange-2010-unexpected-smtp-server-response-expected-220-actual-500-whole-response-500-5-3-3-unrecognized-command/
shadowtuckAsked:
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.

unknown_routineCommented:
Receive connector on Hub Transport server must have Exchange Servers option in Authentication and Permissions tabs.

Is this the case for your situation?
0
shadowtuckAuthor Commented:
Yes and those are the default settings. The only thing different about this RC from the default is anonymous is checked but that is needed to receive inbound emails from our gateway. The article mentions this and states that Forefront is sending anonymous TLS and that is why it's failing. The solution is to create another RC without anonymous being checked. This has to be something different with Forefront because I never had to do this in the past. If this is a common issue, I don't understand why MS doesn't have a tech article on it.
0
shadowtuckAuthor Commented:
I guess what my concern here is creating another Receive Connector. I want to make sure I don't interrupt the flow of email. I am not changing any settings on the two Receive Connectors I have now. I am just adding a third Connector for Forefront. Is there any particular type I should be using Choices are Internet, Internal, Custom etc....I am guessing if I don't specify a type, it should default to what I currently have.
0
shadowtuckAuthor Commented:
I did some test in a test environment using the PS command in the link I posted. There was no issues at all after creating an additional Receive Connector using this command and the only difference between the one I created and the Default RC in Exchange is that Anonymous is not checked. All the other settings are the same.
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
shadowtuckAuthor Commented:
I solved my own issue using testing.
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
Microsoft Forefront ISA Server

From novice to tech pro — start learning today.