Private networks for VPS on Windows

Private networks allow you to connect multiple VPS servers into a single closed network within the data center. All traffic between them passes through an internal channel without accessing the internet.

This provides enhanced security and significantly higher data exchange speeds compared to the public network.

Activate the private network

1. Log in to your Fornex Dashboard.
2. Go to the section Virtual servers → Private network.
3. Create a new private network or select an existing one.

Setting up private network for VPS in Fornex

4. Add the required VPS servers to the network (they must be in the same location).

Setting up private network for VPS in Fornex

Configure the network interface on VPS

To make the private network work, you need to manually configure the second network interface on each server. The address range is 192.168.1.0/24.

You can use any free IP from this range, except .1 and .255.

Example setup on Windows (using Server Manager)

1. Open Server Manager → go to the Local Server tab.
2. Locate the Ethernet parameter (or Ethernet 2, Ethernet Instance 0 2 — this is the second interface added for the private network).

Local Server dashboard in Server Manager

3. Right-click on the Ethernet Instance 0 2 connection → Properties.

Selecting the connection in Network Connections

4. Select Internet Protocol Version 4 (TCP/IPv4) → Properties.

Ethernet Instance properties in Server Manager

5. Select Use the following IP address and enter:
   • IP address — a free address from the 192.168.1.0/24 range, for example 192.168.1.10.
     (Use different addresses on different servers, but within the same subnet)
   • Subnet mask — 255.255.255.0.
   • Default gateway — your router's IP address, for example 192.168.1.1.
   • Preferred DNS server — 8.8.8.8 (public Google DNS).
   • Alternate DNS server — can be left empty.

Configuring the connection parameters

6. Check the information in the Local Server dashboard after applying the changes:

Local Server dashboard in Server Manager after network settings changes

Verifying the private network

From the current server, run a ping to the private IP of the second server:

ping 192.168.1.15

You should see successful responses with very low latency (usually < 1 ms):

Verifying private network VPS connection

Your VPS servers can now securely and quickly exchange data within the private network.