Unable to connect to a Results PC

If you are using a second Timing PC as a results PC, but are unable to connect to the Main Timing PC here are a few things to test to help resolve it. 

 

• Check the Main Timing is running the Timing application
  It needs to be on the Home screen or in an event. Check that the application has not crashed. 
• Make sure both PCs are on the same network
  1. Check the IP address of both timing PCs. To find your PC's IP address, right click on the Start button, and select "Run"
     
  2. Type in "cmd" and the click "OK"
     
  3. In the new window that opens, type in "ipconfig" and press enter
     
     In the information that follows you will find all of the IP address that are configured for your Timing PC. Look for the one labelled IPv4 Address:
     
     The first three parts of both timing PC's IPv4 address need to match i.e. 192.168.1.67 and 192.168.1.68 match - the last digit must always be unique for every devices that is on that network.
     
     If the do not match i.e. 192.168.1.67 and 192.168.10.10 they won't be able to connect. This is known as a subnet mismatch.
     
     

Note: It is quite possible that your PC may have two or more IPv4 address if the device has several network connections i.e. a Wi-Fi connection or a direct cable to decoder connection. 

• Check both PCs are able to see and speak to each other effectively. This is known as "Ping". 
  1. To ping a device on the network, right click on the Start button, and select "Run"
  2. Type in "cmd" and the click "OK"
     
  3. In the new window that opens, type in "ping" followed by the IP address of the other PC and press enter. 
     
     This test will send 4 pieces of test data to the other device and test the speed and reliability of the connection:
     
     The results from this test is excellent. All data was able to be sent and received, none was lost and it took on average 34 milliseconds to send and receive.  
     
     

     
     The results from this test is intermittent. Half of the data was able to be sent and received, but half was lost and it took on average 607 milliseconds to send and receive.

     
     
     The results from this test show the device is unable to be detected on the network.
     
     
• Check that the windows network profile is set to Private. 
  You need to be on a Private network on both PCs or windows will prevent them from communicating. 
  
  Right click the Start button and select "Network Connections". Select the network you are using to connect the two laptops (Windows separates Wi-Fi and Ethernet (cable) connections) and check that it is set to "Private network".