Exchange 2010 smtp helo banner change

Good morning, I am crunched for time, so I am going to use your guys as a resource.

I have some diagnostic errors regarding my smtp helo banner not matching my RDNS.

when I telnet I get 220 ****************

I have the fqdn for the recieve and send connectors set correctly to,  but this is changing the smtp banner.  

this is a single server exchange environment.  I did try the set-Recieveconnector  "word"  -Banner,  but that did not seem to resolve anything

We are getting blacklisted, I assume tyhis is largelythe cause.

Any help would be appreciated.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Glen KnightCommented:
The SMTP banner will be on the server that receives the SMTP connection, if this a a 3rd party spam service or relay service then this won't be your server.

It could however be the default receive connector on the server that holds th einternet facing Hub Transport server, or an Edge Server, or even your firewall.
shareditAuthor Commented:
The server is my server.  we did install forefront, but I dont think we will use it, it has not been uninstalled yet, could that be the problem?

There is a default recive connector, but it is disabled.  I have another for annonymous email that is on port 25.  

The smtp banner does not match the default recieve connecter either.

220 *********** is what I am getting.
Glen KnightCommented:
Do you have a cisco device on your permitter? If so you need to check the SMTP fixup setting, make sure it's set to disabled.

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
shareditAuthor Commented:
Hey, that was exactly the problem.  I am working on another problem.  so I am on this remotely.  I was telneting directly to the local IP, but forgot to consider that that the firewall policys were still being applied to me through the tunnel. So I was under the impression the problem was still at ther server level.

thank you,

shareditAuthor Commented:
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

From novice to tech pro — start learning today.