Question Locked

Connect Outlook 2007 to Exchange 2003 from Remote Location

0 helpful
24 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am trying to connect a netbook to my Exchange Server 2003 using an Outlook 2007 client on the netbook. The operating system for the server is SBS 2003, and that of the netbook is Windows 7 Starter.

When I open Outlook on the netbook, the dialog box saying that it is connecting to the server "mail.mycompany.com" and asking for the username and password continues to pop up without giving me an error until I just finally hit Cancel. Then it says: "The connection to Microsoft Exchange server is unavailable. Outlook must be online or connected to complete this action."

I can connect to this server from this same netbook when I am in the office, but not from a remote location. I can also connect using Outlook Web Access and via iPhone for the same user. Not sure if I am missing something on the client setup or if more configuration needs to go to my server.

I have been using the Outlook Anywhere setup without SSL, using the same server name as the OWA server with NTLM Authentication.

I would appreciate any help anyone can provide. Thanks in advance.

24 replies

by p.j.hutchison

Has RPC over HTTP been installed on the Exchange 2003 server to enable remote connection?

You need to specify additional settings in Email Accounts settings in Outlook in the More Settings, RPC over HTTP to be able to connect.

by zfreeman

I installed RPC over HTTP on the Exchange 2003 server by going into the Control Panel->Add/Remove Programs->Add/Remove Windows Components->Network Services and clicking on the RPC over HTTP Proxy.

In Outlook, when I put my server name into Outlook Anywhere, I did not check the use SSL box since I only use OWA with the http:// prefix. If I click to use SSL and input "msstd:mail.mycompany.com" in the option to connect proxy servers with this namein their certificate, I always get an error saying there is a problem with the security certificate. It does not come from a trusted CA.

by p.j.hutchison

You probably need to install the root CA certificate on your PC for it to be trusted.

1. Download the root.cer from your CA's webiste.
2. Open COntrol Panel, Internet Options
3. Click on Content then Certificates
4. Select Trusted Root Certificates
5. Select Import and import the root.cer you downloaded earlier.

by zfreeman

I exported the certificate to a .pfx file and sent it to the new computer and imported it. This still did not work.

by p.j.hutchison

You probably need Basic Authentication as well which allows authentication over the internet and via the Firewall.

by jlehman

Have you followed the instructions that are posted in Remote Web Workplace? I support 15 clients that use SBS 2003 and the instructions are listed just after logging into Remote Web Workplace. Follow those word for word and you should be set.

I saw you have tried certificates, etc. What operating system are you using? XP is by far the easiest to use to connect. Vista and Windows 7 require more work for the certificate. I have had to open a MMC console and move the certificates to the Trusted Root Certificates\Certificates folder.

Jeff

by zfreeman

I finally got into RWW, but I don't see any instructions. Maybe I'm missing something. I was actually having problems getting into RWW at first until I opened port 4125. Maybe that will help.

I am trying to connect two netbooks running Windows 7.

by cg it

the URL is https://public IP address/OWA or https://domain name/OWA

That's provided that during the CIECW wizard, you chose to allow OWA.

by cg it

OWA on SBS is https over 443 and IIS handles it. I suggest you change back the configuration you did in IIS to the default and use OWA on https. Run the CIECW wizard and publish OWA. That way IIS will be configured properly to handle OWA inbound requests and allow users to access their mail.

Many many IT people make the mistake of configuring SBS manually which often breaks SBS and breaks it in a non recoverable fashion. Because SBS has conbinded many features, like Exchange, SharePoint Services, Active Directory, with OWA/OMA and into an all in one box server, MS created wizards to configure all the services to run on one box. Again, manual configuration often breaks SBS features because the features are not designed to be configurated manually.

by zfreeman

I have updated a few registry keys to use the appropriate ports. I have also imported the certificate from the server to the client's Trusted Root CA directory. Now that I have done that, I get a different error on the certificate saying that the name on the security certificate is invalid or does not match the name of the target site. If I do not use SSL at all in Outlook Anywhere, Outlook just continues to ask for the user name and password without ever logging on or giving an error.

