Outlook 2003 fails to connect to pop server after re-log on


Outlook 2003 & WinXPSP2, NIS 2005. This problem has arisen recently.

When loggin in after boot/restart, there is no problem, Outlook works fine.
However, If I log off and log on again, or if a different user logs on,
Outlook can't reach the incoming mail server and produces a connection error.
Upon restarting the computer and logging on, there is no problem. But if
then a different user wants to get mail, a reboot is required in order for
that user to be able to reach his incoming mail server. This problem is with
POP servers only, IMAP work just fine. Any suggestions?


Sponsored Links:



After reading quite a few posts on this forum with regards to the issue of connecting Outlook 2003 client to the Exchange 2003 server, I thought it worth providing you with as much detail as I have on the issue I have experienced. It appears remarkably similar to the others - though none of them have been answered, so maybe one of the Exchange Guru's on this site can help us mere mortals figure out this issue.

1) I have installed a fresh copy of Windows 2000 advanced server and updated with all the latest patches / SP's etc. And installed a fresh copy of Exchange 2003 as the first Exchage 2003 server in the domain (I previously had 2000 and then moved to 2003, though after a bit of a disaster with some security software with Exch2003 and SP1, I had to remove all traces (all - including Active Directory and Registry) )
2) After adding SP1 to the install I configured a basic setup for the single server and enabled SMTP for a single domain. Then started all the services (and ensured the event log did not report any issues), including POP3, HTTP(OWA), SMTP, IMAP.
3) I have tested POP3, HTTP(OWA),SMTP, IMAP all succesfully - using Outlook as the client and IE6 browser for OWA
4) I can connect to the server for remote admin, and ping etc as you would expect. The DNS resolution is fine for FQDN, Hostname and IP Address via rDNS.
5) What I cannot do is access Exchange directly via the Outlook client using (I believe) MAPI. Which does not have a specific setting in the Exchange Manager to configure (that I'm aware of)
6) I tried to set up a new profile in Outlook by selecting Exchange Server as the type and then entering the server name (also tried the IP address here, and FQDN) and the username of a mailbox that works via OWA.
7) I get the following error message: "The Action could not be completed. The operation failed". Then when it automatically opens the popup window to confirm the details, it gives me this error: "The Name could not be resolved. The operation Failed".
8) Out of curiosity I deselected the "Use Cached Exchange Mode" to see if this was used during Setup or not. It is (in exactly what capacity I'm not sure). I then got a new message before the one above is shown, this stated: "Outlook could not logon. Check to make sure you are connected to the network and are using the proper server and mailbox name. The operation could not be performed because the connection to the server is offline"
9) I have checked the Event Log for any related errors on both the server and the client machine - I couldn't find any. I also temporarily disabled any firewalls, just in case.
It seems very much that the Outlook client just cannot access the Exchange Service (MAPI I assume). Which would indicate (as many other access methods work ok) that the server is not listening correctly for these requests. Or if the client is trying to get information from Active Directory then maybe it hasn't found what it needs ? Either way, I have ensured that all the services with Exchange are running without errors, still without joy.
Please can someone either:
1) let us know what this problem is, and how to resolve it, or if this is not possible..
2) tell us how the process works - i.e. what ports/protocols are used in this initial connection/query to the server and what services should be running to facilitate it.

I hope that one of the experts here can shed some light on this fairly common issue, which to date doesn't seem to have been given an answer.

Thanks in advance.
Damian




I have some Outlook 2003 clients that are getting prompted for authentication
when they start Outlook. As it turns out they are being prompted to connect
to a server that they should not be connecting to. If you look at connection
status, it says that Outlook is trying to connect to the server for Public
Folders. It already has a legit public folder connection.

This happens even if you erase the profile and create it new. The users are
actually from a trust domain.

I know I have seen this before, but can't seem to come up with the answer.
So where and how does Outlook decide what servers to connect to? And how do
I make this connection attempt go away,

Thanks,

Paul




I have been using Outlook 2003 for over two years with very little trouble.
That changed last Thursday (June 28th) when it stopped sending my work
e-mails. Now all I is the following message...
Task 'Crown - Sending' reported error (0x80042109) : 'Outlook is unable to
connect to your outgoing (SMTP) e-mail server. If you continue to receive
this message, contact your server administrator or Internet service provider
(ISP).'

My outgoing mail server (SMTP) is as follows...Smtp.email.msn.com. MSN is my
ISP but I have been unable to reach anyone to learn if their server address
has changed. Can anyone help me?




Bit of a long post, but as you'll see, I've tried to check out as much as I
could before posting!

