The name could not be resolved. The name could not be matched to a name..."

I think I broke something ----

Have existing network Windows 2003 Server Domain.  Single DC, separate exchange server.

I was working in ADSIedit to repair a problem with a new email user added and not being able to create an outlook client connection withthe error - "The name could not be resolved. The name could not be matched to a name..."
Fixed several problems along the way with the RUS and DNS.

But now NO ONE can  resolve to the exchange server.  Existing outlook connections still work.

LDAP.exe cannot see the exchange server, just the DC.

I was workng in ADSIEdit with several purportedserach entries, not sure where now.

Any ideas?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

compdrAuthor Commented:
More info....
When adding new  Exchange Email accounts, they cannot be seen in the GAL.  They do have SMTP and X400 addresses assigned with the RUS.
I would revert what you changes in the RUS and DNS...
are  you getting any events in event viewer? if so what are theose errors
You will find the puporated search entries under All Address Lists in ADSIEDIT.
what were the changed you made there?
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

what happens with OWA? are you able to login?
also instead of Exchange server name, if you can type the IP of GCwhile doing a check name, does it resolves?
compdrAuthor Commented:
Don't really know what to change
RUS is working ok

What would cause LDAP to not connect to one of tje aervers?
compdrAuthor Commented:
IP does not resolve for exchange server

IP of the DC also the GC resolves so does the name which is FS2.  The exchange server 'FS3' does not resolve nor does its IP nor will it resolve with LDAP.exe

I made changes to the filter search strings there trying to fix this.  Actually i am not certain the condition was made worse by what i did.  Not sure if the resolution issues were global or not

compdrAuthor Commented:
OWA works fine with new email account
compdrAuthor Commented:

Using ADSIEdit,
      CN=Microsoft Exchange
            CN=Address Lists Container
              CN=All Global Address Lists
                 CN=Default Global Address List

The Default  LDAP search filter for the Default GAL as follows needed to be restored -

(& (mailnickname=*) (| (&(objectCategory=person)(objectClass=user)(!(homeMDB=*))(!(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=user)(|(homeMDB=*)(msExchHomeServerName=*)))(&(objectCategory=person)(objectClass=contact))(objectCategory=group)(objectCategory=publicFolder)(objectCategory=msExchDynamicDistributionList) ))

LDAP searches work now.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
compdrAuthor Commented:
See above solution
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.