Tag: Ports

Cloud Shell Configure Port Web Preview

Preview Web Apps with Azure Cloud Shell Web Preview

If you have worked with the Azure Cloud Shell in the last couple of days, you might have seen a new button called Web Preview. The Azure Cloud Shell Web preview feature allows you to run web applications on the Cloud Shell container instance and preview them before you deploy them. You can run web applications that listen to HTTP requests on the Cloud Shell from port 1025-8079 and 8091-49151.

If you are running for example a .NET Core application in Cloud Shell, you can preview this to the Cloud Shell gateway.

I have created a short video tutorial to show you the Azure Cloud Shell Web preview feature.

How to use the Cloud Shell Web Preview

First you need to run your application, in my case I run a simple .NET Core web application. This also works with other applications which can run in Cloud Shell and can map a local port.

Cloud Shell Web Preview dotnet

dotnet run

By default, this will use port 5000. Now you can create a simple port mapping by clicking on the Web Preview button in Cloud Shell.

Cloud Shell Configure Web Preview

This will open up the configuration menu to create the port mapping, where you can select port to use from 1025-8079 and 8091-49151.

Cloud Shell Configure Port Web Preview

Now you can access the application running inside your Cloud Shell container through the gateway, to preview your application.

Web Preview

I hope this was helpful and gave you a quick overview about the Web Preview feature in Cloud Shell. If you have any questions, please let me know in the comments.

You can run Azure Cloud Shell from in the Azure Portal or directly from shell.azure.com.

If you want to learn more about Cloud Shell, check out my video about Mastering Azure using Cloud Shell.

How to Install VPN on Windows Server 2008 R2

This HowTo should show you how to install a VPN Server on Windows Server 2008 R2. This is a HowTo for a small environment or a stand-alone hosted Server.

  1. Install the Role “Network Policy and Access Services” with the Server Manager
    Install Role Network policy and Access ServicesInstall Role Network policy and Access Services
  2. Select the Role Services “Routing and Remote Access Services”
    Install Role Network policy and Access ServicesInstall Role Network policy and Access Services
  3. Configure and Enable Routing and Remote Access in the Server Manager.
    Configure and Enable Routing and Remote AccessConfigure and Enable Routing and Remote Access
  4. Choose “Custom Configuration” if you just have one Network Interface in the Server
    Custom Configuration
  5. Choose “VPN access”
    VPN access
  6. Finish and click next
    VPN accessVPN access
  7. Allow access for users “Network Access Permission”. You can set that in de Dial-In Tab under the User Premission.
    User Permission Dial-In Access
  8. Open Ports in your FirewallFor PPTP: 1723 TCP 47 GRE
    For L2TP over IPSEC: 1701 TCP 500 UDP
    For  SSTP: 443 TCP

Optional: If you don’t have a DHCP Server in your local network you have to add a static address pool. This could be if you have a stand-alone Server by your provider.

  1. Right click on “Routing and Remote Access” and open Properties
    Add Static address pool
  2. Click on the IPv4 Tab and check “Static address pool”
    Add Static address pool
  3. Add a static address pool of private IP addresses
    Add Static address pool
  4. Add secondary IP Address to the Server network interface which is in the same subnet as this pool.

I also have other posts for about installing VPN on Windows Server: