No connection to Exchange server - but OWA works
Mr. Bunny
We're running Exchange 2003 on SBS 2003 Premium, with a mix of Outlook
2003 and 2007 clients. This is only my 3rd week of working with this
peticular network, so I don't know the entire setup 100%, or the ratio
of 2003 and 2007 clients. All clients are on Windows XP Pro (except
for 1 XP Home, and 1 Vista Home Premium).
Problem is as follows: Existing users have no problem connecting to
the Exchange server using Outlook. New users, myself included, that
have been added to the server recently (after atleast 3 months of no
new users) are completely unable to connect to the exchange server
using Outlook.
Entering the Exchange server information identical to working clients,
it gives the "The name cannot be resolved. The connection to Microsoft
Exchange is unavailable. Outlook must be online or connected to
complete this action."
This message pops up immediately when clicking the Check name or Next
buttons, without any attempt being made to reach the server whatsoever
(no traceable network traffic generated from the email setup
application). I've tried just about every combination possible of the
connection settings, and every setup method from multiple books and
online resources, Nothing makes any difference whatsoever.
This appears to be a per-user problem. Multiple users on the same
machine, only users added recently cannot establish the connection to
exchange, "old" users have no problems. All users in question have
administrator rights. These users include 1 Outlook 2007, and 2
Outlook 2003.
We have a total of 10 possible simultaneous users in the network (only
10 machines with Outlook or any office products installed), and are
licensed for 20 on the SBS. Total configured users is 14, of these 3
don't work.
What's interesting is that the same users that cannot connect over a
hardline to Exchange, can connect just fine through OWA, and OWA is
generally many times faster than the users that use Outlook for
Exchange. OWA only works in-house, our network security settings do
not allow out-of-house connections to the server.
I've been through every setting I can find on the server, and cannot
find anything different about the Exchange settings for the non-
working users, compared to the working ones. We have over 100 GB free
on the storage drives (and mail folder max is 170 MB), so it's not a
matter of having space for the mail folders.
Totally lost here, any remote hint of a suggestion would be greatly
appreciated.
regards,
Rene
Jeff
Outlook worked fine. If I tried to setup a new computer and Outlook would not
work. It kept giving me an error message saying the Exchange server was not
available.
Try this - In outlook instead of putting in your Exchange server name, put
in the server name of your Domain Controller! See if it resolves the name!
If it works, you have a DNS problem!
Mr. Bunny
Well, the problem is that this is a SBS Server, and this is really a
small business. The SBS is everything - file server, Exchange server,
domain server, AD server. We can use any share on the server just
fine, so we know the connection is there, it's just the Exchange part
that's causing us grief.
We are running McAfee Total Security suite atm, and all prior users
were configured before it was installed, so I'm not sure if that's an
issue or not. While being on the server at the same time as a client
connects, we're getting no popups at either end.
Webs
recommend this link:
http://msexchangeteam.com/archive/2007/07/18/446400.aspx
Webs
recommend this link:
http://msexchangeteam.com/archive/2007/07/18/446400.aspx
On Dec 14 2007, 8:41 pm, "Mr. Bunny" <mbunny...@gmail.com> wrote:
Webs
recommend this link:
http://msexchangeteam.com/archive/2007/07/18/446400.aspx
On Dec 14 2007, 8:41 pm, "Mr. Bunny" <mbunny...@gmail.com> wrote: