To eliminate unnecessary connection problems, make sure that
The source and destination servers have enough available server and workstation licenses to do the migration.
The eDirectory user that you are using to do the migration has no concurrent connection limitations. To check this, do the following:
Run iManager or ConsoleOne on the workstation.
Edit the properties of the User object.
Click the Login Restrictions tab.
Deselect the Limit Concurrent Connections option.
The eDirectory user that you are using to do the migration has the Supervisor right to the source server’s eDirectory object. Use iManager or ConsoleOne to verify that the User object is listed in the source server’s Operators list.
If you have problems establishing or maintaining connections between your servers and workstations, try one or more of the following:
Reboot the client workstation to clear the cache in the Novell Client software.
Map a drive to the server instead of logging in. This is especially useful when connecting with the IPX protocol.
Search for the server by its IP or IPX address instead of its name. Type the IP or IPX address in the Server field of the Novell Login dialog box.
Try connecting to the server and not the eDirectory tree by specifying only the name of the server and leaving the tree name and context blank.
Clear all unauthenticated connections. To do this, right-click the N icon and then click NetWare Connections. Detach from all servers and trees that you are not authenticated to, then try logging in again.
Make sure your Preferred NetWork Protocol is set correctly by doing the following:
Right-click the N icon.
Select > .
Select the desired preferred network protocol, then click .
Reboot the workstation.
Unbind the protocol you are not using from the destination server. For example, if you are using IP for the migration but IPX is bound on the destination server, unbind the IPX protocol on the destination server during the migration.
If you have problems establishing or maintaining connections between your servers, try one or more of the following:
Do not remove the source and destination servers from their respective eDirectory trees. The servers must be able to communicate with the other servers in the tree during the migration.
Make sure the destination and source servers can communicate with each other.
For IP connections, enter ping at the server console and specify the other server’s IP address. For IPX connections, enter display servers at the server console.
For IP connections, verify that you have corresponding addressing, subnet mask, and gateway information. If you are using IPX, make sure the frame type and the IPX network number/server ID are consistent between the source and destination servers.
Reboot the destination server.