I did notice that the name on the server is the internal name, not the external FQDN. This suggests to me that I need to replace the certificate. I am reluctant to do this since I have other devices that have been configured with the current certificates in place.

by p.j.hutchison

You can have multiple certificates and apply different certificates to different services if you wish.

by zfreeman

I think I'll give that a try. Most of the other suggestions/ideas involved either a new certificate or a certificate with multiple domains. This might be a better option.

by jlehman

You do not need to replace the certificate. There is a setting for the internal name that you enter in the Exchange Proxy Settings. Just use Remote Web Workplace and follow the instructions posted on the right side in the Additional Links section. This is after you log into Remote Web Workplace but before you connect to anything. It will have all the information you need to connect Outlook.

by zfreeman

I only three things in the Additional Links section--Provide Remote Assistance, View Client Help, and Ask the Community. And I can't access the View Client Help Section.

by cg it

no matter what you do.

The only way to get rid of the cert error is to buy one from a trusted authority. Trusted authorities are outfits like Verisign, Thawe, etc.

The browser should allow you to ignor and continue. That's about all you can do with self signed certs or certs from untrusted authorites.

by zfreeman

I have been trying not to change too much as this server was set up by someone else. That person is no longer around, so I am learning things about their configuration as I go. I'm still trying to figure out why some of the things are set up the way they are.

by cg it

and changing it screws up IIS and also SharePoint.

The CIECW wizard is the connect to the Internet wizard found in the things to do list in the system management console [left pane at the top]. You run this wizard to publish features of SBS you want made public [public means public users can access the features].

OWA is in this wizard. Exchange is also configured using this wizard as well as the SharePoint internal web site and Remote Web Workplace. you simply check a box or fill in the blanks, the wizard does the rest.

This is how SBS is configured and manual configuration of components often breaks stuff.

To fix problems, you put the DVd/CD in and rerun the setup process. Setup will provide you with a wizard that you can choose 3 methods. uninstall, reinstall or maintenance. This is about the only way to "fix" some things in SBS and more often than not causes more hard than good. I don't recommend this route unless the componet simply will not work. If it works, even if it's not quite how you want it, but still works, don't do this.

If the previous guy simply changed the OWA port in IIS, change it back, Then run the Connect to the Internet wizard in the things to do list. but if he manually changed IIS around or added in sites the company wanted public access via https so he had to change OWA then you've got a bigger problem and might not be solvable.

by ccolding

From Outlook

Go to Tools - Account Settings - (Email Tab) Change - More Settings... - Connection Tab - Exchange Proxy Settings - Uncheck "Only connect to proxy servers that have this principal name in their certificate:"

Let me know how it works for you.

by zfreeman

It still gives me the certificate error saying that the name is invalid or does not match the name of the target site.

by jlehman

Since you only see a couple of links in the Additional Links section, it sounds like Outlook via the Internet is not enabled. You need to rerun the Configure E-Mail and Internet Connection wizard. You will need to select the Outlook via the Internet option to allow users to use Outlook Anywhere. This option is available in the firewall section of the wizard.

Once you have run the wizard, check Remote Web Workplace aain and verify you can see the option listed in the Additional Links section. You also need to ensure you have the proper ports open on your firewall. According to the help guide, it requires port 80 so that might be part of what is hindering your progress.

Jeff

by zfreeman

I reluctantly re-ran the wizard. There were multiple items that were not configured, including Outlook via the Internet. I already had ports 80 and 443 open. As soon I re-ran the wizard, the instructions in RWW came up. I had already re-issued myself a certificate with the proper name and installed it on the client. Everything was working within a matter of minutes.

This has been a thorn in my side for almost two weeks now. Thank you so much for that final nugget, and thanks to everyone else for their assistance.

by jlehman

I'm glad your problem has been resolved. Let me know if you ever need help with anything else.

Jeff

This discussion is closed to new replies.