Sometimes the SMDR.NLM program that is running on the destination server can't make a connection to the source server. To correct this problem, try one or more of the following:
- Reboot the source server.
- Unbind the protocol you are not using from the destination server. For example, if you are using IPX for the migration, but IP is bound on the destination server, unbind the IP protocol on the destination server during the migration.
- If Migration Wizard can't load the appropriate TSA.NLM on your destination server, manually load it from the destination server console and following the onscreen instructions. Or, enter SMDR NEW at the server console to re-create the SMDR object.
- Load SMDR.NLM at the destination server console and then enter SMDR NEW at the destination server console to solve SMSTM problems.
- Make sure the latest NLMTM programs are loaded.
Migration Wizard automatically copies the required NLMs to the source and destination servers. To verify that you have the latest NLMs loaded, check the files in the NetWare Migration Wizard\Products\NW3x directory. You might have to load TSA312 manually.
- Check your primary connections. Right-click the N icon in the system tray and click NetWare Connections. Make sure the destination tree and server are marked as "primary."
- If you are migrating from NetWare 3, make sure the bindery context is set on the destination server. If you are migrating to NetWare 6, enter set bindery context = o=[context] on the destination server console.
