If the device under test (DUT) is connected to a subnet but configured with an IP address that is outside of own subnet, one can add a route to that device into computer's routing table. As there is no router that would forward traffic from own subnet to the IP address of DUT, the IP address of the device can be substituted for the router's address as if the device would forward IP packets addressed to it. On Windows 7 Ultimate:

1. Start administrator's shell: Administrative Tools > Windows PowerShell Modules
2. Add route to DUT: route -p ADD DUT_IP_address MASK 255.255.255.255 DUT_IP_address

-p option makes the command to store routing information permanently into the routing table.

Example

IP address of the DUT is 193.167.101.107 but unfortunately laboratory subnet is 192.168.0.0/16 meaning there is no route to the DUT. Add route by defining DUT to be its own router:

PS C:\Windows\system32> route -p ADD 193.167.101.107 MASK 255.255.255.255 193.167.101.107
 OK!
PS C:\Windows\system32> ping 193.167.101.107

Pinging 193.167.101.107 with 32 bytes of data:
Reply from 193.167.101.107: bytes=32 time=1ms TTL=64
Reply from 193.167.101.107: bytes=32 time<1ms TTL=64
Reply from 193.167.101.107: bytes=32 time<1ms TTL=64
Reply from 193.167.101.107: bytes=32 time<1ms TTL=64

Ping statistics for 193.167.101.107:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms
PS C:\Windows\system32>