Re: Cannot connect to Exchange outside of Local Domain after GPO c

Tech-Archive recommends: Fix windows errors by optimizing your registry

The University Domain was never trusted by our Domain, but, being able to
connect to their Exchange server from OutLook on one of our computers always
worked until lately.

I am the person that handles GPO's, locally, and, am part of a group in
several Domains that's responsible for trying to standardize them, and, so AM
one of the ones troubleshooting this (there is no "THEY"...I is part of
"THEY"...<G>). We don't see something that would obviously stop this.

I assumed that someone in this Forum would have had a similar experience.
It's not simple connectivity, as, we can both PING and resolve their server,
and, even adding their Domain into our network settings doesn't help matters.

It looks as though OutLook cannot even SEE their Domain or Exchange server,
for some reason.

Thanks.

"Lanwench [MVP - Exchange]" wrote:

Bill Bradley <BillBradley@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
We're a hospital with our own Domain and Exchange 2003 SP2 server.
Many of our doctors are from a University across the street, with its
own Domain and Exchange 2003 SP2 server.

Until a few weeks ago, they could (on our computers, joined to our
Domain) just setup a seconday OutLook (2003 SP3) profile, put in the
U's Exchange servername, and, their U Domain Logon account name, and,
use it, while logged-on to our computers with our Domain's logon name
for them (they'd just have to logon to OutLook using the U's
Domain\UserName). It all worked fine, they opened up OutLook, chose
the correct profile, then either directly when to our Exchange, or,
logged-on to the U's Exchang.

About two weeks ago, our hospital was pushed some GPO's from higher
up in our Forest, in an effort to "be standardized", and...at that
time, the U doctors started to no longer be able to connect.

You should probably talk to the people who did this to find out what has
changed. Were they aware that you had a trust with another domain?

Network connectivity is NOT affected, it's something stopping them
from seeing the other Domain (they can't see the U Domain, and, check
name fails). Computers NOT on any Domain (in a workgroup) still work
as before, so, I presume it was something in one of the GPO's.

Not necessarily.

I've
gone through them, but...nothing pokes out.

Any ideas what could be stopping this from working as before?

Thanks!!

It's hard to say. This isn't going to be an Exchange issue. I'd try posting
in microsoft.public.windows.server.active_directory (after checking with the
people who made the changes).



.

Relevant Pages

  • Re: Problem with multiple access to one exchange email account
    ... The emails are hosted on the SBS exchange server using SMTP protocal. ... The users' Outlook accounts are connected by selecting exchange server ...
    (microsoft.public.windows.server.sbs)
  • Re: Problem with multiple access to one exchange email account
    ... The emails are hosted on the SBS exchange server using SMTP protocal. ... The users' Outlook accounts are connected by selecting exchange server ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange connectivity issue question
    ... "Log stalls are a common cause of Outlook access issues. ... Nuevo, by separate spindles, do you mean a new RAID controller with new ... “connecting to exchange server” style pop up and the end users having to wait ... while the outlook clients try and talk to our Exchange server, ...
    (microsoft.public.exchange.admin)
  • RE: Created a new mailbox but cant access it via Outlook or OWA
    ... The permissions on the exchange server may be modified. ... Mailboxes to Your Outlook Profile ... 40037315-Created a new mailbox but can't access it via Outlook or OWA. ...
    (microsoft.public.windows.server.sbs)
  • Re: Outlook 2003, Pop, Exchange Server
    ... Windows XP users using Outlook 2003 can connect directly to the MailStreet ... connecting to an Exchange 2003 server via HTTPs gives you ... delivery location to a personal folder file, ... > with the exchange server, can I just add the exchange server to the ...
    (microsoft.public.outlook.general)