Debugging TCP/IP connections to broadcast devices.
This note describes the first steps in verifying network connection to a device. If you have trouble getting Rascular software to connect to a device, please try the following steps.
STEP #1: "pinging" a device.
Using Windows: Start/All Programs/Accessories/Command Prompt:
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
"ping" the device as shown below:-
You should see something like this, if it's working:-
Reply from 192.168.0.6: bytes=32 time<1ms TTL=128
Reply from 192.168.0.6: bytes=32 time<1ms TTL=128
Reply from 192.168.0.6: bytes=32 time<1ms TTL=128
Reply from 192.168.0.6: bytes=32 time<1ms TTL=128
Ping statistics for 192.168.0.6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
If it fails, you'll see something ike this.
Reply from 192.168.0.16: Destination host unreachable.
Reply from 192.168.0.16: Destination host unreachable.
Reply from 192.168.0.16: Destination host unreachable.
Reply from 192.168.0.16: Destination host unreachable.
Ping statistics for 192.168.0.32:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
This indicates a fundamental problem with TCP/IP connectivity to the device.
Things to check:-
- Has a network cable or router failed or been removed/switched off?
- Is the device switched on and running?
- Are the PC and device both on the same subnet (e.g. 192.168.0, in the case above),
- (or, if not, is TCP/IP routing configured correctly to enable communications - ask your IT department)
STEP#2: Access to specific port.
DO NOT BOTHER TO TRY STEP #2 UNTIL STEP #1 IS CORRECT!
Using windows command prompt, attempt to 'telnet' to a specific port.
The port number will vary according to the device - but for Imagestores, it is 5006
If it fails, you'll see (after a long delay) a message like this.
Things to check:-
- Is the device correctly configured to accept connections? (consult the device vendor for details)
- Is your firewall software preventing the connection?
- Does you device have the necessary licence from the vendor to accept connections?
- Have you tried rebooting the device?
- Are there other systems connecting to the device via this port (some devices may limit the number of simultaneous connections)
- Did step #1 above really work? Try it again...
If both #1 and #2 pass, then contact Rascular for further help. send all available details (software/firmware versions), and - if using HELM - enclose a copy of panel file.