I’ve just completed setup of a SBS2003 R2 server and I’m having a big
problem with getting Outlook 2003 clients to connect to the Exchange server
in its native (RPC) mode.

Outlook web access is fine for all users, the users can map drives to the
server, etc – no problems. The client PCs are one which is a member of the
domain and authenticates against the SBS server and one which is configured
in a workgroup so only connects to pick up email. I checked IMAP access to
the mailboxes also works fine, except I don’t like Outlook’s handling of IMAP
so I’d rather use a proper Exchange server setup.

I tell Outlook to add a new account, MS Exchange Server. Enter the server
name and the user name and click Next. Outlook then complains “The action
could not be completed. The connection to the Microsoft Exchange server is
unavailable. Outlook must be online or connected to complete this action” and
won’t go any further.

I’ve tried the short name server, the FQDN server.domain.local and even
the internet equivalent www.server.net, all with the same result. The
setting of “Use Cached Exchange mode” also makes no difference.

I thought this might be an authentication issue, so I tried setting “Always
prompt for user name and password” under More Settings/Security. That lets me
create the email account and demands a login when I start Outlook, but then
comes up with “Outlook could not log on…. The connection to the server… etc
etc”

Trying to set Outlook up for RPC over HTTP also doesn’t get me far. So, I’m
guessing it’s something about the server’s security or RPC, but 4 hours of
digging around on the web later and I’m none the wiser. Especially as I would
expect a default Exchange server config to talk to Outlook.

I’ve tried deleting the Outlook profile and even setting up a fresh user ID
on the client PC to test from. Same results each time.

If I have “Always prompt for user/password” ticked, then running Outlook
/rpcdiag initially shows two lines – Directory (no server name)/connecting
and Referral (SBS server name)/Connecting. If that’s not set, it clears the
diag list too fast for me to see anything at all! Anyone know whether the
diags are captured in a file someplace?

For reference, both machines are on the same internal subnet and in the
interests of ensuring no interference, the client PCs have their firewalls
disabled (“allow all traffic”) temporarily. The server isn’t running Windows
firewall anyway (single network machine, not in the DMZ). Clients can all
get to the server by hostname for web and other access, so the DNS appears to
be working (DNS is managed by the network router, not the Windows server).

Help!

Any guidance on this much appreciated!




Hi,

I have a client who uses exchange and asked about a bizzare behaviour they
have been experiencing. Apparently every (approximate) two days when they
come into the office their outlook will fail to connect to exchange. What
they have been doing to fix this is to Reboot exchange. For some reason this
is working.

What I am hoping to find is a "fix" that doens't require a reboot. :)

There seems to be an error in the event log indicating that the exchange
database is larger than it is allowed to be. Could this cause the experience
they are seeing?

Any clues would be appreciated.

I am a dba/developer so Exchange is a bit of a mystery to me.

Thanks in advance

Rob




Hi,

I have a client who uses exchange and asked about a bizzare behaviour they
have been experiencing. Apparently every (approximate) two days when they
come into the office their outlook will fail to connect to exchange. What
they have been doing to fix this is to Reboot exchange. For some reason this
is working.

What I am hoping to find is a "fix" that doens't require a reboot.

There seems to be an error in the event log indicating that the exchange
database is larger than it is allowed to be. Could this cause the experience
they are seeing?

Any clues would be appreciated.

I am a dba/developer so Exchange is a bit of a mystery to me.

Thanks in advance

Rob




I will be co-existing Exchange 2003 and Exchange 2007 with Outlook 2003 and have a couple questions.

When I do move-mailbox, I understand that if Outlook 2003 tries to connect to the Exchange 2003 box, it is notified to go to Exchange 2007. I am assuming a company-wide e-mail should be sent out ensuring that users attempt to connect to this mailbox during a certain time-frame while Exchange 2003 is up.

If Exchange 2003 is brought down, I'm assuming those user's will have to manualy re-configure their profile?




Outlook 2003 unable to delete message headers, cannot find message on
server, delete only strikes through the message header




How can I download all my @sbcglobal.net emails into Outlook 2007 Ultimate?  I am switching from DSL to cable and will lose my email account.   Microsoft Office Outlook Connector fails to sign into the @sbcglobal.net acct, managed by Yahoo.




My mail server is very flaky. When Outlook 2003 tries to connect to the
server it often results in a timeout or some other error which causes the
connection to fail.

This causes Outlook to give me a prompt asking me to enter my username &
password. They are already entered in the fields and they are correct, all I
have to do is hit OK and Outlook will try to reconnect to the mail server and
download new messages.

