We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

MDaemon: Error writing to winsock

lee_murphy
lee_murphy asked
on
Medium Priority
7,088 Views
Last Modified: 2007-12-19
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

Lee
Comment
Watch Question

Commented:
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 gmail-smtp-in.l.google.com or mx1.hotmail.com 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.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
Will have a look at that today, thanks tymes
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.