Intermec CV30 Data Collection Browser Client User's Guide - Page 98

Symptoms and Solutions, Appendix B - Troubleshooting, Data Collection Browser Client User's Guide

Get Intermec CV30 PDF manuals and user guides View all Intermec CV30 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 98 highlights

Appendix B - Troubleshooting Symptoms and Solutions If you have problems running dcBrowser in your data collection network, look for your symptom in the table below, and then try the solutions in the order that they are listed. If your problem is not listed in the table, you can look at the diagnostics or refer to the Product Support web page. Symptoms and Solutions Symptom Solution From your device, you cannot connect to the Intermec Application Server. View the current connections to be sure that you have a connection configured between the dcBrowser client and the dcBrowser gateway. Ping the Intermec Application Server. Make sure that you have configured the network port on the device to 4055 for TCP/IP or 05555 for UDP Plus. Make sure that you have correctly configured your RF network parameters on the device, access point, and Intermec Application Server. On the DCS 30X, access the command prompt. Ping the device IP address. If you are using a UDP Plus or WTP terminal, check your configurations and correct if necessary. From your PC, you cannot connect to the Intermec Application Server. You may access the Internet by using a proxy server. Make sure that you have added the Intermec Application Server IP address to your Exceptions list. After you reboot the Intermec Application Server, the response time between the device and the web server is slower than expected. You can continue to send data from the device. The network will speed up in about 30 minutes. Stop the dcBrowser gateway. Start the dcBrowser gateway and then turn on ONE device. When the device's home page appears, then you can turn on the other devices. UDP Plus device continually reboots. Verify that dcBrowser gateway is running. Verify that the downline network is running. Verify that the device is configured in downline connections. Verify port number. The dcBrowser gateway starts and then stops. The dcBrowser gateway is already running as a service on the PC. Close one copy of the gateway. You start the dcBrowser client for Use the PING command from the PC to verify that the the device and "Thin client device's radio is configured properly. for dcBrowser" is not Verify that the dcBrowser gateway is running. replaced by the device's web page. You start the dcBrowser client for Verify that the web page is configured for the device. the device and "Thin client Verify that the Intermec Application Server is configured for dcBrowser" is replaced properly. After you change the Intermec Application by an error message. Server configuration, you must save and reboot. For help, see the Intermec Application Server online help. Verify that your web server is running. Verify that the host IP address has :80 at the end of it in the dcBrowser gateway configuration page. 86 Data Collection Browser Client User's Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
Appendix B — Troubleshooting
86
Data Collection Browser Client User’s Guide
Symptoms and Solutions
If you have problems running dcBrowser in your data collection network, look for
your symptom in the table below, and then try the solutions in the order that they
are listed. If your problem is not listed in the table, you can look at the diagnostics or
refer to the Product Support web page.
Symptoms and Solutions
Symptom
Solution
From your device, you cannot
connect to the Intermec
Application Server.
View the current connections to be sure that you have a
connection configured between the dcBrowser client and
the dcBrowser gateway. Ping the Intermec Application
Server.
Make sure that you have configured the network port on
the device to 4055 for TCP/IP or 05555 for UDP Plus.
Make sure that you have correctly configured your RF
network parameters on the device, access point, and
Intermec Application Server.
On the DCS 30X, access the command prompt. Ping the
device IP address.
If you are using a UDP Plus or WTP terminal, check your
configurations and correct if necessary.
From your PC, you cannot
connect to the Intermec
Application Server.
You may access the Internet by using a proxy server.
Make sure that you have added the Intermec Application
Server IP address to your Exceptions list.
After you reboot the Intermec
Application Server, the response
time between the device and the
web server is slower than
expected.
You can continue to send data from the device. The
network will speed up in about 30 minutes.
Stop the dcBrowser gateway. Start the dcBrowser
gateway and then turn on ONE device. When the device’s
home page appears, then you can turn on the other
devices.
UDP Plus device continually
reboots.
Verify that dcBrowser gateway is running.
Verify that the downline network is running.
Verify that the device is configured in downline
connections.
Verify port number.
The dcBrowser gateway starts
and then stops.
The dcBrowser gateway is already running as a service on
the PC. Close one copy of the gateway.
You start the dcBrowser client for
the device and
“Thin client
for dcBrowser”
is not
replaced by the device’s web page.
Use the
PING
command from the PC to verify that the
device’s radio is configured properly.
Verify that the dcBrowser gateway is running.
You start the dcBrowser client for
the device and
“Thin client
for dcBrowser”
is replaced
by an error message.
Verify that the web page is configured for the device.
Verify that the Intermec Application Server is configured
properly. After you change the Intermec Application
Server configuration, you must save and reboot. For
help, see the Intermec Application Server online help.
Verify that your web server is running.
Verify that the host IP address has :80 at the end of it in
the dcBrowser gateway configuration page.