psychedelicshark
asked on
Cannot access Exchange server VIA Outlook Web Access from outside the local network
We have Exchange Server 2000 running on our fileserver and we're able to access it from inside the office by entering 192.168.1.25/exchange. However, if we try to access our mail from home or on the road by entering www.domain.com:1010/exchange into an Internet Explorer Address bar, we receive the following error message.
=======================
The page cannot be displayed
The page you are looking for might have been removed or had its name changed.
Please try the following:
Open the s: home page, and then look for links to the information you want.
If you typed the page address in the Address bar, make sure that it is spelled correctly.
If you still cannot open the page, click the Internet Explorer
Search button to look for similar sites.
=========================
If we try to access an account using Firefox, we receive THIS error message
=========================
* OK Microsoft Exchange 2000 IMAP4rev1 server version 6.0.6249.0 (FILESVR.digitaloriginalin
GET BAD Protocol Error: "Unidentifiable command specified".
Host: BAD Protocol Error: "Unidentifiable command specified".
User-Agent: BAD Protocol Error: "Unidentifiable command specified".
Accept: BAD Protocol Error: "Unidentifiable command specified".
Accept-Language: BAD Protocol Error: "Unidentifiable command specified".
Accept-Encoding: BAD Protocol Error: "Unidentifiable command specified".
Accept-Charset: BAD Protocol Error: "Unidentifiable command specified".
Keep-Alive: BAD Protocol Error: "Unidentifiable command specified".
Connection: BAD Protocol Error: "Unidentifiable command specified".
Cache-Control: BAD Protocol Error: "Unidentifiable command specified".
* BYE Microsoft Exchange 2000 IMAP4rev1 server version 6.0.6249.0 closing connection: invalid command limit exceeded.
=====================
We have a Linksys router with port 1010 forwarded to the Exchange server. Any ideas?
=======================
The page cannot be displayed
The page you are looking for might have been removed or had its name changed.
Please try the following:
Open the s: home page, and then look for links to the information you want.
If you typed the page address in the Address bar, make sure that it is spelled correctly.
If you still cannot open the page, click the Internet Explorer
Search button to look for similar sites.
=========================
If we try to access an account using Firefox, we receive THIS error message
=========================
* OK Microsoft Exchange 2000 IMAP4rev1 server version 6.0.6249.0 (FILESVR.digitaloriginalin
GET BAD Protocol Error: "Unidentifiable command specified".
Host: BAD Protocol Error: "Unidentifiable command specified".
User-Agent: BAD Protocol Error: "Unidentifiable command specified".
Accept: BAD Protocol Error: "Unidentifiable command specified".
Accept-Language: BAD Protocol Error: "Unidentifiable command specified".
Accept-Encoding: BAD Protocol Error: "Unidentifiable command specified".
Accept-Charset: BAD Protocol Error: "Unidentifiable command specified".
Keep-Alive: BAD Protocol Error: "Unidentifiable command specified".
Connection: BAD Protocol Error: "Unidentifiable command specified".
Cache-Control: BAD Protocol Error: "Unidentifiable command specified".
* BYE Microsoft Exchange 2000 IMAP4rev1 server version 6.0.6249.0 closing connection: invalid command limit exceeded.
=====================
We have a Linksys router with port 1010 forwarded to the Exchange server. Any ideas?
ASKER
Thanks Ben. That's what I figured, but I can't find any documentation on how to change the port that Exchange server listens to. I'd leave it on port 80, but we have a web server on the same subnet with Exchange Server 2003 installed. I've considered migrating, but I'm afraid it'd be just another project exploding in my face. :(
Any further suggestions? Thanks in advance.
Chris
Any further suggestions? Thanks in advance.
Chris
I have had nothing but hassle when trying to get Exchange to operate on any other port than 80 or 443. Remember that OWA is a very complex web application and is made up of lots of components.
If you have another web server already in place, then you really only have one option that has any chance of working, and that is to use SSL. Get a cheap certificate from FreeSSL.com and then redirect traffic on 443 only to the Exchange server. If you use a different URL and host headers (mail.domain.com for example) then anyone who enters https://www.domain.com will not end up at Exchange.
Simon.
If you have another web server already in place, then you really only have one option that has any chance of working, and that is to use SSL. Get a cheap certificate from FreeSSL.com and then redirect traffic on 443 only to the Exchange server. If you use a different URL and host headers (mail.domain.com for example) then anyone who enters https://www.domain.com will not end up at Exchange.
Simon.
Can I hear an AMEN? :-)
In all seriousness, you CAN change the port that the Exchange server listens on for OWA, but results can vary. If you do want to try and change it, on your Exchange sever, go to IIS Manager and go to the properties of your Default Web Site. In there, you will see the port used for TCP (regular HTTP) and SSL. You can try and change the port in there to 1010 and see if that works, but it really isn't an elegant solution, as you will be placing the burden on your users of remembering to type in the port each time.
Ben
In all seriousness, you CAN change the port that the Exchange server listens on for OWA, but results can vary. If you do want to try and change it, on your Exchange sever, go to IIS Manager and go to the properties of your Default Web Site. In there, you will see the port used for TCP (regular HTTP) and SSL. You can try and change the port in there to 1010 and see if that works, but it really isn't an elegant solution, as you will be placing the burden on your users of remembering to type in the port each time.
Ben
ASKER
Well. This is turning into a real adventure. :)
So far, I've learned that something else (God only knows what) is using port 1010 on the Exchange server, so I changed it to listen on port 1020 and changed the port forwarding on the router. Using Firefox, I'm in. No muss, no fuss. But using IE6, I get...
====================
The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.
Please try the following:
Click the Refresh button, or try again later.
If you typed the page address in the Address bar, make sure that it is spelled correctly.
To check your connection settings, click the Tools menu, and then click Internet Options. On the Connections tab, click Settings. The settings should match those provided by your local area network (LAN) administrator or Internet service provider (ISP).
See if your Internet connection settings are being detected. You can set Microsoft Windows to examine your network and automatically discover network connection settings (if your network administrator has enabled this setting).
Click the Tools menu, and then click Internet Options.
On the Connections tab, click LAN Settings.
Select Automatically detect settings, and then click OK.
Some sites require 128-bit connection security. Click the Help menu and then click About Internet Explorer to determine what strength security you have installed.
If you are trying to reach a secure site, make sure your Security settings can support it. Click the Tools menu, and then click Internet Options. On the Advanced tab, scroll to the Security section and check settings for SSL 2.0, SSL 3.0, TLS 1.0, PCT 1.0.
Click the Back button to try another link.
Cannot find server or DNS Error
Internet Explorer
GRRRRRRRRRR!!!!!!!!!!!
So far, I've learned that something else (God only knows what) is using port 1010 on the Exchange server, so I changed it to listen on port 1020 and changed the port forwarding on the router. Using Firefox, I'm in. No muss, no fuss. But using IE6, I get...
====================
The page cannot be displayed
The page you are looking for is currently unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings.
Please try the following:
Click the Refresh button, or try again later.
If you typed the page address in the Address bar, make sure that it is spelled correctly.
To check your connection settings, click the Tools menu, and then click Internet Options. On the Connections tab, click Settings. The settings should match those provided by your local area network (LAN) administrator or Internet service provider (ISP).
See if your Internet connection settings are being detected. You can set Microsoft Windows to examine your network and automatically discover network connection settings (if your network administrator has enabled this setting).
Click the Tools menu, and then click Internet Options.
On the Connections tab, click LAN Settings.
Select Automatically detect settings, and then click OK.
Some sites require 128-bit connection security. Click the Help menu and then click About Internet Explorer to determine what strength security you have installed.
If you are trying to reach a secure site, make sure your Security settings can support it. Click the Tools menu, and then click Internet Options. On the Advanced tab, scroll to the Security section and check settings for SSL 2.0, SSL 3.0, TLS 1.0, PCT 1.0.
Click the Back button to try another link.
Cannot find server or DNS Error
Internet Explorer
GRRRRRRRRRR!!!!!!!!!!!
ASKER
Okay. For everyone's edification the IE6 problem seems to have been resolved like so:
First go to www.domain.com
Then go to www.domain.com:1020 and get error message
Finally, go to www.domain.com:1020/exchange and boom, it's fixed.
Go figure.
First go to www.domain.com
Then go to www.domain.com:1020 and get error message
Finally, go to www.domain.com:1020/exchange and boom, it's fixed.
Go figure.
ASKER
PS- Thanks again, guys.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Ben