Microsoft home server remote access ports

To deploy Remote Access, you need to configure the server that will act as the Remote Access server with the following:. In the Remote Access Server Setup Wizard, on the Network Topology page, click the deployment topology that will be used in your organization.

In Type the public name or IPv4 address used by clients to connect to the Remote Access server , enter the public name for the deployment this name matches the subject name of the IP-HTTPS certificate, for example, edge1. Network adapters for the networks in your deployment.

If the wizard does not detect the correct network adapters, manually select the correct adapters. This is based on the public name for the deployment that you set during the previous step of the wizard. On the Prefix Configuration page this page is only visible if IPv6 is detected in the internal network , the wizard automatically detects the IPv6 settings that are used on the internal network. If your deployment requires additional prefixes, configure the IPv6 prefixes for the internal network, an IPv6 prefix to assign to DirectAccess client computers, and an IPv6 prefix to assign to VPN client computers.

For multisite and two-factor authentication deployments, you must use computer certificate authentication. Select the Use computer certificates check box to use computer certificate authentication and select the IPsec root certificate. To enable client computers running Windows 7 to connect via DirectAccess, select the Enable Windows 7 client computers to connect via DirectAccess check box.

You must also use computer certificate authentication in this type of deployment. To configure the infrastructure servers in a Remote Access deployment, you must configure the following:. In the Infrastructure Server Setup Wizard, on the Network Location Server page, click the option that corresponds to the location of the network location server in your deployment. If the network location server is on a remote web server, enter the URL, and then click Validate before you continue.

If the network location server is on the Remote Access server, click Browse to locate the relevant certificate, and then click Next. Usually the Web page is at the IP address of your router. If necessary, type your user name and password to log on to the configuration Web page. Find the port forwarding configuration page on your router. Save the port-forwarding configuration on your router, and then close the browser. On the Remote Access Settings page, click Repair.

Open the Web browser on your computer and enter the address for the Linksys router in the address field. The default IP address is At the login screen, leave the User Name field blank and enter the router password.

The default password is admin. Click the Administration tab, the Management page should be selected. If not, click the Management tab. If not, click the Port Range Forwarding tab. Enter the settings as in the screenshot below. The IP address should be the IP address of your home server. Open the Web browser on your computer and enter the address for the Netgear router in the address field.

At the login screen, enter the user name and password. The default user name is admin. The default password is password. Configure Windows Home Server settings. Windows Home Server will attempt to automatically configure the Netgear router to forward Web site requests to your home server.

If UPnP was successfully configured you should see the three ports opened in the screenshot below. Close the Web browser. In End IP address , enter the ending IP address in the range you want to assign to VPN clients, or in Number of addresses , enter the number of the address you want to make available. For optimal network performance, the VPN server itself should not have a network interface in the same IPv4 subnet that assigns IPv4 addresses to the clients.

If the VPN server does have a network interface in that subnet, a broadcast or multicast that is sent to that subnet could cause a latency spike. Optional If you are using DHCP, select Adapter , and in the list of results, select the Ethernet adapter connected to your internal perimeter network. Select the Grant access. Grant access if the connection request matches this policy option.

Clear the Remote access connections inbound only and Demand-dial routing connections inbound and outbound check boxes. In Maximum ports , enter the number of ports to match the maximum number of simultaneous VPN connections that you want to support. If prompted, select Yes to confirm restarting the server and select Close to restart the server.

Step 4. You also configure NPS to handle all authentication, authorization, and accounting duties for connection requests that it receives from the VPN server. Skip to main content. The place where it differs, I think, is the client-side. The WHS end-user will want to connect to their machine from locations such as the office or on the road travelling.

This is why I brought up the internet cafe as well. The beauty of HTTPS is that you can securely wrap anything you want in it and have a decent expectation of privacy. This would include the tight proxies like I just mentioned. No worries about what type of network they are on, etc. They shouldn't have to worry about that. They will always see this as a WHS problem.

In fact, it is something that WHS could resolve -- in a future release of course. I fully agree that this was the best way to get the bang for the buck. The WHS team cleverly reused many components of other products and have put together a decent package that users will find compelling. I disagree however, that they would have to rewrite or reinvent RWW. There are many other programs that do this kind of thing.

Thursday, July 19, PM.