Errors When Connecting to a NetWare 4 Server

Problem:  When attempting to connect to a NetWare 4 server, any of the following types of errors are returned:

• An error occurred opening the file. filename was invalid.
• Error opening connection to SMDR.
• The name spaces couldn't be checked.
• 8998 error. NWGetVolumeNumber.

Action:  There are several actions to take if errors are returned when trying to connect to a NetWare 4 server, including the following:

• If your source server is NetWare 4, make sure that you have IPX^TM on your client. For information on verifying IPX on your client, see Verifying IPX is Bound On the Client.
• Add a mapped drive to the source server.
• Ensure that SLP is configured properly on the servers involved in the consolidation project.

Problem:  NetWare 6.5 won't communicate with NetWare 4 during a consolidation. IPX was not installed during the NetWare 6.5 installation.

Action:  Add IPX to the NetWare 6.5 server after the NetWare 6.5 installation is complete.

1. Enter edit at the NetWare 6.5 server console.

2. Press the Insert key.

3. Select sys: and press Enter.

4. Select System and press Enter.

5. Select autoexec.ncf and press Enter > Enter.

6. Add the server ID of the source server and save the autoexec.ncf file.

Problem:  IPX connection is not communicating.

Action:  Ensure that there is an IPX connection to the server.

To verify that the source and destination servers can see each other via IPX:

1. On the server console of the destination server, enter serverid xxxxx, where xxxxx is the unique server ID number for the server.

2. Enter load ipxping.

3. Enter the internal IPX number of the source server.

4. Repeat this process on the source server, replacing the internal IPX number of the source server with the destination server's internal IPX number in Step 3.

Action:  Bind IPX on the destination server.

1. At the destination server console, enter inetcfg.

2. Select Boards and press Enter.

3. Press the Insert key.

4. Select the appropriate network interface and press Enter.

5. Enter a board name and slot number, then press the Esc key.

6. Select Yes to save changes and press Enter.

7. Press the Esc key to return to the main Internetworking Configuration screen.

8. Select Protocols and press Enter.

9. Select IPX and press Enter.

10. Enable and configure IPX and exit the inetcfg utility.

HINT:  If you prefer, IPX can also be enabled on the server by adding the appropriate Load and Bind commands to the server's autoexec.ncf file.

Action:  Verify that IPX is bound on the client running the Server Consolidation Utility:

1. Right-click on the red N in the system tray on your workstation.

2. Select Novell Client Properties.

3. Select the Protocol Preferences tab.

   If the Protocol window displays both IP and IPX, the client has IPX bound.

   If the Protocol window displays only IP, then IPX needs to be bound on the workstation.

Action:  Bind IPX on the client running the Server Consolidation Utility:

1. Insert the Novell Clients Software CD (March 2003).

2. Select the client version you want and click Next.

3. Select the appropriate language and click Next.

4. Select Custom and click Next.

5. Click the radio button next to one of the following two choices:

   • IP and IPX
   • IP with IPX compatibility

     HINT:  You can select this choice if you are running in an scmd environment.

6. Click Next > Next > Finish.

Action:  Ensure that the correct smdr.nlm and tsa.nlm are loaded on the server.

1. On the server console, enter unload smdr.

2. Enter smdr new.

3. Enter N when asked if you want to disable NDS.

4. Enter N when asked if you want to disable SLP.

5. Enter N when asked if you want to disable SAP.

6. Enter N when asked if you want to disable name resolution through sys:\etc\hosts file.

7. Enter load smdr on the server console.

8. Enter load tsa600 on the server console.