The problem is that if I'm not at my computer the error window doesn't go
away and Outlook won't try to reconnect on its own. Outlook will remain in
this state for days if I don't click OK. This is a major problem because I
get all my email on my cellphone which wirelessly syncs with Outlook. If
Outlook chokes I don't get any email until I'm back in the office to click
'OK' and that can be several days. BIG PROBLEM!

I just upgraded from Outlook 2000 and this was NOT a problem with OL2000.
With OL2000 if a connection failed I didn't even get an error message, it
would just try again at the next regularly-scheduled interval. This is what I
want OL2003 to do!

How do I get OL2003 to operate this way? When a connection with the mail
server fails I just want OL to try again on its own without any input from
me. PLEASE HELP!

NOTE: This is not the usual problem people have when they get the
username/password error message. My username & password are correct and they
ARE saved in OL. Please don't go down this route in advising me.




Since about the first week in December 2006 I'm getting an error
message synchronizing folders between Outlook 2003 and Hotmail Plus.

The error message is "Outlook's request to the server failed" This
error is intermittent, but always occurs the first time Outlook is
loaded after the computer is turned on. Eventually, folders do
synchronize and I get my mail. The problem also occurs after several
hours of inactivity, e.g., not using Outlook or having it loaded but
minimized on the task bar.

A test using Outlook Express with the same Hotmail account does not
produce this error message showing that the problem is limited to
Outlook 2003 on the desktop. All the mail comes down to the desktop
using Outlook Express from Hotmail on the web without any error
messages.

The Hotmail Plus account is current. I don't find anything directly
relevant in the Microsoft KB. This installation of Outlook is not
connected to an Exchange Server. I don't get this error at work where
I am connected to an Exchange Server, but I do from time-to-time lose
my ability to access my Hotmail account with Outlook 2003.

Any ideas?

System info

Pentium 2.4 Ghz, 1 Gb memory, 80 Gb HD
Windows XP SP2
Symantec Personal Firewall 2006, Anti-virus 2005
Outlook 2003 SP2
Internet Explorer 7.0573




I have been using Outlook 2003 with gmail successfully for almost 3
years. Last Friday, at about 4pm I started getting this message:
Task 'pop.gmail.com - Receiving' reported error (0x80042108) :
'Outlook is unable to connect to your incoming (POP3) e-mail server.
If you continue to receive this message, contact your server
administrator or Internet service provider (ISP).'

I've made no changes to my settings, and double and triple checked my
account settings in Outlook. Pop is enabled in gmail. I went
through
the common errors list and then the troubleshooting guide on the
gmail
help site. I followed the instructions to do a telnet check which
also failed Then I received this message:

The error you're experiencing indicates that your network is blocking
access to Gmail's POP servers. Please contact your local network
administrator or your Internet Service Provider's customer support
department for further instructions.

I then contacted my ISP who said they are not blocking access so they
believe the problem is with Google. I work at a hotel and my ISP
keeps all ports open because of the high amount of users we have on
the wireless network. I've run out of things to do.

Why would it suddenly just stop working after all this time?
Can anyone recommend something to me?

Thank you.




After upgrading from Outlook XP to Outlook 2003 it fails to perform
advanced searches by right clicking shortcuts pointing to containers
from inside mailboxes other than the default Exchange mailbox. If you
do the same operation by first opening the shortcut and then selecting
the advanced search option, then Outlook performs the task as expected.
In case that you try to reproduce the sequence described above by
selecting an item from the folder list instead of the shortcut, then we
have no problems.

The computers we used in these testing are XP Professional with Office
2003 connected to a SBS 2000 server. It's important to mention that we
have this problem ever since we started using office 2003 and even
though we stay pretty current on all Windows updates, the problem
remains.

This Outllok 2003 behaviour is diferent to all previous versions; It
seems that Outlook only logs into Exchange Server when an specific
mailbox is manually requested by the user. If that is so, it is failing
to perform the log by first selecting advanced search before actually
opening the container.

Any help would be greatly appreciated.




I have been using Outlook 2003 with gmail successfully for almost 3
years. Last Friday, at about 4pm I started getting this message:
Task 'pop.gmail.com - Receiving' reported error (0x80042108) :
'Outlook is unable to connect to your incoming (POP3) e-mail server.
If you continue to receive this message, contact your server
administrator or Internet service provider (ISP).'

I've made no changes to my settings, and double and triple checked my
account settings in Outlook. Pop is enabled in gmail. I went
through
the common errors list and then the troubleshooting guide on the
gmail
help site. I followed the instructions to do a telnet check which
also failed Then I received this message:

