Optimizing the NetWare Client Software
Improving Security
Troubleshooting NCP Packet Signature
This section describes some solutions to problems that might be associated with using NCP packet signature.
Client Workstations Are Not Signing Packets
Problem | Client workstations are not signing NCP packets. |
|
|
Solution | The SECURITY.VLM file is not loading. Ensure the signature |
| level on the client workstation is not set to 0. |
| SECURITY.VLM loads by default when the client signature |
| level is set to 1, 2 or 3. |
| Use the VLM /V4 command line parameter when |
| loading the VLM software to display load time |
| information. |
|
|
Client Workstations Cannot Log In | |
|
|
Problem | Client workstations cannot log in. |
|
|
Solution | Make sure the packet signature levels on the server and the |
| client workstation are correct. See “Effective Packet Signature |
| Levels”. |
| Note that the following situations do not allow logging in: |
| • Server packet signature = 3, client workstation signature = 0 |
| • Server packet signature = 0, client workstation signature = 3 |
| • The LOGIN utility is an older version that doesn’t support |
| packet signature |
| • The NetWare DOS Requester or the shell is an older version |
| that doesn’t support packet signature |
|
|