Sometimes the SMDR 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:
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 Migration Wizard can’t load the appropriate tsa.nlm on your destination server, manually load it from the destination server console and following the on-screen 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 SMS problems.
Make sure the latest NLM programs are loaded on your servers.
Migration Wizard automatically copies the required NLM programs to the source and destination servers. To verify that you have the latest NLM programs loaded, check the files in the NetWare Migration Wizard\products\nw3x directory. You might need to load TSA312 manually.
Check your primary connections. Right-click the N icon, then select . Make sure the destination tree and server are marked as Primary.
Reboot the source server.