By default, all rUsers on a given Injector will generate traffic from the same IP address.
For most cases, this has no effect on testing and saves IP address space. However, in certain situations using a single IP is undesirable or incompatible, for example when testing applications that track IP addresses, depend on specific ports, or when network security policies limit simultaneous connections from the same IP address.
Fortunately, on Windows Server 2008 R2 and later, Remote Desktop Services does provide a solution. We can configure the Terminal Server on our Injector(s) to use a unique IP address per Remote Desktop Session using a new feature called IP Virtualization.
- Injector running Windows Server 2008 R2 or later.
- DHCP enabled
- Available IP addresses on your network
On your Injector machine, go into the Control Panel and then open Administrative Tools.
You should see a folder in Administrative Tools called “Remote Desktop Services”
Note: In “Category View,” Administrative Tools is under the “System and Security” category
Inside this folder there is a tool called “Remote Desktop Session Host Configuration,” open it
At the bottom of the configuration panel is a setting called “IP Virtualization”
Double-click “IP Virtualization” to bring up its Properties
Check the box for “Enable IP virtualization,” choose your preferred Network Adapter in the drop-down list (usually the default), and ensure that the “IP virtualization mode” is “Per Session.”
Hit “Apply” and/or “OK” and you are now properly configured.
You will need to restart any existing Remote Desktop Connections or running rUsers for the new settings to take effect. From now on, each Remote Desktop Session/rUser will use a unique IP Address.