"Mikey" <> wrote in message
news:6c85d0d0-d1ac-418f-a375-...
> On Jan 5, 11:27 am, "Brian Cryer" <not.h...@localhost.invalid> wrote:
> > "Mikey" <texan...@hotmail.com> wrote in message
> >
> > news:57b64e48-b79d-4f57-bee4-...
> >
> > > I'm running SBS 2008 & have one user that works from home, using
> > > windows mail.
> > > He can recieve emails, but not send.
> > > I'm getting the message:
> > > Socket error : 10061, Error number 0x800CCC0E
> > > The ports are open on my firewall - what could be the problem?
> >
> > Has the user been able to send emails via your server previously, or is
> > this
> > the first time they've tried?
> >
> > I'd start by looking at whether from the user's pc they can connect to
> > port
> > 25 (SMTP) on your server. If they can then I'd guess its down to
> > authentication issues - although the resolution will depend on whether
> > or
> > not they've ever been able to send emails.
> >
> > To confirm that he/she can connect to port 25 on your server open a
> > command
> > prompt window on his/her pc (so client's end not at your end) and then
> > type:
> > telnet sever-dns-name 25
> > replacing "server-dns-name" with the correct dns name of your server. If
> > they get a line which identifies your mail server then they can connect
> > to
> > that port. If it instead indicates that it couldn't connect then the
> > problem
> > is firewall related - but could still be at the user's end.
> >
> > I know this is only a start and not the solution, but I hope it helps.
> > --
> > Brian Cryer
> > http://www.cryer.co.uk/brian
>
> I tried that & got the following response;
>
> 220 remote.mydomain.com Microsoft ESMTP MAIL Service ready at Thu, 6
> Jan 2011 10:56:02 -0600
>
> The name of my server isn't 'remote', but that's one of the cnames (I
> believe) that it uses for remote workplace, etc.
> Even if I changed server name to remote, I am still repeatedly asked
> for name & password...
That's good. It shows that the port is open and that there is a connection
from the user's pc through to your server. So it doesn't sound like its a
firewall issue. That said, it is worth reviewing the firewall configuration
on the user's pc just to make sure that windows mail isn't being blocked my
the local firewall - some firewalls allow blocking by application name. I
think its unlikley but worth checking.
The only other thing I can think of is to check that its trying to connect
to the right IP address. So double check the SMTP server that the user is
using. Also its worth checking via DNS too, so (again on the client):
nslookup dns-name
and check that the IP address which comes back is correct. I can reproduce
the error you are seeing but only if I using a DNS name which can't be
evaluated or if there is nothing listening at the IP address it evaluates
to.
Thinking about it, the IP address or DNS name should be visible in the FULL
error. You've only supplied some of it in your original email.
So, firewall config and double check the dns name are all I can think of at
this point.
--
Brian Cryer
http://www.cryer.co.uk/brian
Similar Threads
Linear Mode
