Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2234
  • Last Modified:

Change OWA port from 443 to 465 on Microsoft Exchange Server 2003

I have at&t u-verse with a block of 8 static IP addresses. I am using 2, 1 to a web server and 1 to an Exchange Server 2003. The at&t gateway (private address 192.168.1.254) that serves all IP addresses (public and private) to devices uses port 443 to communicate with the Cisco WAP for wireless u-verse TV set top boxes. I have a Netgear WNDR4500 connected to a port on the gateway that serves the public ip to the netgear WAN connection. The LAN connection is 10.0.0.1 and is on the same network as my Exchange server. When I forward port 443 to my exchange server, my wireless TV boxes lose their connections. AT&T cannot change the port 443 that it communicates with the Cisco WAP. I need to change the OWA port so I can use Outlook Web Access. Can this be done?
0
Racer1950
Asked:
Racer1950
  • 2
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
You can just modify the port in IIS manager.
However that will only work for OWA. You cannot use alternative ports for ActiveSync and RPC over HTTPS. Those are hard coded to port 443 (ie HTTPS).

Although if you have a block of 8 IP addresses you must be able to do a 1:1 NAT, otherwise the block of addresses is close to useless.

Simon.
0
 
Racer1950Author Commented:
I tried to change the port for the default website in iis, but it didn't work. I hear that 443 is hardcoded in Exchange 2003 so there is no way in system manager.
I have a SonicWall TZ on one of the public ip addresses that I can do 1:1 NAT but I do not know how in the ATT gateway.
0
 
Simon Butler (Sembee)ConsultantCommented:
The ISP wouldn't give you a block of IP addresses if you couldn't use them, so there has to be a way to allow multiple addresses through to a device. I am not familiar with the AT&T implementation you have so probably not best person to ask.

Rather than changing the port in IIS, try adding an additional listener. That way 443 would continue to work internally, but would also work externally on the other port.
Another option would be port redirection, so direct port 4433 to port 443 internally etc.

Simon.
0
 
Racer1950Author Commented:
That's what I thought, but it is really difficult to get the better techs at at&t to help with a Microsoft application. I'm considering replacing the wireless receivers with wired ones.
Thanks for your help.
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

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