The same message appears when I try any other name or IP address that points to this same local server including localhost and the server's name and the server's IP address in 192.168.0.0/24. This happens regardless of whether I use the Exchange server's name ("exchange") or its (fixed) IP address or "localhost" or 127.0.0.1.Īfter that error message, this small window appears with a slightly different error message.įor some reason Outlook cannot "resolve" the name 127.0.0.1. Online or connected to complete this action. The connection to Microsoft Exchange is unavailable. Now the network adapter has a default gateway and Outlook continues to pretend that it cannot find the Exchange server. When running Exchange 2013, on manually creating an Outlook profile, you discover things have changed. We clicked a little button that resolved these details and went ahead to open Outlook and access our mailbox. The Outlook installation is just for testing mailboxes. Once upon a time we created Outlook profiles by simply filling a server name and a mailbox user name. Outlook first refused to connect because the network adapter didn't have a default gateway and apparently Outlook requires a default gateway to connect to 127.0.0.1. I have an Exchange Server 2013 and I am trying to connect using Outlook 2010. The Outlook installation is just for testing mailboxes. I have an Exchange Server 2013 and I am trying to connect using Outlook 2010.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |