Re: SMTP Error # 0x800ccc60


"JaR" <jrderby@xxxxxxxxxxx> wrote in message
news:uGlbiaBaIHA.208@xxxxxxxxxxxxxxxxxxxxxxx

I don't know. All the other clients are sending email fine with
Outlook set to port 25 for SMTP. I just re-tried on this machine,
which uses the same settings for e-mail, is set to use port 25
outbound, is able to email out just fine, and yet when I try to
telnet the server(GoDaddy) on port 25, , the result is "connect
failed". Our firewall is not blocking telnet, as I can reach my
home server from here.


That is weird. I don't mean to insult your intelligence but you
entered the command like the following:

telnet your-smtp-server-name 25

didn't you? Just want to make sure. Also try telnetting to the IP
address of your SMTP server on port 25.

The reason I posted in here is because I thought it possible that
others had seen the same problem and found a solution that worked
for Outlook.

There are no other problems with the two boxes other than SMTP out.

Someone mentions uninstalling AV product on the 2 problem PCs and
test it without AV installed. Worth a shot.

Good luck.

Well, things just get wierder. Also I learned something new about our
firewall. I figured the firewall wasn't blocking outbound telnet,
because I could get into my home server on port 23 and our POP server
on 110, but the SMTP server returned "fail to connect" on 25. I tried
to connect from a box outside our company net and connected just fine
to the SMTP server on 25. Now I need to figure out how the heck the
firewall blocks telnet on port 25 but allows SMTP outbound on the same
port.

But that's another story, possibly for another group.

I uninstalled McAfee on the two boxes in question, and the one with the
socket error now connects and sends e-mail normally. Thank you K.Orland!

The other box is still unable to connect to the server and is still
returning 0x800ccc60 error.

Thanks to all for their suggestions. Any more ideras on the remaining
box would be most welcome!

--
JR
Remove hat to reply
.

Relevant Pages

  • Exchange issues
    ... IP address that the MX record points, port forwarding is configured to route ... all traffic on port 25 to the SBS Exhange server. ... I suspected SMTP relaying becuase ... All the Exchange services are running and all looks fine. ...
    (microsoft.public.exchange2000.admin)
  • Re: Mail sent through IIS virtual SMTP server not arriving
    ... Juan T. Llibre, asp.net MVP ... In the Default SMTP Virtual Server's properties, in the "Access" tab, both ... a real sender address on the SMTP virtual server? ... Youi'll find sample code for changing the port number under system.web.amil here: ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: SMTPS - Exchange
    ... the newsgroups are staffed weekdays by Microsoft Support professionals to ... If the Exchange server is listening on other port rather than ... the external email server will not send emails to your SMTP ...
    (microsoft.public.windows.server.sbs)
  • Re: IIS and SBS 2003
    ... I have a new sbs2003 install and if I telnet to localhost ... port 80, and type hhh and hit enter it returns a HTTP/1.1 400 Bad ... "broken" sbs server, it connects but then dumps me. ... If I http to localhost, companyweb or anything I get Cannot Find ...
    (microsoft.public.windows.server.sbs)
  • Re: Suggestion for a lexical (login mode via TCPIP)
    ... Not sure of it is the right one to modify or to add another one, but it would be useful to be able to get information on whether the user us coming in via FTP, TELNET, etc. ... This would also allow a LOGIN.COM to check if someone is coming in through a secure/SSL port for instance. ... For the HP SSH server, it seems to be undefined. ... forget about the possibility of virtual terminals. ...
    (comp.os.vms)