The Name Could Not Be Resolved. Bookmark invalid?

I recently setup a fresh install of Exchange Server 2003 on a Windows Server 2003 system.

I presently have 1 domain controller, and 1 Exchange server.

All appears to work fine except when I attempt to configure an Outlook client to use an exhange server, I enter ther name of my Exchange Server, and a mailbox name.  I then get the following error...

The Name Could Not Be Resolved.  Bookmark invalid

I'm confused as to how to resolve this issue so that I can configure my user's Outlook client.
LVL 2
TheBrothaULuv2H8Asked:
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.

gpriceeeCommented:
Hi.  Try a couple of things:
1. Open a cmd prompt on the Outlook workstation and enter the following two commands:
      ipconfig /flushdns
      nbtstat -RR
2. Rather than use the NETBios name of the Exchange server, use the FQDN: don't use Exchange use Exchange.domain.local
3. Rather than use a name, try using the ip address.

One of the above should lead your workstation to Outlook.  After it does, then you can begin to resolve the naming issue.

SembeeCommented:
There are lots of causes of this error.

- Access to a global catalog domain controller
- Replication of data between the domain controllers
- Invalid address book data

The most common fix seems to be to reboot the GC DC. If you have recently changed a server and created a GC then you may need to reboot it again.

Make sure that the DNS settings are correct. The client machine should be pointing at the domain controllers ONLY for DNS. No external DNS servers should be involved.

Simon.

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
TheBrothaULuv2H8Author Commented:
gpricee:

Thank you for your suggestions, I applied them to no avail.  From what I'm reading the problem isn't a DNS issue but something going on with the global address book, however I tired your suggestion anyway.
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.

gpriceeeCommented:
How much time have you given the machines to find the Exchange server?
On the Domain Controller, open a cmd prompt and type netstat.  See if port 3268 shows (Global Catalog).
Also check to see if the lsass process is running.

Did you run forestprep and domainprep before installing the Exchange application?
NiclasHCommented:
Have you changed permissions on the address lists in ESM? Logon to a workstation with a domain admin account, configure Outlook for that account does it work?
TheBrothaULuv2H8Author Commented:
Thank you for all your assistance, rebooting the GC DC worked like a charm!  I feel somewhat stupid I didn't try that first!  Thank you Sembee and everyone else for all your assistance!
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
Exchange

From novice to tech pro — start learning today.