Environment
Novell Cluster Services
Novell Open Enterprise Server 2 (OES 2) Linux
Novell Open Enterprise Server 2 (OES 2) Linux
Situation
End users were accessing data on the cluster resource most of the day. Late in the day, they reported that the drive mapping was "not working". The clustered volume was online and would migrate to any cluster node without a problem. However, trying to map to a drive would error out. For example:
C:\DOCUME~1\User1>net use k: \\10.20.30.40\users
System error 67 has occurred.
Additionally, a packet trace shows a request from the workstation to the server and the server immediately sends a reset packet [rst,ack].
C:\DOCUME~1\User1>net use k: \\10.20.30.40\users
System error 67 has occurred.
Additionally, a packet trace shows a request from the workstation to the server and the server immediately sends a reset packet [rst,ack].
Resolution
The following were missing in the load & unload scripts:
load script:
exit_on_error ncpcon bind --ncpservername=ClsSvr --ipaddress=10.20.30.40
unload script:
ignore_error ncpcon unbind --ncpservername=ClsSvr --ipaddress=10.20.30.40
Adding the above lines via iManager, and offlining and onlining the resource fixed the issue.
load script:
exit_on_error ncpcon bind --ncpservername=ClsSvr --ipaddress=10.20.30.40
unload script:
ignore_error ncpcon unbind --ncpservername=ClsSvr --ipaddress=10.20.30.40
Adding the above lines via iManager, and offlining and onlining the resource fixed the issue.
Additional Information
Since the clustered volume was able to be accessed earlier in the day, it is likely that someone modified the load/unload scripts since the last mount time. For further information, please see Cluster Services Documentation - Configurating a Load Script for the Shared NSS Pool