superaz300 Posted June 11, 2019 Posted June 11, 2019 Hi Guys, Just wondering how many people are successfully using Reverse Proxy within Smoothwall to use Remote Desktop Services and Exchange? I have it kind of working, and I can get to the correct pages for https://remote.mydomain.co.uk and https://mail.mydomain.co.uk. However, when using RDS, once the RDP file has been downloaded, it hangs on "Initiating remote connection". Has anyone had this issue before? I have the following rules setup in Smoothwall. External Address: https://remote.mydomain.co.uk - Internal Address: https://IPOFRRDSSERVER External Address: http://remote.mydomain.co.uk - Internal Address: http://IPOFRDSSERVER External Address: https://mail.mydomain.co.uk - Internal Address: https://IPOFMAILSERVER External Address: http://mail.mydomain.co.uk - Internal Address: http://IPOFMAILSERVER External Address: https://autodiscover.mydomain.co.uk - Internal Address: https://IPOFMAILSERVER I have both HTTP and HTTPS for HTTP redirection. Can anyone see anything wrong? Kind regards James
Jonah Posted June 11, 2019 Posted June 11, 2019 We’ve historically had trouble with the reverse proxy, so reverted to standard port forwards to 443 for OWA and RDWEB
superaz300 Posted June 11, 2019 Author Posted June 11, 2019 We’ve historically had trouble with the reverse proxy, so reverted to standard port forwards to 443 for OWA and RDWEB I had a feeling you was going to say this. Smoothwall support told me, I quote "Reverse proxy will work sometimes and not others"... the problem is I don't have more than 1 public IP address, so I can only port forward HTTPS to either the mail server or RDS. The mail server has been here for ages, I just wanted to introduce RDS recently.
computer_expert Posted June 11, 2019 Posted June 11, 2019 I've never had much luck with reverse proxies & remote desktop gateway/services unless you use the Web App Proxy roles built in to windows server.
Cache Posted June 11, 2019 Posted June 11, 2019 I gave up on using it for Remote Desktop Gateway and went for a Port Forward instead.
superaz300 Posted June 12, 2019 Author Posted June 12, 2019 I gave up on using it for Remote Desktop Gateway and went for a Port Forward instead. I would love to go for a port forward, but this all depends if I can get another public IP address from our ISP... at the moment we only have the 1. Its either that, or I wait until we move from Exchange to Office 365 and then I can use 443 for RDS. James
ibpalle Posted June 13, 2019 Posted June 13, 2019 It may be possible to use non standard port on your RDS? Depends on your users and if they are capable of using links with port number is them.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now