Wireless Sensor Device Manager
Connecting to the Gateway
SKF Wireless Machine Condition Sensor
33
Service Manual
Issue: Gateway Connection Failed
It may happen that communication with the gateway is enabled but the gateway is not
connected.
Issue:
Gateway is not
connected. The red message
Gateway is not connected
does not change.
One or more of the following
items may be at fault. Check
each item to find the
problem.
•
Incorrect gateway IP Address
•
Incorrect Port Number (Remote) (default is 20004)
•
Incorrect Polling Address (must match the polling address DIP
switch setting – default is 0 with all switches in down position)
•
Gateway and PC are in different subnets
•
Gateway is faulty
•
Network cable is faulty
•
Faulty network hardware (card and/or cable)
•
Firewall security is blocking the ports used by Device Manager
Troubleshooting the Required Ports
If the Device Manager PC is able to access the gateway’s web page but Device Manager
failed to connect, a network security firewall may be blocking the ports needed by the
Device Manager software. The following ports are required by default:
•
Destination:
20004
. The gateway’s UDP server listens at port
20004
(SKF default).
You can test 20004 by connecting to the Telnet server in the gateway from the
host PC. Go to
http://social.technet.microsoft.com/wiki/contents/articles/910.enabling
to enable Telnet client in the Device Manager computer.
From the Device Manager
computer, in the DOS cmd window, enter Telnet
<Gateway IP address> 20004.
•
Source:
7000 to 7010
. Device Manager uses ports
7000
to
7010
(SKF default) to
initiate communication with the gateways in the network. Ask IT to open these
ports in the firewall.
Two ports in the Port Number Range are used for each gateway. The first port (7000) is
used by the Device Manager UI and the next port (7001) is used by the batch service to
connect with the first gateway, and so on, as shown below.