• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 954
  • Last Modified:

Exchange 2010 over LAN : Can connect to OWA site but not via Outlook

Configuring my exchange server.
From PC A i can connect and login to the OWA on the new exchange server without any problems.

When i try to connect via outlook it cannot resolve the domain name/mailbox?

I can ping the exchange server via cmd from this PC, do i need to setup a DNS record to tell all PCs what IP the 'exchange server' is on rather than it just knowing?

Many thanks in advance..
0
MPJHorner
Asked:
MPJHorner
  • 6
  • 3
  • 2
  • +3
1 Solution
 
schima_czCommented:
When You are connecting, Do You use same name (exchange.domainname.local) or using IP adress? When You config Outlook profile, have You used name or IP?
0
 
MPJHornerAuthor Commented:
I have tried both, no luck with either.

I can however ping both?
0
 
Exchange_GeekCommented:
When you comment that you cannot "it cannot resolve the domain name/mailbox? '

So, does it work with email address login? How about you try working on other work stations - are all of them reporting same issue? Are multiple users reporting the same issue?

How about you configure your OL with webmail name? I am hoping that your OL has the name of your CAS Server and not DC/GC listed, can this be checked?

Regards,
Exchange_Geek
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
schima_czCommented:
Try to read this, may be helps  to You
http://blogs.technet.com/b/exchange/archive/2010/04/23/3409853.aspx

Open in new window

0
 
MPJHornerAuthor Commented:
Yeh, my exchange server is called 'exchange' i also tried exchange.mydomain.local..

Here is a screenshot of the error

Screenshot of the error!
0
 
James HIT DirectorCommented:
Verify that all exchange services are running.
Any errors found in the event logs?
Restart the Exchange Address Book service and try again.
0
 
MPJHornerAuthor Commented:
hmm the address book service wont start..

its a clean installtoo?
0
 
MPJHornerAuthor Commented:
edit : That is now started. Still get the same error.
0
 
Exchange_GeekCommented:
You're OL isn't able to resolve your Exchange server name, if it could the moment you clicked on Check Name, Exchange would resolve to Exchange.yourdomain.com.

Perform a simple test, ping the server with its netbios name and find results.

Ping exchange

Do you see the response as exchange.yourdomain.com with server IP address?

Regards,
Exchange_Geek
0
 
MPJHornerAuthor Commented:
it state replying from exchange it doesnt include the domain name at the end on its reply.

just states pinging exchange [192.168.16.21] ....

but does reply?
this mean netbios not working?
0
 
AmitIT ArchitectCommented:
Run nslookup on exchange server and post the result here.
0
 
ExchangePanditCommented:
Try putting your Domain Controller/Global Catalog server instead of your Exchange Server name in the "Microsoft Exchange Server" field and please let me know the result.

Regards
0
 
Exchange_GeekCommented:
this means that your machine has a local host entry which has the server name registered in it. Look into local host entry and verify Exchange is not part of it.

Also, perform nslookup and check what is the response for Exchange.

Regards,
Exchange_Geek
0
 
James HIT DirectorCommented:
Just out of curiosity, what is your CAS set to?

In the EMS, just type:

get-clientaccessarray
0
 
MPJHornerAuthor Commented:
Turned out to be a DNS issue afterall, nslookup explained this to me - thanks very much!
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 6
  • 3
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now