We help IT Professionals succeed at work.

No connection could be made because the target machine actively refused it - Exchange 2010, sonicwall, Barracuda 300

Suddenly external email to our company stopped reaching our building, while internal email continues to function.

We have a Sonicwall which directs the email to a Barracuda Spam filter, which sends it to our Exchange 2010 Server. There is no mail reaching the Barracuda. The NAT policy in the Sonicwall to send the mail to the Barracuda appears to be intact and nothing there has been changed. I have restarted both the Sonicwall and the Barracuda.

I went to mxtoolbox.com  and did an MX lookup for one of our domains. It looks correct. Then I did a DNS lookup which looks okay too. When I did an SMTP test, it says "No connection could be made because the target machine actively refused it (my public ip address):25"

I am not sure what to do at this point, any help is appreciated - thank you.
Comment
Watch Question

CERTIFIED EXPERT

Commented:
Does your SonicWall require a annual subscription? Just a thought

Author

Commented:
Yes, actually it looks like our Software and Firmware updates and Hardware warranty expired on Jan 9, 2012. The purchase of a new appliance has been tied up in corporate and delayed, this one is outdated (Pro 3060). Would the expired Software and Firmware updates cause this? Should there be a warning or notification somewhere? Thanks

Author

Commented:
Also - if this helps, Internet and other services (Terminal Services) are working okay..
CERTIFIED EXPERT

Commented:
I'm not sure about SonicWall, but this does happen on other routers.
You may have had 1 month to update before it switches off.

Mark
Syed_M_UsmanSystem Administrator
CERTIFIED EXPERT
Top Expert 2011

Commented:
Dear,

i would like to know how many WAN connections you have? +
if you telnet your publicip on port 25 what is the responce from outside? +
what logs tells about outoing email, are emails set in quee if yes ... you will see an ip assonicated with the email ... can you confirm this is your public ip for emails?
Commented:
It turns out that it was the Barracuda Spam Appliance, the MTA Service had stopped and my restart did not correct that because apparently when I restart my Barracuda it does not actually restart, due to a firmware bug. Their tech started the service and the mail started flowing. Worked for an hour, broken again - at any rate the issue is with the Barracuda Spam filter. Thanks to all who replied for trying!

Author

Commented:
The issue is with the Barracuda Spam filter, being fixed by their techs.