If you manually install Windows on your server, you will not automatically have the network route added to your server.

Note: Not all of our servers are currently in our pods with Private Networking. Some of our budget servers also lack secondary NICs and it may not be possible to add a private network connection. Check with support if you're not sure.

First, you need to make sure your server was assigned a Private IP address. If your server does not have a private IP, you can request one from support.

You can find your IP address in the Server Manager. Take note of the information.

Within Windows, open up Network Connections and find the Ethernet 2 adapter. Right click on it and select Properties.

Select Internet Protocol Version 4 (TCP/IPv4), click Properties, and then click on Use the following IP address. Enter your assigned IPv4 address (10.90.x.x) and subnet mask (check Server Manager for the correct subnet mask to use). Important: Leave The Default Gateway Blank! 

Click OK and then OK again. You should have a Private Network connection. 

Open the Start menu, search for CMD. Right click and run as administrator.

Once you open the command prompt, type in the following command. The last IP should be the Gateway listed in Server Manager. In this example, the Gateway is 10.90.0.254. 

route -p add 10.0.0.0 MASK 255.0.0.0 10.90.0.254

Once you type that in, press enter. You should see an "OK!"

If you want to use our internal DNS servers, set your DNS server on the private network interface (Ethernet 2) to your Gateway IP. Then edit your Ethernet interface and remove any DNS servers there. This will force Windows to use the Private Network for DNS.