Re: OE 6& SP2 CORRECTION TO PREVIOUS

From: N. Miller (anonymous_at_discussions.microsoft.com)
Date: 08/27/04


Date: Thu, 26 Aug 2004 22:27:13 -0700

In article <10a301c48bd3$40b6d220$a301280a@phx.gbl>, Stephen Einson says...

> After upgrading to SP2 I can receive mail but I can't send
> mail using my MSN account. I can send and receive mail
> using my alternative ISP as a secondary ACCOUNT in OE 6

> The error message from the MSN account is:
> ==============================
> The connection to the server has failed. Account: 'MSN
> Sat', Server: 'smtp.email.msn.com', Protocol: SMTP, Port:
> 25, Secure(SSL): No, Socket Error: 10060, Error Number:
> 0x800CCC0E
> ====================
> I have eliminated my router, and now feed from the Lan Card
> directly into my DSL modem.

Put the connection back the way it was; the router is not the problem.

> I have turned off the Windows firewall and also have
> disabled Norton Anti Virus.

Re-enable the ICF. Man, do you like to live dangerously! No router, no
firewall; just a bare, unprotected Windows XP computer connected directly to
the Internet. It is a wonder that you aren't infected; especially with NAV
disabled! Yikes, man; you are a disaster looking for a place to happen!!!

> The strange thing is that Port 25 is used for both my MSN
> service and for my alternative ISP email functions.

Nothing strange about it. Even my server uses port 25. Port 25 is the
standard port for SMTP clients to connect when passing SMTP messages. If
there wasn't such a standardized port, there would be no easy way for any
one SMTP client to know how to connect with any SMTP server; not without a
lengthy port scan.

> Any suggestions.

I have already made some. My next suggestion is to do a thorough scan with
Norton, after reactivating it, and updating it. You only need to disable the
email scanning, not the whole shebang.

Now, look at this. I made this happen by suitable changes to my system:

==============================
The connection to the server has failed. Account: 'Sally
J', Server: 'mail.pacbell.net', Protocol: SMTP, Port:
25, Secure(SSL): No, Socket Error: 10060, Error Number:
0x800CCC0E
====================

The connection failed because I put a block on port 25 in my Netgear router;
no computer on my LAN would have been able to connect to an SMTP server off
site. Something between your gateway connection (the modem) and MSN is
blocking port 25 access; you can't get to the server, 'smtp.email.msn.com',
from the connection that you are trying it on.

My guess is, you tried to reach the MSN SMTP server while connected through
your alternate ISP; and they are blocking port 25 off of their network at
their border routers. You won't be able to use any SMTP server, other than
that of your alternate ISP, when you are so connected. It is an anti spam
measure.

It is unlikely that you can prevail on them to change their policy, but you
might try it. It is even less likely that MSN will implement a Mail
Submission Server; a special MTA which accepts authenticated connections
from Mail Submission Clients on TCP port 587; MSN is trying to move their
customer base away from SMTP mail to HTTPMail.

Now, put your rig back the way it was; and, in the future, ask your
question, and post your error message, ***BEFORE*** you make system changes
which reduce your security to zero.

-- 
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint


Relevant Pages

  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • RE: VBscript Error on SBS2k3
    ... DHCP Server turned of SonicWALL with VPN Pass through request for IP to ... the problem should be caused by the 4125 port. ... > | Accessories and Communications and Remote Desktop Connection? ... > | 2.In Internet Explorer on the workstation you are connecting from, ...
    (microsoft.public.windows.server.sbs)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Can not access Web and FTP sites from Internet
    ... your IP Configuration on the Server is correctly. ... Connecting To 12.208.215.87...Could not open connection to the host, ... 1> From the result, we can see the telnet failed, which means the router ... does not forward Port 443 to SBS Server. ...
    (microsoft.public.windows.server.sbs)