Possible DNS error preventing Outlook connections to Exchange?
- From: "David" <abc@xxxxxxxxx>
- Date: Mon, 16 Apr 2007 13:53:33 +0100
I apologise for the length, but would appreciate help towards solving a
problem that I suspect may be a DNS error that is preventing client Outlook
connections to Exchange over the network. Client workstations can access
shares, database programs and the internet as normal.
On Saturday, I installed Service Pack 2 onto a SBS2k3-R2-Premium box and
installed all missing server patches listed by WSUS, Shavlik, and Microsoft
Update. After clearing up numerous Perflib errors, the server was restarted
with no errors being listed over the weekend. Monday morning, none of the
workstations could access Exchange Server using Outlook - messages that ES
could not be contacted. However, Exchange *is* running and can be accessed
via OWA both internally and (in my case) externally. Exchange is also
successfully sending me reports of service start/stops, etc., and forwarding
incoming mail out to my external address.
On the server there are no errors, but one curious information item upon a
restart of DNS:
Event Type: Information
Event Source: DNS
Event Category: None
Event ID: 113
Date: 16/04/2007
Time: 11:14:11
User: N/A
Computer: MERCURY
Description:
The DNS server could not signal the service "NAT". The error was 1168. There
may be interoperability problems between the DNS service and this service.
On all workstations, there is only one error that occurs at log-on and also
following a "GPUPDATE /FORCE" command:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 16/04/2007
Time: 11:20:02
User: NT AUTHORITY\SYSTEM
Computer: ET2600
Description:
Windows cannot determine the user or computer name. (The RPC server is
unavailable. ). Group Policy processing aborted.
To eliminate this, the server was restarted, and I have rerun the CE&IC
Wizard requesting it to modify everything except the SSL certificate. Same
problem.
From the workstation, using the Mail Applet (control panel) to either createor modify a profile, results in the error:
"The action cannot be completed. The connection to Microsoft Exchange is
unavailable. Outlook must be online or connected to complete this action."
In addition, within IE, the server cannot be contacted via:
http://mercury/
by *can* be contacted by:
http://mercury.mydomain.local/
http://192.168.15.2/
Yet you can ping the server "Mercury" successfully. By this, I'm assume
there is a DNS error somewhere. IE can access internet sites without
problem.
** Confession time **
When originally set up in February, I configured a second (split) DNS zone
to allow the same URL to be used for OWA and PDA access internally and
externally. 10-days ago after complaints that they couldn't access their
own externally hosted web-site (with the same domain name), I removed the
second zone entry. The client also said that they no longer sync PDAs, so
there seemed to be no point in the second DNS zone. After restarting DNS
there appeared to be no problems. No other changes have been made since
then.
.
- Follow-Ups:
- Re: Possible DNS error preventing Outlook connections to Exchange?
- From: Les Connor [SBS MVP]
- Re: Possible DNS error preventing Outlook connections to Exchange?
- Prev by Date: Re: Manual WSUS sync command
- Next by Date: New users don't have roaming profiles any more
- Previous by thread: Re: Fax Rendering
- Next by thread: Re: Possible DNS error preventing Outlook connections to Exchange?
- Index(es):
Relevant Pages
|
