MDaemon: Error writing to winsock

Hi all,

I'm having a problem with my MDaemon Server (v8.1.5 - latest available).  Whever a connection is tried via SMTP it reports back:

Mon 2006-03-20 13:03:27: Session 11; child 1; thread 260
Mon 2006-03-20 13:03:27: Accepting SMTP connection from [x.x.x.x : 53358]
Mon 2006-03-20 13:03:27: Error writing to socket
Mon 2006-03-20 13:03:27: Winsock Error 10054 Connection was reset by the other side!
Mon 2006-03-20 13:03:27: SMTP session terminated (Bytes in/out: 0/0)
Mon 2006-03-20 13:03:27: ----------

And that's all.  Any suggestions as to what could be causing this?  It's installed onto a Windows NT server.  Which leaves me with another option.  I've installed it on my Windows 2005 server and instructed the route to route all SMTP requests to the new server and that just blocks it completly, no message at all in MDaemon.  I assume this is something Windows 2003 is doing to block the port, but I've disabled the Firewall on that server to be sure, but no change.  Would love to get one running.

Many thanks

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.

Go locally on the machine and telnet localhost 25 or telnet ip 25 and see if it connects, also see if you get the proper helo string.  It may be that the service can't start because you have microsoft's SMTP also installed -- the helo string will tell you.

You should also try telneting out to or port 25 to ensure you're not blocked by a firewall on the way out...

So start on the machine (rule out a firewall), then go one step out to another computer behind the network firewall on the same subnet (rule out the "route" you setup), then try it from the internet.  You'll find the problem that way.  

Most likely it would be either a competing SMTP service or the firewall.

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
lee_murphyAuthor Commented:
Will have a look at that today, thanks tymes
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
Email Software

From novice to tech pro — start learning today.