Koozali.org: home of the SME Server

outlook error 0x800CCC0F outside nat

javabytes

outlook error 0x800CCC0F outside nat
« on: March 06, 2006, 10:10:30 PM »
we upgraded our sme 6.0 to 7.0

the mail server is inside our nat and outside access is portforwarded

subsequent to the install outlook clients within the nat recieve mail but outside the nat outlook error 0x800CCC0F is reported

webmail, www and other services on this machine work fine,

any ideas?

Offline dsemuk

  • *****
  • 269
  • +0/-0
outlook error 0x800CCC0F outside nat
« Reply #1 on: March 06, 2006, 10:21:54 PM »
http://support.microsoft.com/default.aspx?scid=kb;en-us;813514#kb2

Says the Outlook/Outlook Express error code you give is due to communications errors.

Are you sure you have all the ports are forwarded correctly?  Have you checked to make sure after the upgrade?  Did you have any additional contribs installed on SME6 which may have not upgraded properly?

Are you saying before the upgrade everything was working but after it was broken?

Dave
--
Esmith/Mitel/SME server  :-D...

javabytes

everything worked before
« Reply #2 on: March 06, 2006, 10:27:55 PM »
yes, this matter arose after the upgrade..

methinks it is a port forwarding issue as well, are there other ports other than 110 that are required in v7?

thanks

brent

Offline JonB

  • *
  • 351
  • +0/-0
outlook error 0x800CCC0F outside nat
« Reply #3 on: March 07, 2006, 10:15:08 AM »
Check your email settings in the server-manager. You will find that POP3 is set for POP3S i.e secure POP3 and SMTP is set for SSMTP i.e secure SMTP.

Secure POP3 uses port 995 and secure SMTP uses port 465.

These are the default settings of SME7.

If you want to enable public POP3 access and are aware of the risks i.e username and password are transmitted across the internet in plain text then from the console


Code: [Select]
/sbin/e-smith/db configuration setprop pop3 access public
/sbin/e-smith/signal-event email-update


Jon
...

Offline domainwizard

  • **
  • 34
  • +0/-0
    • http://www.domainwizards.net
that worked!
« Reply #4 on: March 07, 2006, 05:48:17 PM »
thanks so much, methunk it was a port issue....

 :lol: I need 2 get out more  :hammer: