If the Internet Connection Wizard opens, skip ahead to step four. To configure Outlook to connect to your account, please do the following: If you have an email account set up on the server, you may want to configure Outlook or Outlook Express to send/receive email from this email address. com addresses remain their defaults).īut I would rather understand exactly why the system thinks it needs to reach outside the LAN for information and why it infers it needs to look at BlueHost.Search Bluehost Web Hosting Help Email Application Setup - Outlook Express Maybe I can just change the default back and ensure that users' profiles are not set to automatically This is just the first time I changed the default (in #2 above). Oddly enough also, we were already using multiple domain names (.com). First Organization -> Recipients -> Recipient Policies -> Default Policy -> Properties: added rule for type SMTP, address and set it as default. First Organization -> Connectors -> Small Business SMTP connector -> Properties -> Address Space: added address space type SMTP, address. In the System Manager, I believe the only two things I had to change to do this were these:ġ. This problem will all disappear in a few weeks when we migrate to Office 365 with hosted MS Exchange, but in the meantime, it is making me look like an idiot (or, I fear, revealing that I am one) because Outlook 2010 never gave us any auto-discovery indicationsĪt all before we added. Of course, they are, but only as the hosting Why Outlook thinks it needs to do any auto-discovery, especially that which points to BlueHost, when there is no information anywhere I can see on the Exchange server that BlueHost is even involved in any of this. It just falls into auto-discovery mode when attempting to access other user's mailboxes. When a user logs onto aĬomputer & opens Outlook for the first time, we just enter the NetBIOS name of the server in the profile dialog.Īs noted, connecting to other mailboxes works perfectly in Outlook 2003, and Outlook 2010 connects to the logged-on user's mailbox just fine. All computers are members of the domain and on the LAN with the server. Exchange is configured to handle e-mail for address spaces. Internal (SBS 2003 server with Exchange 2003) MX records point to McAfee Saas, which pre-filters e-mail and then forwards DNS records for and both point to my firewall at the office. So it is not something stuck from a previous profile.Īll computers are members of the domain and are in the LAN with the server, so I still cannot figure out why Outlook is even trying to reach out to the internet domain when the entire connection is between the workstation and the server on the same LAN.Įxternal (on our internet domain at Bluehost):ĭomains. One of my tests earlier today was to log onto one of the office computers as a user that had no previous local Outlook profile on that computer, open Outlook for the user, configure the profile, then try to connect to another mailbox to which the user has I did get your other post by e-mail, even though it never showed up here. In fact, I have never configured anything related to auto-discover, since this is an Exchange 2003 server. None of the auto-discovery registry entries refers to BlueHost, and there is no auto-discover record on my local DNS server. The problem does not occur on our last remaining Outlook 2003 computer. It is not rights-related it is Outlook 2010-related (but the Outlook forum folks told me to bring my question here). Never allow the user to open the other user's mailbox. However, when I grant one user rights to another user's mailbox (on the server) and then attempt to open the mailbox (Account Settings -> More Settings -> Advanced -> Add), the same message pops up and will That, of course,ĭoes no good because BlueHost is nothing more than our domain hosting service, and where we have MX records redirecting mail to our in-house Exchange server.
Clicking OK just adds the BlueHost address to the list of redirect servers in HKCU\oftware\Microsoft\Office\14.0\Outlook\AutoDiscover\RedirectServers. The user checks the box to quit notifying, then clicks Cancel, and things just repeat. This is soon to become Office 365 with MS hosted Exchange, but we are not quite there yet and need help with this issue in the meantime.Īfter changing the default e-mail domain from one domain to another (e-mail for both domains is hosted on this Exchange 2003 server), already-working Outlook 2010 Exchange clients are now popping up this message at startup and periodically during the day:Īllow this website to configure server settings?. Outlook 2010 with Exchange 2003 as part of 2003 SBS.
0 kommentar(er)
