Outlook Anywhere

U

/usr/home

Supreme [H]ardness
Joined
Mar 18, 2008
Messages
6,160
After reading this thread (http://hardforum.com/showthread.php?t=1569628&highlight=outlook) I hadn't heard of OA before and it's exactly the sort of thing that I was looking at for a client of ours. They want Exchange over multiple remote branches without doing VPN and this looks perfect. Before I try this with them, I figured I would do it on my own server.

New install of Server 2008 R2 Standard.
New intall of Exchange 2010 Standard.

OWA and connecting to Exchange with Outlook internally works great. It can receive and send mail. Everything is working as it should be. OWA works as well. All the proper ports are forwarded; 25, 80, 443, 143, and 110. (I forwarded them all just because. I'll take out 110 and 143 once I get it working all right.)

Now my server has a name of server.domain.local. domain.ca points to my webserver on another IP, but mail.domain.ca points to my home IP on which this server sits on. I hope I haven't lost anyone yet.

I have not played around with many of the settings in Exchange, and for the most part. everything is set to the basic defaults.

I go to setup OA in the Outlook client and for the Exchange server I enter in "server.domain.local" and in the username I type in the username "Test" (That's the user I'm testing with). In the connections under proxy I use "mail.domain.com" and use NTLM for authentication. This setup is not working though. I have played with all the settings in the connections tab to get it to work, but still can't. Am I missing something or doing something wrong here? Maybe DNS problems on the Exchange servers end? This server is connected straight to my firewall (Mikrotik RB450G) so there's no ISA or anything. Any insights?
 
Trying to sort through your situation. Are you trying to hit mail.domain.com from an internal system? Is your net behind a NAT firewall?
 
The Exchange server is the Local name of the server, the Proxy is the Internet facing URL. If you are trying to use the Internet facing URL while you are inside the network, you'll need a DNS entry to point to the internal server. Also, did you set up Autodiscover?
How do you have your Cert setup?
 
I'm assuming you are referring to SSL cert? If that's the case. I don't have one. Do I need one? No I haven't setup Autodiscover. I'll look into that now.
 
when you installed exchange did you choose to enter in the external URL you would be using?

you onhly need to put in the domain, so to log in for example it would be Server\User unless you disable the need to enter in the domain.

Exchange over multiple remote branches
Click to expand...

you dont need a vpn, just use pop3/smtp or imap access then.

Honestly if your setting up exchange for clients, you need to learn alot more about it before you go offering it as a service for a company.

trainsignal exchange video's are phenominal


you'll need a DNS entry to point to the internal server
Click to expand...

I use my external URL inside the same network for our office accounts and it works fine, no DNS records on our network pointing internally, sure it is better, why go out to the net and back if you dont need to, but it will work using the external URL assuming the external URL works.

Do you have your ports properly done in your firewall? try the URL using the IP of your system instead of the URL.

Do your URLs point to the IP's so far?

www.mxtoolbox.com , great tools on that site for mail admins.
 
I would just use IMAP and SMTP remotely, but the whole thing is calenders... we have new owners so with them comes more clientel. (SP?) I will admit I have barely worked with Exchange, but I have worked lots with other mail servers and AD in general. Also SBS where it's even easier, but bare Exchange I'm lacking in. Hence why I'm messing with this on my own equipment and time. Anyways, yeah they want shared calendars... I suggested something like Google calendars, but since I'm young (20) my ideas/thoughts very often get overlooked... I digress. My ports are correct as well. OWA works great and everything, just getting this to work isn't.

I did enter in the external address that I would be using when I setup Exchange.
 
You must log in or register to reply here.
Back
Top