Troubleshooting > Connections to Virtual Machines

Troubleshooting Problems With Hyper-V Connectivity

The following checklist helps to find and fix any possible issues when working with Hyper-V machines:

1.Is PowerShell 3.0 installed (both on Guest and Host Machine)?

a.Check $PSVersionTable.PSVersion in PowerShell

2.Is the machine properly configured in the Settings > Virtual Machines screen (pay attention to hardcoded IP addresses which may be dynamically assigned by DHCP)

3.Is RayPack Studio Tools for Hyper-V installed on the Guest machine? Is the process vm-proxy.exe from RayPack Studio Tools for Hyper-V running?

4.Is WINRM configured?

a.Check winrm qc

5.Does WINRM have proper TrustedHosts entries on both VM and server?

a.winrm s winrm/config/client '@{TrustedHosts="RemoteComputer"}'

b.winrm g winrm/config/client - shows the current TrustedHosts lists

c.More information: https://technet.microsoft.com/en-us/library/ff700227.aspx

6.Does WINRM have a connection to the VM and vice-versa?

a.- Test-WSMan -ComputerName IP

7.Are all necessary ports unblocked on the physical machine?

a.The default port range is 48654-48999.

Changing TCP / IP Configuration

In some cases it may be required to use custom port ranges, timeouts, etc. for PackBot related functionality.

The following table summarizes the available options:

Setting name	Default value	Description
TcpIpDefaultPort	48654-48999	Port range used for TCP/IP communication. Use minus (-) and comma (,) to indicate which ports are valid for incoming communication. Make sure that these ports are not blocked by your firewall. PackBot tries to find first valid free port and listen on it from lower to higher numbers.
TcpIpMaxRetry	3	Maximum number of retries before asserting the machine is not available..
TcpIpDefaultReceiveTimeout	240000	Reverts to default value if Windows does not define its own timeouts.
TcpIpDefaultSendTimeout	240000	Reverts to default value if Windows does not define its own timeouts.