Menu

Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

Sign In Register

Port forward website but limiting URI

TravTrav Newbie ✭
edited March 2022 in Entry Level Firewalls

Hi there,

We have a sonciwall TZ305.

We have a Server 2019 with IIS running and we want to publish a website, but we want to limit the what is published to a specific URI.

IIS has the default website and 2 seperate sites/apps on it. We want one published externally (SSL:443) but not the other. If we go to https://server.com.au/ it shows to the website we want published, but if someone enters in https://server.com.au/rdweb we dont want that published externally.

The way I see it I can either, create a new website in IIS and move the RDWeb there and specify different ports for it to use. Then use normal port forwarding out the server on 443.

Or find someway of limiting this via the Sonicwall. I think 'App Rules' may do this, but the only info I can find appears to be limiting external websites for internal users.

I look forward to hearing your suggestions.

Category: Entry Level Firewalls
Reply

Answers

  • shiprasahu93shiprasahu93 Moderator

    Hello @Trav,

    Welcome to SonicWall community.

    Since this website is hosted on HTTPS, without server DPI SSL, we will not be able to see if the client is visiting https://server.com.au/ or https://server.com.au/rdweb. Due to this reason, even if we try to create an App rule, it will not get applied.

    So, IMHO it would be best to move RDWeb to a different port as you mentioned on the server and only perform port forwarding for HTTPS to reach https://server.com.au/

    Thanks!

    Shipra Sahu

    Technical Support Advisor, Premier Services

This discussion has been closed.