There is this, but i doubt this is the solution..
Error Message: Outlook Is Unable to Connect to Your Outgoing (SMTP) E-mail Server
http://support.microsoft.com/default.aspx?scid=kb;en-us;302357


Check this out also:

"I may have seen this several times.

My solution was to check the settings and have it checked off that the server requires authentication.

outlook - Tools>services>internet mail
Properties button
Servers tab and check My server requires authentication."

I have previousally scoured EE, MSDN/MSKB, and the web via Google, for a solution to this problem and have not found one.  The articles mentioned above (Microsoft, EE, and EE) I have already read and none of which have helped.  The configuration is identical between the machines and the two computers which are acting up worked previousally - the problem was spontaneous, it seems.

The overriding problem here is that all outgoing communications over port 25 are denied on these two workstations.  I already knew this was the reason for the error - I need to know how to fix it.

Also, the SMTP server we use here /requires/ authentication to work.  It does not use POP-before-SMTP authentication, it uses a username/password combo.  Also, it's a slightly grander problem then just Outlook - I am unable to even telnet to any server on port 25, my testbed, the Windows 2003 SBS, and both the "real" name of the SMTP server and the "virutal" name of the SMTP server (one being mail.ourdomain.com and the other being host.hostingcompany.com).

Any other ideas?

if this happend for no reason then maybe u should look for addware or spyware programs running on those two computers?
also try changing one of the nic cards(i doubt two nics will fail the same time)it wont hurt.

Ran a complete virus scan over the affected computers and discovered nothing - the user who was logged in when this started lacks permission to install /anything/ on the computer, and as the physical location of these computers is a 40 minute drive to another city... replacing NICs would be difficult.  I'll try re-installing the NIC drivers, but I fear an OS re-install may be nessicary... arg.

Hmmm, Is the XP firewall enabled? Probably not that, but if it is, try disabling it. Usually, the xp firewall doesnt block outbound connection tho..

I'd be impressed if the Windows 2000 machines had Windows XP firewalls. ;-)

But just in case, I made sure the thing most resembling a firewall (IP deny rules inside the connection settings) was disabled.

topfloor i know u have AV but since two machines went bad the same time it may be
something they downloaded so if u can download a free anti spyware and run it.also make sure users have not downloaded popup blockers(they cause what u describe).

No spyware, no popup blockers.  Checked both, and no user can install such software - only Administrators can install anything.  Thank you for the suggestions, but I still need a solution to this ASAP - users getting frustrated.

I'll try killing off random processes - we'll see how well that works. ;-)

All workstations are at one site, all sharing the same ISP.  I have already attempted the easy solutions (delete and recreate profile in Outlook, re-install Outlook, etc.) to no avail.  Re-installing the system worked much better, however, the problem still remains a mystery.

    Like Dissenter mention on his comment, PORT 25 is blocked by most ISP today to control SPAM, but if you have and ISP BUSINESS account (Business DSL for exemple) Port 25 should not be blocked most ISPs only block port 25 for Residential accounts. the main thing is the ISPs wont support this, I have worked for many of them that's how I know.

     If you have a business account you need to have an MX Record created with your ISP to better accept your profile. Also if your ISP require authentication look up with them if you need to have the full email address under the Logon Information box i.e. johndoe@myisp.net insteady of just johndoe. I tried to insert a picture for you to see what I mean, but I could not insert it here.  By the way if anyone know how I can attached a snpshot to this box as an exemple let me know please.

     Hope you get it fixed, I know how bad is when you want and need something done and start getting error messages.

 
 
   

disregard my lest comment...you have other machines that was working fine.  some how you some profile issue on those 2 machines it's clear if you have 5 PCs 3 works fine and 2 dont the problem is configuration that got damage on the affected PCs.

I have called 3 Cable companies. It took them a while to Divulge the info. But they all said the exact same thing. That port 25 has been blocked, and you MUST use their outgoing SMTP server... I.E.

I use COX.NET with my YAHOO.COM Email so my settings look like this...
POP3= pop.mail.yahoo.com
SMTP= SMTP.COX.NET

This fixed the problem. They assured me that E-mail is still private, but the companies simply don't want others accessing that port. An annoyance really only if your ISP does not provide POP3 Mail... I hope this helps some of you.

Lomius Maximus

Despite the fact that in most cases, your comments would solve the problem, reading my previous comments reveals that port 25 is only firewalled on the machine itself, not outside the building.  Two machines cease to create connections on port 25, thus causing the problem.  There are three other machines which continue to work fine, and, once the system was re-installed, both of the computers began functioning properly again.

Thanks to everyone who posted constructive comments.

After much arduous researching this exact problem with my computer using Outlook 2003 on an Earthlink account accessed through a cox cable network, I found that by changing my outgoing port to 443 from 25 totally solved the problem...

Good luck to all

I recently came across the same problem and tracked the issue to Norton Anti Virus 2003. Outlook 2003 was functioning properly until the user downloaded a new virus definition file. Disabling Norton completely did not solve the problem, but disabling the email scanning properties for both incoming and outgoing emails solved the problem.

I hope this suggestion will benefit someone else who may encounter this problem.

gamblerc

We had the same problem.  It turns out to be an issue with Windows Firewall Settings (we think).  Logged in as local Admin and switched off the firewall and shutdown all services to Symantec AV, then tried to telnet to port 25 on the mail server, and it worked (previously had failed).  Switched Firewall back on and restarted Anti Virus and tried again, and all Okay.  Rebooted machine and logged in as restricted access user and tried to telnet to port 25 again, which worked with no problems.