The error you're experiencing indicates that your network is blocking
access to Gmail's POP servers. Please contact your local network
administrator or your Internet Service Provider's customer support
department for further instructions.

I then contacted my ISP who said they are not blocking access so they
believe the problem is with Google. I work at a hotel and my ISP
keeps all ports open because of the high amount of users we have on
the wireless network. I've run out of things to do.

Why would it suddenly just stop working after all this time?
Can anyone recommend something to me?

Thank you.




OK, here is the issue..

OWA 5.5 works great for users that use Outlook 2000 (or Lower version), but
the uses that are using Outlook 2003, they are getting the "failed to
connect to the microsoft exchange server" error when attempting to access
the mail via the OWA page.. I've searched and searched for this one.. any
answers.. and no, upgrading the server to 2000 or 2003 isn't a option right
now.

Thanks for your Help

--
Paul




possibly an exchange 2003 setup error leads to this bizarre scenario:
setup the standard ms exchange mail client on apple i-pad, connection via wifi and VPN.
all ok. mail client configs correctly, verifies account from exchange server and sync normally.
I need to change the default primary smtp mail address belonging to my exchange mail enabled account. I therefore replace the primary smtp with another address using a different mail domain suffix. i then remove the resulting "secondary" smtp mail address since is now obsolete for my purpose. the mail client on i-pad stops working as it fails to connect to the exchange server.

how to understand this "error" ?
considering that OWA access is seamlessly accepting such changes
as well as any outlook client ?
any help much appreciated




Hi All,

I've read every possible forum post, tutorial, and technet article in the past week and still cannot get Outlook Anywhere working correctly when using outlook 2003 clients connecting to my Exchange 2007 server.

My setup:
Exchange 2007 with all typical roles installed on one machine, with an external IP address, and DNS entry on that IP address to mail.company.com (Server 2003 R2 SP2 x64). NO Edge Server, NO ISA server. No firewall or anything in place, all ports are open to the exchange box. The internal name of the machine is exchange1.domain.local
There is a GC also in the domain, called directory.domain.local

I have exchange sending and receiving email, and OWA works fine. I got a certificate from startcom.org, and installed it per all of the tutorials available. Activesync also works fine with my windows mobile 6 device.

If I launch outlook 2003 on a machine outside of the network, setup the exchange profile from scratch, and configure the exchange proxy settings, it will connect via HTTPS to the mail server, but fails to connect to the directory server (keeps on trying to connect to directory.domain.local). So people can send/receive mail, but not use any of their contacts.

After bringing the machine inside the network, the only way to get it to connect via HTTPS when it's brought outside the network again is to remove the exchange profile and then re-add it.

Is anyone else having this problem?




We have a client who is having a very odd behavior. The environment is
Exchange 2007 with Outlook 2003 SP2 clients running MAPI native connections
to the server. When the client receives an email that was forwarded from an
external user it fails to display the attached message. Let me try to be
very clear about exactly what is happening here.

External user 1 (EU1 as it happens an AOL account) sends a message to
external user 2 (EU2). EU2 in turn forwards the message to our internal user
(IU). When IU gets the message in Outlook 2003 she can see the subject and
an AOL tag line but it does not show any attachment in the displayed header
or inline.

If IU opens the message in OWA there is an attachment that is the forwarded
message and this opens fine.

If IU opens the message in Outlook 2007 the attachment shows up as expected.

The same behavior occurs with a newly created Outlook 2003 profile on the
original workstation as well as on a second workstation running Outlook 2003.

If IU forwards the received message to any user internal or external the
received message contains the attachment as expected.

Now here is a really weird one - If IU forwards the message to herself the
attachment is displayed correctly!

I have been trying to figure out if there is something weird with attachment
blocking or TNEF at the server level but I have not come up with anything. I
don't believe that there is any strange GPO doing anything here. I tried
setting the messages to be viewed in the internet security zone, set down to
medium with no change. I'm stumped. Any ideas??




After upgrading from Outlook XP to Outlook 2003 it fails to perform
advanced searches by right clicking shortcuts pointing to containers
from inside mailboxes other than the default Exchange mailbox. This
behaviour cannot be reproduced if you first select and open an item
directly from the folder list or through its shortcuts.

It seems that Outlook only sign on in Exchange Server if we actually
select and open an specific mailbox. This sign on process used to be
automatically done in all mailboxes by the time we opened the previous
versions of Outlook.

Any help would be greatly appreciated.

CZorzella