Need to allow port 446 thru the firewall

I am a total newbie on Pix 515.   I have a two websites sitting on the DMZ.  They share the same IP address.  I am using host headers to direct to the correct site.  They both use SSL.  One is using port 443 and the other is using port 446.  IP of the web server is

https works for the website using port 443, but the site using port 446 can only be accessed on the LAN, not the WAN.    

Any help on how to open port 446 on the PIX so this site can be accessed from the outside would be appreciated.

Who is Participating?
lrmooreConnect With a Mentor Commented:
you have to create a static xlate, then open the port in the access-list.

static (inside,outside) tcp interface 446 446 netmask
access-list outside_access_in permit tcp any interface outside eq 446
Yes, this does pose a problem... if you're trying to host 2 SSL websites on the same IP address you will need a  web server that supports SSL host headers (like IIS 7). It is not possible to run two SSL websites on port 443 on the same IP address unless you have SSL host headers.
You CAN open up port 446 to the outside, but this is NOT a pratical solution as ALL browsers default to port 443 for SSL. Maintaining redirects and proper linking in an SSL site that doesn't use the default port is a nightmare and usually unmaintainable. It's especially bad if the same code ever runs on a regular HTTP (port 80) connection.
I highly recommend getting a second public static IP from your ISP. That is the correct solution to this problem. Redirecting to port 446 will cause problems with web search engines that crawl the site and lots of other things.
BTW -- if you have Vista business or ultimate or Windows Server 2008, you have IIS 7. This is the only way to do this with one public IP and two or more SSL sites. I don't believe there is currently an open source or free web server that supports SSL host headers (What? MS invented something? Lol.).
Let me know if that info helps!
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

FMAIntlAuthor Commented:
The server is 2003 Server and I am running IIS 6.

Both sites on this webserver are actually for employees only.  The application I am trying to use port 446 for actually requires SSL.   So, when the employees are given the URL, I can actually put in in the message for the URL to book mark.

 Does that change any of the recommendations or do I still need to get a second IP?  I would rather not burn one for an employee only app.
FMAIntlAuthor Commented:
lrmoore - you mentioned these two commands
static (inside,outside) tcp interface 446 446 netmask
access-list outside_access_in permit tcp any interface outside eq 446

Can I just put those into the command line function in the Pix PDM?  I do not know how to make changes to that firewall other than thru the PDM.
PugglewuggleConnect With a Mentor Commented:
If the app has no problem using 446 then go for it and avoid wasting that IP! It's just not recommended for public sites.
Yes, you can enter those through the command function of the PDM. Those setup the forwarding of port 446 as requested.
Please note that the access-list command needs to have the name replaced with the name of your current access-list.
FMAIntlAuthor Commented:
Pugglewuggle's comments made me think.  I want to do this the right way.  I realized I had never actually used https to access the other website from outside the LAN, only http. So I tried and that and it doesn't work either! I get invalid hostname.  

So now I wonder what is using port 443.   Netstat/PUTIL shows that  Citrix Metaframe Secure Gateway is listening on port 443.  

I had assumed the first site had port 443 set in the SSL port in IIS, well it was actually set to port 444.  I had assumed it was using 443 (sorry should have checked before I submitted the question).

So now I have Citrix using port 443 for SSL.  That access works.  But, my other two sites https access don't work at all.  

So, does that mean I need to have 3 public IPs?   I said I was a newbie, so here is a dumb question -

I get a two new public IPs for these two sites. I would have to
1 - Change the PIX to route https traffic for those new IPs to  
2 - In IIS - remove the host headers
3 - In IIS - change the sites to use the public ips instead of
4 -In IIS - change the SSL ports to 443 for these sites.  
Here is dumb question #2 -  I get an error now trying to use port 443 for SSL on the site because Citrix has it.  Will I still have that same problem and have to use a different port for SSL? Then aren't I back at square one?   Don't laugh - I said I was new at this!
PugglewuggleConnect With a Mentor Commented:
That is right: it won't work from the inside by default. You need a thing called "hairpinning" to access servers from inside the LAN.
Is the 1st site a public site or another employee site (the 444 one)?
Is there a way to get Citrix to work on a port other than 443? If not, and the 1st site is for the public, you will need to use another public IP.
No - you don't have to have 3 public IPs. For that matter, you can theoretically run over 65,000 SSL sites on one public IP. The only 3 times you really need to use port 443 are a) when the site is for use by the public. Search engines don't like SSL sites not being on 443, and b) if more than one of the apps running SSL cannot be used a port other than 443, or c) you have a public site and the something that also has to run on SSL (in this case you need 2 IPs).
What error do you get when trying to access site?
I'm not laughing - getting SSL setup can be complicated at times. :) I understand.
FMAIntlAuthor Commented:
The site using 444 is also an en employee only site.   All the public sites are hosted off site, which is why I don't know how to set some of this stuff up, that is all done by the hosting site:)

I haven't tried to move Citrix to another port, I could try that.

The site using port 444 gets a generic error BadHost - Invalid address when I try to use HTTPS to access it over the WAN using If I use, it works fine.

FMAIntlAuthor Commented:
PIX didn't allow 444 either.  I added both 446 and 444 and everything works now.  Thanks for the help and the education on this topic!!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.