Link to home
Start Free TrialLog in
Avatar of runright
runrightFlag for Canada

asked on

Another 10061Connection refused error

We have just setup a new SBS 2011 running Exchange 2010.  We have set up all the users, mailboxes etc etc.  We are at the stage of bringing in emails.  We are using Smart Pop2Exchange 7.21.  Went we restart the server everything works fine for about 20 mintues then we get "SmartPOP2Exchange Enterprise Edition (7.2.1.477) 3/3/2011 3:12:07 PM   Error while opening SMTP connection to 'Server': Socket Error # 10061  Connection refused.  --> No connection could be made because the target machine actively refused it.  You tried to connect to the wrong server or the SMTP service isn't available on that server.Please check for a correct the SMTP host name and port (usually 25 or 587?) and make sure the SMTP service is available."  and it stays that way until we reboot.  We have started the Microsoft Information Store, restarted the SmartPop2Exchange.  Most messages appear to be firewall related, we have turned off the firewall(s) no change.  We have disabled the Microsoft Spam Filtering using "Set-ContentFilterConfig -Enabled $false" and "Set-ContentFilterConfig -InternalMailEnabled $false" and "Set-ContentFilterConfig -ExternalMailEnabled $false".  We have downloaded an applied all the Windows Updates .. any ideas what to try next?
Avatar of Alan Hardisty
Alan Hardisty
Flag of United Kingdom of Great Britain and Northern Ireland image

Why are you not using the built-in POP3 Collector?
Avatar of runright

ASKER

Bad experiences with SBS 2008, if emails did not come in perfectly it refused them and left them on the server until its mailbox filled up.
I'd ask the same question...

Here is the response from the Jam software Knowledge base...apparently happens enough that they had to put it in their knowledge base
http://www.jam-software.com/knowledgebase/smartpop2exchange/post_6300.shtml
I had read that, however I had not noticed the firewall exception...although right now the firewalls have been disabled and I have verified that the "SpamdServiceControl" is running.  I will do the re-install of SmartPop2Exchange just to cover all bases.
You shouldn't really be using a POP collector as it is only really designed for transitions - you should use Exchange for what it was designed for and have mail delivered to it.

Why are you using POP3 collection still?
I agree with you ... unfortunantly I cannot get all my clients to agree with us.  This client has an ISP that "does a wonderful job of filtering spam and viruses" and they do not want to change something that is already trained and works well ...
Sure - can't the ISP deliver the cleansed mail instead and you restrict the server to only receive mail from the ISP?

Most should be able to deliver the mail not sit on it and wait for it to be collected.

Do they have to setup mailboxes on the ISP's system and the SBS server?
It would likely be better if we could talk this company into a full domain name and setup but at this time they are happy with what they have and do not want to change anything more than is necessary.

Yes they set up two mailboxes, one at the ISP and one on the server, the company is small (less than 10 users), the staff has been very stable and so far this has not been an issue until SBS 2011.  
Sure - I appreciate the "if it isn't broken - don't fix it" mentality - but then that's also a recipe for stagnation too - it's a double-edged sword.

A bit risky of them not wanting to change anything more than necessary yet they are bleeding edge SBS 2011 adopters and only 10 users, so it's not as if they would have outgrown SBS 2008 / SBS 2003.

Not trying to be pedantic here - just seems a bit strange!
I find that it takes all kinds of people to make up this world we live on.  Some people will change only if it is forced on them ... even then they fight it tooth and nail until they go oh ... I'm glad I changed.  It is best to pick and choose your battles and the times for those battles, this one (using a 3rd party Pop collector) I thought was going to be an easy one ... turns out it is becoming a nightmare one to solve.  They upgraded the server only because the old one died and could not be resurrected.  
Sure - if the world was full of similar people - it would be very boring.

Some people a lot of coaxing to move in the right direction - others go willingly - that's part of the fun : )

It's a pain when some software that worked well before doesn't work quite so well now - I had fun when I upgraded to Exchange 2010 and discovered a known big that wasn't fixed by a certain company!  Caused me massive headaches for 5 months : (

I have always used POPCon - which I have found to be very simple, good and reliable.  Not suggesting you switch allegiances - but you might want to think about it if the software you are using isn't working properly.

http://www.servolutions.com/popcon.htm
ASKER CERTIFIED SOLUTION
Avatar of runright
runright
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Actually you do have the Edge Transport Exchange Role installed on your SBS Server.   SBS is different from standard products in that this would normally not be on domain controller and Exchange usually involves two servers
Cris - since when did SBS have the Edge Transport Role installed on it?
Not the solution I was expecting or looking for ... but it is still working, so who am I to complain....