AKD User Guide | 4 Connecting the Drive
4.1 Connected and Disconnected States
WorkBench always starts disconnected from any drives. The Disconnected view opens when you start Work-
Bench and offers two choices:
l Connect: Opens the Connect to a Drive view.
l Delete: Opens a list of available drives and allows you to delete a drive from WorkBench.
While WorkBench is trying to establish communications with the drive, WorkBench is in the connecting state.
Normally, WorkBench will be in the connecting state for a few moments before the connection is established. If
WorkBench cannot establish communications correctly, then a five second timeout occurs and WorkBench
returns to the disconnected state.
4.2 Disconnected
When WorkBench is disconnected from a drive, no communication exists between your PCand the drive.
The drive becomes disconnected because of one of the following conditions:
l When WorkBench starts it remembers which drives you were using previously but it does
not initially connect to these drives.
l If WorkBench detects that it can no longer communicate with the drive, it will automatically
go to this disconnected state. Common causes include a network cable being disconnected
or the drive being turned off.
l You pressed the disconnect command.
To restore communication:
1. Clicking Connect will start communication with the drive. If WorkBench cannot find the drive, it will imme-
diately return to the disconnected state.
2. Pressing select will show a window where you can select a different drive you would like to use.
3. Pressing delete will remove this drive from the navigation tree on the left hand side of the main window.
4.3 Device Not Shown
If your specific drive is not shown in the list, then WorkBench has not been able to find the drive.
Common reasons why your drive is not shown in the list include the following:
l The drive is not powered on.
l One of the network cables between your PC and the drive are not connected correctly. You can check if
the cable is connected to the drive by checking that the linkLED on the Ethernet connector is on con-
tinuously. If your PC has a linkLED, then you should check that this LEDis also continuously lit (usually,
this LED is next the RJ45 socket on your PC).
l A router on the network between your PC and the drive is blocking the drive discovery messages. Make
sure that port 5002 is not blocked by any routers or firewalls. You can enter the IP address of your drive
directly into WorkBench if a router or firewall is blocking port 5002. Often, firewalls are the cause of a
blocked connection.
l Your PC and the drive are on different subnets. Networks, especially those with many devices on them,
are split up into multiple subnets. The discovery protocol used to find drives will only work if your PC and
the drive are both on the same subnet .You can enter the IP address of the drive directly into WorkBench if
this is the case.
l The network mask defines more than 512 possible addresses. In this case, WorkBench will not ping all of
these addresses, so you must unblock discover ports or specify directly the IP address of your drive.
34 Kollmorgen | December 2010