How To
Summary
This article describes the steps to configure both public and private network connections in Windows Virtual Service Instance provisioned in IBM Cloud.
Objective
By default, Windows Virtual Server instances are automatically configured with public and private connections when they are provisioned by IBM Cloud. The network settings set by the IBM Cloud provisioning system enable you to connect the instance through remote desktop connection without any additional configuration. However, sometimes, you might want to test packet capture or sniffer tools like Wireshark in your servers. Or some might try to create custom network connections. These actions would possibly remove the default network settings and replace them with custom configurations, which makes you unable to access your servers remotely. It also causes the servers not to receive timely Windows update from local IBM Cloud Windows Server Update Services (WSUS) servers, which could make the systems vulnerable. Hence, this article aims to provide the necessary steps to set up and restore the public and private IP addresses along with DNS and gateway in Windows Virtual Server instances.
Environment
Windows 2008, Windows 2012, Windows 2016, Windows 2019
Steps
These steps need to be executed as "Administrator" account of the system from the KVM console.
1. Open Device Manager and check the Network card. You see two network adapters such as XenServer PV Network Device #0 and XenServer PV Network Device #1 as in the following screen capture:
XenServer PV Network Device #0 is allocated for Private network connection, and XenServer PV Network Device #1 is for Public network connection.
2. Open Control Panel -> Network and Internet -> Network and Sharing Center. You see two Network connections: PublicNetwork-A and PrivateNetwork-A. If you accidentally remove these default network connections, you have to create them again manually using the "Set up a new connection or network" option.
As the name suggests, "PublicNetwork-A" is created for accessing the system by using public IP address. It also provides internet connectivity to the system. "PrivateNetwork-A" is used to connect the system securely through VPN by using the private IP address.
3. In the Network and Sharing Center screen, click "Change Adapter Settings".
You are presented with both Public and Private connections.
If you view the screen capture, you see that "XenServer PV Network Device #0" is assigned for PrivateNetwork-A and "XenServer PV Network Device #1" is allocated for PublicNetwork-A.
It is important that "XenServer PV Network Device #0" is always associated with private network and "XenServer PV Network Device #1" with public network. If you change or customize these network connections, you need to ensure that
- "XenServer PV Network Device #0" is associated with private connection or network only
- "XenServer PV Network Device #1" with public network connection or network only
If you swap these network cards wrongly to private and public connections, then you lose the remote connectivity to the system.
4. Now check the configuration of private network connection.
a) Double-click "PrivateNetwork-A" to open it. You can see the status of private network connection as in the following screen capture:
b) Click "Properties" to open the network configuration. You see the network card (XenServer PV Network Device #0) associated with this connection and the network modules that are enabled and used by the card as in the following screen capture:
c) Select "Internet Protocol Version 4 (TCP/IPv4) and click "Properties" to set the IP address, net mask, gateway, and DNS.
d) A new window opens for setting private IP address, Subnet mask, Gateway, and DNS servers.
e) Enter the private IP address in IP address field. In Subnet mask field, type your subnet ip. Leave "Default Gateway" field unfilled. You should not fill the Default Gateway for private network because both private and public traffic are handled by public gateway. In "Preferred DNS server" and "Alternate DNS server" fields, fill 10.0.80.11 and 10.0.80.12 respectively. Click "OK" to save.
5. Next, check the configuration of the public network connection.
a) Click "PublicNetwork-A" from the Network Connections window. Then, click "Properties" from the pop-up window.
b) You see that "XenServer PV Network Device #1" network card is associated to the public connection.
c) Select "Internet Protocol Version 4 (TCP/IPv4) and click "Properties".
d) Enter the public IP address in the IP address field. In Subnet mask field, type your subnet IP. In "Default Gateway" field, fill the public gateway IP address. In "Preferred DNS server" and "Alternate DNS server" fields, fill 10.0.80.11 and 10.0.80.12 respectively. Click "OK" to save.
6. Ping the DNS server (10.0.80.11) from the commandline window inside the system to check whether the system reaches the IBM Cloud DNS server.
7. Try to log on to the system through RDP using the public IP address.
8. Next, connect to the VPN and attempt to log on to the system through RDP via the private IP address.
If the logons are successful, then you completed the steps to set up and restore the public and private IP addresses along with DNS and gateway in Windows Virtual Server instances.
Related Information
Document Location
Worldwide
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCLA2","label":"Virtual Server"},"Component":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"","label":""}}]
Was this topic helpful?
Document Information
Modified date:
24 September 2019
UID
ibm11072824