• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 368
  • Last Modified:

OWA on Exchange

I have one exchange server and want to configure this server with a public IP address so that clients can access their email over the web at home.

Is it possible to do this with the one exchange box? any ideas how i would do this?
0
Avatar261
Asked:
Avatar261
  • 4
  • 4
  • 2
2 Solutions
 
Avatar261Author Commented:
this is an EX2003 server
0
 
MicrotechCommented:
very possible with one box.
What is your setup and I can help more, do you have a firewall?

you can just open port 80 and NAT it to the exchange server but I would go secure though.
http://www.petri.co.il/configure_message_security_in_owa_2003.htm

post back with details of what software you use and I will get you more info
0
 
Avatar261Author Commented:
Yes, use a netpilot firewall at present.

All SMTP mail is forwarded by this to the exchange box. Do you need anymore info?

Do i just add the public address to the 2ND NIC? really dont have a clue how to do this!
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
MicrotechCommented:
on the firewall you have opened port 25 then... and passed this through to the internal address of the exchange server. you will need to open port 80 and point it to the exchange server also. there is a NAT configuration somewhere on the firewall config. Opening port 80 is less secure though as passwords are sent plain text.
here is a guide http://www.microsoft.com/downloads/details.aspx?FamilyID=847774D9-DB4A-444B-A5C9-D0B01958F6B7&displaylang=en

this is how to set up ssl Although it is for 2000 it is still relavant http://go.microsoft.com/fwlink/?linkid=3052&kbid=320291

0
 
leehewsonCommented:
I personally wouldn't like to give an Exchange server a public IP address. The best thing to do is to use NAT on the firewall and point IP traffic for ports 25 (smtp), 80 (http) and maybe 443 (https) to the internal IP address of the Exchange server. That way mail can be delivered by you isp to the Exchange server and to use outlook web access from an external source, people can type in http://(your router/firewall ip address)/exchange. If you are using small business server 2003 then you'll have to use a scure connection for it to work properly: https://(your router/firewall ip address)/exchange. Hope this helps.
0
 
Avatar261Author Commented:
If i did it that way could there not be a DNS entry created that pointed the external address at the server so that instead of having

http://(your router/firewall ip address)/exchange

i could have

http://<server.domain>/exchange

is that possible?
0
 
leehewsonCommented:
Have a chat with the company you registered your domain with and ask them if they will set that up for you. I can't see it being a problem.
0
 
MicrotechCommented:
your mx record should do ... ie http://mail.yourdomain.com/exchange

0
 
Avatar261Author Commented:
Would i obviously need an external record as well as an internal?
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now