Link to home
Start Free TrialLog in
Avatar of EICT
EICTFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Problem adding Exchange account to Outlook on non-domain laptop

Hi,
I have a laptop which is connected to our company wireless network. Unlike the other laptops it is not a member of the AD domain.
When I try to create an exchange account in outlook 2007 and enter the Exchange Server name or IP Address I get an error "The connection to Microsoft Exchange is unavailable" and the username check fails.

The strange thing is that if I enter the IP address of the DNS server, not the Mail Server, the username check works and the username and mail server names are underlines. It replaced the DNS server IP with the mail server name.
but I still can't access the exchange server.

I have checked DNS and the DNS setting on the laptop and they appear ok.

This problem has only occurred since we moved from Exchange 2003 SBS to 2013.  Its like an old exchange record is in DNS or Active directory??
Avatar of Scott C
Scott C
Flag of United States of America image

That's because you need to be using autodiscover to connect to Exchange.  With Exchange 2013 it's not possible to enter the Exchange servername or IP address.

The way to manually configure the profile is to enter the name of your DC and it should resolve and work.

But it looks like something is still wrong with your AutoD.

Go to this page and do the "Outlook Autodiscover" test.

https://testconnectivity.microsoft.com/

Look at the results and see where to go from there.
Avatar of EICT

ASKER

thanks.
The person has gone for the day with their laptop so I will try this tomorrow.
Thanks for your help. I'll respond then.
Avatar of EICT

ASKER

Sorry it's been a while since looking at this.
There is definitely a problem with the Autodiscovery service .

On Testing TCP port 443 on host domain.org to ensure its listening and open
The specified port is either blocked, not listening or not producing the expected response.

How do I configure https://domain.org:443/Autodiscover/Autodiscover.xml
Do I need to add a record in  the internal and external DNS for this  (i.e. autodiscovery.domain.org) and what does it point to? Where is the XML file held?

Thanks
ASKER CERTIFIED SOLUTION
Avatar of Kash
Kash
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of EICT

ASKER

This did the trick. I also had to sort out certificate errors by manually adding the route CA into my trusted CAs.
Autodiscover still does not work but this gets around the problem. Thank you