I had a very similar issue with a windows xp sp2 machine running Mcafee Virusscan 8. Hidden in the Virusscan Console was a service called Access Protection which had 6 port blocking rules applied.  One of these was to prevent mass mailing of worms on port 25.

From your description above you never mentioned disabling antivirus, did you try that?  Once I unticked the rule, my telnet on port 25 returned.
I have searhced I high and low for a solution to this problem and it was driving me mad!!!!!

I had the same problem.  Most large ISPs no longer let you telnet to port 25, so it looks like the port is filtered/blocked.  It wasn't filtered at the gateway because other systems were using the same connection.  I killed AV, I killed the local firewall.  Still couldn't connect.  I tried deleting and recreating the profile, no luch.  The symtoms i experienced appear as though there is an issue making a connection.

However, try this.  Create a new pst, tell outlook to deliver to that new pst.   And then try to do a Send receive.  If this works,  Do a file export of the pst with data to a new pst and set that new one as the pst to deliver mail to.  Check to makes sure you can send/receive and life should be good.  Using scanpst.exe (Inbox Repair Tool) does not fix the problem.  I spent the last 6 hours chasing a ghost because it looks like a connection problem, so if you are still having problems give this a try, it may work for you.

Hi everybody. I've got not solution but I think I understood the cause. This happens when you change the account name in your outlook 2003 account list. For example, if you have:

john@example.com

and then rename this account into:

Account of john@example.com

You got the problem. I don't know where but I think that's a reference bug because Outlook it's trying to refer to account "john@example.com" but now there is just "Account of john@example.com".

Comments are accepted and precious

Have a nice day
Adriano

Look here:
http://www.salocin.com/weblog/archives/000309.html

Now It works again, maybe is really all related to Transparent Proxying (I'm hating it..). I think my SMTP server has just a delay and in this interval locks you when you try to connect. Now it's all OK.

Perhaps you should call your ISP asking about their Transparent Proxying polices.

Have a nice day
Adriano




the article body
___________________________________________________________
0x80042109 SMTP server problem

I post fixes to computer problems I have that takes me ages to fix, in the hope that someone else might be able to find the solution and so save themselves the pain. In this case, I couldn't send outgoing email via my SMTP server on port 25 despite the fact that I could receive email fine. It all came down to transparent proxying, but it took a while to find out. If this helps you, please drop a note to let me know, otherwise I feel like I'm writing for the web-bots.

Basically, when I tried to do a send/receive with Outlook, everything went well until it tried to send my outgoing messages, at which point it would hang for a while, and after the pause, I'd get error number 0x80042109, with some problem connecting to my SMTP server. But this would happen only through some connections and not through others.

Microsoft's online help service, which is frankly usually quite good, was completely useless in this case. It has some blurb about MSN messages that doesn't really help at all.

What it turned out to be is that my ISP is using something called "Transparent Proxying", which they didn't bother to tell us they were doing. It's part of a spam-prevention toolkit that prevents anyone who subscribes to this ISP from connecting to any machine's port 25 other than the ISP's own SMTP server. Annoying? Oh yes. Especially since it took me 2 days to work out what the damn problem was.

In my case, my email provider has a workaround. They've set up another port on which the SMTP server will respond, and their authentication system requires that I log into the POP3 server before the SMTP server will acknowledge my existence. This conveniently bypasses the port 25 block my ISP has set up. That's all this problem really was - my ISP was blocking connections to port 25 on any machine other than their own SMTP server.

If you're struggling with something similar, try TELNET to any SMTP server you can find outside of your own ISP's address range (port 25) - if it doesn't work there, but it works on your ISP's SMTP server, then this is your problem - scream at your ISP, and much good may it do you.

I had the same experience w/ Outlook 2003.  I noticed that I was able to successfully connect and send/recieve email after I created my first account.  Then I tried to create a second account (and I changed the .pst file location at the same time.  Immediately afterwards, I started receiveing the username/password error.  
 
After a bit of time, I was able to get Outlook working by using the login info for the second account created, but only that account.  I cannot add another account r everything stops working).  Deleting accounts and recreating them does not work either.    I can however, always seem to get things working in the second account.
 
Unfortunately, the account that works is not the preferred account.  Right now, Outlook2003 is unusable to me, so if anyone has any suggestions, I would certianly appreciate hearing some.  
 
Many thanks.

Okay, I have found a solution that fixes this problem.  
 
Delete any Outlook profiles you have created (not email accounts, but Outlook profiles), and re-create them.  Once you do this, you can re-create your email accounts, and everything (so far) seems to work as intended
(even no problem adding multiple email accounts to the same profile works).  

Good day and good luck.
gmctech

"I have called 3 Cable companies. It took them a while to Divulge the info. But they all said the exact same thing. That port 25 has been blocked, and you MUST use their outgoing SMTP server... I.E.

I use COX.NET with my YAHOO.COM Email so my settings look like this...
POP3= pop.mail.yahoo.com
SMTP= SMTP.COX.NET

This fixed the problem. They assured me that E-mail is still private, but the companies simply don't want others accessing that port. An annoyance really only if your ISP does not provide POP3 Mail... I hope this helps some of you.

Lomius Maximus"

This fixed my issue for me. Since I was using a different ISP, but trying to connect to an smtp server of a different ISP, I used my current smtp server and I'm able to send e-mail.  Thanks Lomius!