CloudConnexa: Access to Private Resources Fails After a Windows Server Update

Overview

After a Windows update on a Window Server running as Network connector, access to private resources through CloudConnexa may stop working.

This issue can occur if the update causes the Routing and Remote Access Service (RRAS) to reset, removes the NAT configuration, or changes the network interface configuration. As a result, traffic from clients are no longer routed correctly between the OpenVPN tunnel interface and the private network.

This guide explains how to verify the NAT configuration and reconfigure RRAS if necessary.

Step 1: Verify the Existing NAT Configuration

1. Open Routing and Remote Access (RRAS).

2. Expand your server name.

3. Expand IPv4.

4. Select NAT.

Verify whether the NAT configuration is still present.

Expected configuration:

• One interface configured as:

  • Public interface connected to the Internet

  • Enable NAT on this interface

• One interface configured as:

  • Private interface connected to private network

If the NAT configuration is missing or the interfaces are no longer configured correctly, proceed to Step 2.

Step 2: Reconfigure RRAS and NAT

Disable the Existing RRAS Configuration

1. Open Routing and Remote Access (RRAS).

2. Right-click the server name.

3. Select Disable Routing and Remote Access.

4. Confirm the action.

    

   

Re-enable RRAS

1. Right-click the server name.

2. Select Configure and Enable Routing and Remote Access.

3. Click Next.

4. Select Custom Configuration.

    

   

5. Click Next.

6. Select:

   • NAT

   • LAN Routing

7. Click Next.

    

   

8. Click Finish.

9. Click Start Service when prompted.

    

   

Step 3: Configure the Public Interface

1. Expand:

   • Server Name

   • IPv4

   • NAT

2. Right-click NAT and select New Interface.

    

   

3. Select the interface connected to the Internet (typically Ethernet).

4. Select:

   • Public interface connected to the Internet

   • Enable NAT on this interface

5. Click Apply and OK.

    

   

Step 4: Configure the OpenVPN Interface

1. Right-click NAT and select New Interface again.

2. Select the OpenVPN tunnel interface (commonly named OpenVPN Connect DCO, OpenVPN Wintun, or Local Area Connection depending on the server configuration).

3. Select:

   • Private interface connected to private network

4. Click Apply and OK.

    

   

Step 5: Verify the Configuration

Confirm that NAT now shows:

After the configuration is complete:

1. Verify that the CloudConnexa Connector is connected.

2. Verify access to private resources from a connected client.

3. Test connectivity using:

   • Ping

   • RDP

   • SSH

   • Application-specific traffic

Expected Result

After the NAT configuration is recreated, traffic should once again be routed correctly between Clients and the private network, restoring access to private resources.