Microsoft Surface Pro running Win 8.1
Novell Client 2 SP3 for Windows (IR7a)
OES 11 SP1
The Novell Client works fine until the device goes to sleep and wakes up. After the wake-up, all drives are disconnected. User can Ping the server, but any attempt to login or map drives will return the "tree or server not found" message. Attempting to access previously mapped drives gives the error " path not available, network path not found."
Disconnect and reconnect the network interface.
Apparently, Microsoft has corrected the driver issue that caused the bug in earlier iterations of Surface Pro, but the fix is still pending for the Surface Pro 4.
The Novell Client reacts to a "the network card is being powered down" event, instead of waiting for Windows to notify us of IPv4 network addresses being activated or removed in order to more robustly handle cases where the machine is shutting down. Typically, only the power event occurs and no Windows IPv4 address removal notification, so we use the power event to remove the existing NCP connections.
Typically, a Windows machine (and network adapter) being un-suspended or powered on causes a IPv4 network address event to occur when Windows verifies what network it's still connected to and uses DHCP to renew/confirm it's lease, etc. This network address activation event occurs when the machine is woken up.
Evidence from debug logs taken on a Surface Pro shows that there is not any kind of "IPv4 address activation" event occurring when the machine has been woken up. The Novell Client is still in the state where the power event has caused us to think the network interface is down, and we're waiting for Windows to notify us that an IPv4 address has been re-activated / learned for the network adapter once it's powered back on. But presumably Windows is thinking "no, we're still good, I never told you the IPv4 address went down."