Troubleshooting - Yamaha DRCX User Manual

CHAPTER2 Ethernet Unit
2-13
Symptom
No.
1 Cannot make
TELNET
connection.
(Using "ping"
only results in
a timeout.)
1)
2)
3)
4)
5)
6)

Troubleshooting

When problems occur, then troubleshoot as needed by using the following information
as a guide. Be sure to always also refer to sections on "Troubleshooting" in the controller
user's manual as well as the instruction manual for the other party's equipment such as
PCs or HUB peripheral devices. If taking the troubleshooting steps listed there does not
eliminate the problem, then quickly contact your local YAMAHA sales dealer.
Probable causes
• Disconnect the controller from the
network and connect the PC instead.
(Use a PC capable of a good
connection with the network. Make the
same IP address, subnet mask and
gateway settings as used on the
controller.)
Now try running "ping" from the client
while setup as above, and check for a
response.
Ethernet cable • Check if securely attached to the
defects, poor modular connector.
connection, or
• Check for a disconnection (or break) in
wrong specs. the cable or a miswire.
• Check if the straight-through cable or
crossover cable are being used for the
wrong connection.
• Try replacing the cables.
Defective HUB • Try changing to another port.
or wrong settings
• Check if the communication mode is
manually set to other than 10Mbps/Half
Duplex.
• Try another HUB
Router is
• Check the router settings.
defective or • Try substituting with another router.
wrong settings
Network adapter
• Check the network settings on the
used by the client client side.
is defective or the • Try substituting with another network
settings on the
adapter on the client side.
client side are
wrong.
Network traffic • Check if the traffic load is appropriate.
(communication
data load) is too
heavy.
Ethernet cable is • Check how and where the Ethernet
too close to a
cables are installed.
noise source such
as motor cables.
Checkpoints
32
Action
• If timeouts still occur when connected
this way (using PC instead of
controller), then the problem is on the
client side or in the HUB peripheral
device. (Check probable causes 1
through 6.)
• If a replay comes back normally, then
the problem is in the controller, so
check probable causes 7 through 8.
• Insert in firmly until a click noise is
heard.
• Correct the wiring if a miswire is
found. Replace the cable if a break in
the wiring is found.
• Use a straight-through cable between
the HUB and controller. Use a
crossover cable if connecting directly
to the other party's device.
• If operation returns to normal, then the
problem is in the cables. Replace the
cable.
• If operation returns to normal then the
port is defective, so do not use that
port.
• When setting the HUB communication
mode manually, then set it to
10Mbps/Half Duplex.
• If operation returns to normal then the
HUB is defective, so replace the HUB.
• Redo the router settings.
• If operation returns to normal then the
router is defective so replace the
router.
• Redo the network settings on the client
side.
• If operation returns to normal then the
network adapter is defective so replace
the adapter.
• Change the network structure to get a
smaller traffic load.
• Separate the Ethernet cable from
potential noise sources.