Here is the fix:
It had nothing to do with certificates.
The last known working configuration, had a Firewall between the DSL Modem
and a SBS2003 Server providing DHCP, DNS, ActiveDirectory, Routing and
RemoteControl, and Exchange Services. The SBS2003 server had 2 nics, one to
the LAN, and one to the Firewall.
The new ISP's Modem is also a Router with Firewall and DHCP services. After
I told the laptop to "Obtain DNS Service Address" from new the Modem/Router,
Outlook could no longer route its Exchange Connection to the domain computer
because it could not find it.
The clues were in Event Viewer Application Logs:
"Automatic certificate enrollment for NETOPPS\bigdave failed to contact the
active directory (0x8007054b). The specified domain either does not exist or
could not be contacted."
"Windows cannot obtain the domain controller name for your computer network."
"Windows cannot determine the user or computer name. (The specified domain
either does not exist or could not be contacted. ). Group Policy processing
aborted."
As soon as I told the laptop to use the SBS2003 DNS Server for domain
resolution, instead of the new the Mode/Router's DNS Server, Outlook was able
to route its Exchange Connection to the domain computer because it could find
it. Outlook connected to the Exchange server and I was able to view my 463MB
of emails and contact info!
"boaldave" wrote:
> I changed the ip address of my Exchange Server to switch ISP's, not realizing
> that would have an impact on Outlook 2003 connections to Exchange Server.
>
> I remember using CA to create a Certificate a long time ago but I don't
> remember how I created it or where I put it. In any case, I have no idea why
> I need a certificate to connect and LAN Outlook client to a LAN Exchange
> Server in the first place.
>
> My first attempt at correcting the connection was to remove the Exchange
> account from Outlook and add it back, but now can't run Outlook at at. It
> tells me I must connect to Exchange at least once before I can view my
> Offline folders, then promptly shuts down, I assume because it is unable to
> make the connection.
>
> How can I eliminate this Exchange connection error? Is there a way to
> elimate this certificate dependency?
>
> Thanks,
> Dave
|
Similar Threads
