Exchange wont accept external email

is inbound SMTP opened on your firewall and pointing to your exchange server?

also make sure to disable any antivirus on your exchange box to test

The ISP also handles our firewall rules(this will be changed shortly).  I dont know why they would change the firewall rule in the middle of the night but I will ask them.  Everything worked fine yesterday evening.  Could this be something in the smtp settings in system manager?

mail.jrkellyco.com is the server if that helps.

Find out which port they are connecting to your exchange server on and make sure you have this forwarded from your router/firewall to the internal IP of your exchange server.

Also uninstall any virus/spam/firewall software you have on your server, restart and then try again.

1) telnet to mail.jrkellyco.com 25 from outside and you have a firewall picking up so far so good.
now back to my second post, disable/uninstall any antivirus you have

can you telnet the exchange box on port 25 intenrally ?

telnet InternalIPofexchnage 25

i have disabled Trend antivirus.
I CAN telnet the exchange box on port 25 internally

If mail.jrkellyco.com is you server then I don't believe it is a exchange server listening (at least it doesn't display a typical Exchange type banner, perhaps it is Trend as you say), it is more likely some other device that is intercepting port 25, it may then be configured to pass on to Exchange. It isn't accepting mail from my location, but then if it is configured securely it should only accept mail from your ISP so this may not be an issue.

Shaun

Whatever it is Trend or router, it is probably the cause, check IP restrictions etc or fully disable (may need to remove completely to remove SMTP event sinks).

Shaun

Disabling trend will not help it must be removed to eliminate it.

if you don't have access to your firewall rules then it is hard to troubleshoot further

If exchange is answering to telnet internally there is no reason why it shouldn't from external IPs

one more thing check the event log on your exchange anything relevant?

Its more likely that Exchange is cinfugured to listen only from the ISP?
Not unusual for a filtered service to be setup this way for security purposes.

I meant filtering service not ISP

They are both: "ISP host a barracuda server that filters all of our emails before we receive it"

Shaun

The Trend Server is also my Exchange server.  Should I uninstall the Trend client or the Trend Server or both?

Ahh well at least you all know what i meant :-)

I know what you meant, I wrote it in my comment earlier!

"It isn't accepting mail from my location, but then if it is configured securely it should only accept mail from your ISP so this may not be an issue"

Shaun

uninstall all of it, you can always install it again later

No need to uninstall a Trend Server and client just disable a services.msc and also disable from registry and reboot a server once and check it.

Disablng will not help!
It must be removed otherwise the hooks it has on the SMTP service will not be removed!

Most systems that scan SMTP work on a CLOSED DOOR system as in if they cannot scan it, it doesnt get in!

I do appear to have covered all this above:

"Whatever it is Trend or router, it is probably the cause, check IP restrictions etc or fully disable (may need to remove completely to remove SMTP event sinks).

Shaun"

Shaun

thanks for your efforts guys.  I am waiting on a call back from the ISP so I will wait until I speak with them before I continue troubleshooting.  THANKS!

Was just re-enforcing after the last post :-)

we are on the same page shaun :-)

i believe i also said this in my first post:

"Also uninstall any virus/spam/firewall software you have on your server, restart and then try again."

Un installation is not a good salutation I believe @demazter you know very well.

@Satyapathak > i have seen numerous issues with virus software causing mail flow problems.  The only way to resolve this is to uninstall it.  Have a look through the accepted answers on my profile and you will see numerous occasions when this has been the case.

Disabling anti-virus does not work.  Uninstalling is the only way.  Demazter is correct.

Here is my take on it:

Try disabling it first, using services.msc. If this resolves, you haven't had to uninstall it, and can now move forward and find out what in the software is causing the problem. No need to worry about any customisation / settings to be worried about.

If you see no improvement then you can't assume that the software was not the culprit, and indeed, sometimes you definitely do have to completely remove the software. However, I would suggest this points to some very poor programming from the developers, because you should never have to totally remove software to disable the functionality. The reason you do have to uninstall completely as demazter has said, is because it uses SMTP event sinks (actually injecting its own code into the SMTP engine) and to completely remove this, you uninstall the product.

Shaun

I am not deny you, but make sure this the basic troubleshooting part disable all virus service from services.msc after also disable from registy  msexchangesa virus key ,than reboot the server and check it.

This salutation is also not acceptable for enterprise label.

@Shaun you are 110% right..

"This salutation is also not acceptable for enterprise label."

i am not suggesting leave it off, its merely a troubleshooting step.

In my experience of working with exchange/windows/virus products quite often an Operating System Update, a Virus Software update or a combination of the 2 can cause Virus Software to stop playing well with Exchange.  This is common knowledge.  At the end of the day the priority is to get systems back up and running and then troubleshoot what happened.  More often than not uninstallung and then re-installing the latest version if the Virus software resolves the issue.

Users dont tend to care WHY something isnt working they just want it to work.  The IT people want to know why and tgat can be ascertained afterwards.

are there any settings in system manager that may cause such issues with external clients connecting to the exchange server?

Ok, I am there.

Under the Access tab I have the following ticked for authentication:

Anonymous access

For certificate, I have none.

For connection control, I have all allowed.