- How connect outlook to exchange server manual#
- How connect outlook to exchange server password#
- How connect outlook to exchange server Pc#
and ) for domain2 from both domain1's AD network, and domain2's AD network. Then ping the OWA URL and AutoDiscover URL (eg. Both should respond as the IP Address of the hosted provider and be the exact same from both AD Domains. and ) for domain1 from both domain1's AD network, and domain2's AD network. To make sure DNS is working properly, ping the OWA URL and AutoDiscover URL (eg. Don't dismiss this because you're trying to setup the profile manually.Īs DNS is a vital component in any network, please make sure that DNS is setup first before doing anything else. DNS is vital for Exchange Autodiscover configuration and making it work properly with Onsite or O365/hosted Exchange. You need to make sure your DNS is setup properly for BOTH domains. Now go to domain1's AD - ping that hostname that was in the "Use this URL to connect to my proxy server for Exchange" - does this resolve? does it point to the EXTERNAL hosted party's IP? If not - this is where your problem lies.
Take this hostname that is written in the "Use this URL to connect to my proxy server for Exchange" and ping this in domain2's AD - it should resolve to the EXTERNAL hosted party's IP. Open up More Settings, Connection, Exchange Proxy Settings, and look at THIS information.
How connect outlook to exchange server Pc#
On a working PC in Domain 2, in Outlook - 'Forget' about what you see written as the mail server - it means nothing in terms of the connecting. If not - do an nslookup on from domain1 AD - it may be a CNAME pointing to a hostname rather than an IP.Ĭonfirm that an O365 account can be setup in domain2's AD Domain - it should without issue.įor domain2 that you are importing into domain1. Ping from domain2 AD - it should resolve to the same IP.
How connect outlook to exchange server password#
How do you use outlook on O365? You open it up and type in your email address and password right? It then locates autodiscover and configures according to MS. It is only when I log on to the PC as a domain user that I can't get Outlook to connect successfully to the server in the other domain. I don't think it is a DNS issue because I cannot resolve the name of the server in the other domain even when logged on locally, however Outlook works and can connect to the server and open the user's mailbox. I don't understand why this doesn't work when I am manually setting up the profile. So I need a PC in one domain to be able to open e-mail in either domain in Outlook (using 2 different profiles) until we complete the migration into our domain. The reason I am trying to do this is that we will be moving the other domain into ours but we don't have sufficient staff to do this overnight. I have very limited access to the hosted server-I can only do what the hosting company allows in their web portal and have no powershell access. We use Office 365 here and the other domain uses a hosted Exchange server. There is not an Exchange server on premises here. I am putting in the same servername that autodiscover finds when setting it up as a local user.
How connect outlook to exchange server manual#
I don't understand why this doesn't work with manual setup for a domain user. If I log on to the PC with a local instead of domain account, it works fine with autodiscover. Outlook must be online or connected to complete this action." "The connection to Microsoft Exchange is unavailable.
When I log in to a PC on our domain here with a domain account and try to set up a profile in Outlook to connect to a hosted Exchange Server in another domain using manual settings, not autodiscover, I get this error when I try to check the name:
0 kommentar(er)
