Click to See Complete Forum and Search --> : Linksys BEFSR41 and OWA?


Ranger
10-20-2002, 04:54 AM
Hi to all
question regarding OWA and a linksys...

First some history of the network installed:
Fractional T1 coming into a Cisco 1720 (for VPN and filtering), then crossover to a linksys (config'ed as gateway, setup as a 10. subnet), the default ports open for browsing. From the hubs, connected to a NT4 box running Exchange 5.5 (yeah, I know but I inherited this mess).
Former "IT" type decided that there was too much traffic on the network and the server was running too slow and she decided to reboot server and reset the linksys box...thereby loosing all the settings that were initially setup for exchange webaccess....to make matters worse, when she left the company, she also took all documentation (screenshots and such) of the setup and now I've got a super mess on my hands :(

Anyone here know the ports and/or triggering that needs to be enabled for exchange webaccess to work properly?

I can ping the the server; http://mail.xxxxxx.com/exchange but nothing comes up for login, password, or domain.

Greenstead
10-20-2002, 05:50 AM
I'm not an Exchange expert. But you might try reading this technet article which discusses port static mapping for OWA access. You may need to inspect the server registry to find out which static ports have been used.

http://www.microsoft.com/technet/treeview/default.asp?url=/technet/itsolutions/ecommerce/maintain/operate/d5nlb.asp

e.g. an extract :
"On the firewall, it is important to enable several TCP ports to allow the Outlook Web Access server to connect successfully to the Microsoft Exchange Server directory and information store. Because Microsoft Exchange Server randomly assigns ports for the directory and information store by default, you must statically map the ports that clients will use.

The following steps describe the registry entries that must be added to allow static port mapping. In this example, port 1225 is mapped to the directory and port 1226 is mapped to the information store.

Important Do not assign ports immediately above the 1023 range to the directory and information store. This may cause other problems with Microsoft Exchange Server.

Using the Registry Editor on the Microsoft Exchange Server computer, add the following entry for the Microsoft Exchange Server directory in HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services
\MSMicrosoft Exchange ServerDS\Parameters:
Entry: TCP/IP port REG_DWORD
Value: port number to assign
For example, in the port number "dword:000004C9(1225)" the decimal number 1225 (4C9 in hexadecimal format) is for the directory.
Add the following entry for the information store in
HKEY_LOCAL_MACHINES \System \CurrentControlSet \Services
\MSMicrosoft Exchange ServerIS\ParametersSystem:
Entry: TCP/IP port REG_DWORD
Value: port number to assign
For example, in the port number "dword:000004CA(1226)" the decimal number 1226 (4CA in hexadecimal format) is for the information store.
Quit the Registry Editor.
After enabling these ports on the firewall, test your configuration and verify that a browser can connect successfully with the Microsoft Exchange Server over the Internet. For test purposes, use Outlook (using TCP transport) to connect to the Microsoft Exchange Server. If you are able to connect with Outlook, the Outlook Web Access client will also connect. If Outlook does not connect to Microsoft Exchange Server, check the firewall settings and verify the Microsoft Exchange Server configuration."

Good Luck.

Ranger
10-20-2002, 06:36 AM
Wow, thanks for getting back to me....Gonna remote into that thing tomorrow and check it out.

Thanks for the quick response!