Port 443 used by exchange but needed for Citrix Secure Gateway

Either:

1) Change the CSG port, which will work though isn't advisable as users will have to enter that port whenever they want to connect (e.g. https://citrix.mycompany.com:445).

2) Obtain a second public IP.  Some expense involved.

Maybe I misunderstood.  If CSG is listening on a port other than 443 wouldn't that port need to be appended to the URL entered in to the browser?

I changed the CSG port and IIS port and everything is working great. Carl is right, I did not need to use the port number in the url.

Thanks so much for everyones help.

I feel I may have awarded points incorrectly but more importantly posted an incorrect solution. I just got back to this project and noticed that I am having to use the port number at the end of the URL. Nothing has changed and I double checked all settings. I probably posted too quick without fully testing. If I dont use the port number, I go to IIS on my exchange box https://citrix.domain.com but with https://citrix.domain.com:444 I go to WI/CSG.

I thought it worked before without it but I guess I was seeing things.

Yep.  If you change a listening service's port then the client, in this case your web browser, needs to communicate over that port rather than the default.  So if you change CSG to listen on 444 then the client needs to pass the URL request appended with 444.