Platform: Windows Server 2019, 2022 and 2025, with the version and hosting restrictions described below.
Choose the gateway function before selecting features
Remote Access is a Windows Server role containing several capabilities. RRAS supplies traditional routing and VPN functions, while DirectAccess and Web Application Proxy serve different purposes. Installing their components is not the same as completing a secure network service. Begin with the function the gateway must perform: LAN routing, outbound NAT, remote-user VPN or a link to another site.
For a managed Netcloud24 environment, this design and installation work is performed by the authorised infrastructure team. Customer handover should provide the agreed connectivity and support route, not a requirement to run a gateway wizard. The following preparation is useful for administrators responsible for the underlying Windows gateway and its dependencies.
Check support for the actual hosting platform
A server can offer the relevant feature-installation command while its platform does not support the planned deployment. Microsoft explicitly excludes the Windows Server Remote Access role for VPN, DirectAccess and other Remote Access functions inside Azure VMs. That restriction is specific and should not be recast as a claim that all virtual machines are unsuitable. Supported Hyper-V gateway VMs remain a different scenario.
On another hosting platform, confirm its forwarding, public-address, protocol and anti-spoofing policies. A second virtual adapter does not guarantee permission to route another subnet through it. Record any upstream NAT, firewall or provider-controlled route that the Windows administrator cannot alter locally. Keep a console connection for recovery if a route change breaks the normal management session.
Choose availability and security boundaries. A gateway accepting external traffic should not casually share duties with a domain controller or public business application. Define patch ownership, monitoring, capacity and an alternate path if the single gateway fails. The installation task cannot resolve those architectural choices afterwards.
Map interfaces and address spaces
Document which interface faces each network, using MAC address and actual IP configuration as well as the friendly name. Reserve non-overlapping ranges for internal networks, VPN clients and remote sites. Overlap can make a correct-looking tunnel unusable because traffic is delivered locally or sent to the wrong route.
Get-NetAdapter | Select-Object Name,ifIndex,MacAddress,Status
Get-NetIPConfiguration
Get-NetRoute -AddressFamily IPv4
Get-DnsClientServerAddress
Get-NetConnectionProfile
Get-WindowsFeature RemoteAccess,Routing,DirectAccess-VPNDecide where the default route belongs. Multiple unrelated gateways on different adapters can create asymmetric replies. On a domain member, review DNS registration and access to domain services across its interfaces. A Public network profile may indicate a domain-location problem; changing the profile solely to open firewall traffic can hide that cause.
If RRAS already exists, preserve its configuration, active users and dependent routes before modifying features. A tutorial’s new-server starting point is not permission to reset a working gateway.
Install the appropriate role services
Use elevated Windows PowerShell on the intended machine. A router needs the Routing role service. A VPN server needs DirectAccess-VPN, whose name includes the components used for VPN without requiring a DirectAccess deployment. A combined approved design may use both, but do not select every service merely to avoid deciding.
# Example: prepare a LAN-routing server.
$featureResult = Install-WindowsFeature Routing -IncludeManagementTools
$featureResult | Format-List Success,RestartNeeded,ExitCode
# A VPN design would instead include its required component:
# Install-WindowsFeature DirectAccess-VPN -IncludeManagementTools
Get-WindowsFeature RemoteAccess,Routing,DirectAccess-VPNReview the result and arrange any requested restart. Administration tools can be provided on an approved management machine, particularly when the gateway uses Server Core. Do not add Web Application Proxy or other externally reachable functions without a defined requirement, authentication design and owner.
Initialise the chosen mode without invoking another deployment
For a genuinely new routing-only deployment, initialise RoutingOnly. For VPN, use its specific RRAS workflow and complete certificate, protocol, authentication and address-assignment planning before exposing it. DirectAccess examples with DAInstallType and client-policy settings describe another deployment path and should not be copied into an ordinary router setup.
# New routing-only deployment, after reviewing the baseline:
Install-RemoteAccess -VpnType RoutingOnly
Get-Service RemoteAccess
Get-RemoteAccess
Get-NetRoute -AddressFamily IPv4A Running RemoteAccess service demonstrates activation, not successful forwarding or access. If configuration already exists, inspect how the proposed change integrates with it rather than rerunning initialisation blindly. A command that reuses existing configuration can still alter shared settings, so retain the old state and plan the maintenance scope.
Apply VPN hardening to the configuration you actually have
A future VPN setup needs an explicit protocol choice and authorisation model. New Windows Server 2025 RRAS configurations do not accept PPTP and L2TP by default, but older deployments and retained upgrade configurations can behave differently. Inspect ports and policies directly rather than assuming the OS version removed historical acceptance.
IKEv2 and SSTP have different client, certificate and transport requirements. Select the approved protocols and disable unused acceptance. Do not introduce PPTP to obtain a quick successful test. Decide whether local or separate NPS handles authentication, which group may connect, how accounting is retained and whether another supported service supplies MFA. None of those controls appears automatically because the VPN role service was installed.
For external RADIUS, secure the peer relationship, source scope and shared-secret handling. For certificate authentication, make trust, revocation and renewal part of the rollout. Installation is the point at which those dependencies should become visible, not the end of the security design.
Test the assigned network function
Choose a representative client and an explicit allowed flow. For routing, prove packets and replies cross the intended subnets. For NAT, observe translated client traffic and confirm no unintended service publication. For remote VPN, test a valid user, an invalid user, assigned address, DNS and authorised resource access. For site-to-site VPN, use hosts behind both gateways rather than testing only from the routers.
Get-Service RemoteAccess
Get-NetRoute -AddressFamily IPv4
Get-WinEvent -FilterHashtable @{LogName='System';StartTime=(Get-Date).AddHours(-1)} `
-MaxEvents 60Record source, destination, protocol, time and expected result. A local gateway ping or a green service icon cannot prove a client’s complete path. Retain relevant events and upstream evidence so a later failure can be distinguished from the original installation.
Recover from a failed rollout without resetting other services
For feature failure, inspect servicing and source compatibility. For service failure, retain the precise RRAS error and dependency evidence. For network failure, investigate interfaces, routes, upstream restrictions, firewall and authentication separately. Enabling every protocol or disabling the firewall changes the boundary without identifying the cause.
Rollback only the introduced function and restore the recorded interface and routing baseline. Do not uninstall shared RRAS components while other VPN users, NAT clients or sites depend on them. Preserve logs, verify the prior working path and document the final gateway mode and ownership. This gives a managed service team a maintainable connection boundary rather than a wizard result that nobody can safely change.
Providing controlled outbound IPv4 access with RRAS NAT
Configure traditional RRAS outbound NAT from the client’s full route, assign deliberate interface roles, verify actual translations and…
Building a certificate-validated IKEv2 remote-access service
Design an IKEv2 service around gateway and EAP certificate validation, narrow NPS authorisation, managed client provisioning and external…
Connecting two routed sites through an RRAS IKEv2 interface
Connect two sites using an RRAS IKEv2 interface with machine certificates, complementary subnet routes and matched responder policy, then…
Introducing NPS as a controlled RADIUS authority
Introduce NPS with distinct AD registration and RADIUS peer trust, narrow policy matching, current integrity and certificate requirements,…
Maintaining a specific Windows Server route without changing the default path
Maintain a subnet-specific Windows route with a verified interface and next hop, prove source selection and application reachability, and…