Have you checked the Windows Network Profile eventlog on the affected machines. The nlasvc (only Win10) and netprofm services can be a big pain on some systems. If Windows does not like the network adapter or the switch/accesspoint or the combination of both the network identification can take quite a while. I have machines, where it takes from 2 to 7 minutes, till network identification has finished.

And some of those things you can try to resolve, but there remains an unknowm multitude of things, which cannot be changed, where you get that problems. It is especially a problem with machines in a domain, because you cannot set the network profile for domain connections manually. (And as the domain in question is a DSfW domain, you don't get any support from Microsoft).

If you have such long network identification times, all network connections time out and you have to relogin. If you have a permanent drive mapping, this should autumatically resolve as network connectivity is back via a seamless relogin, if that is enabled at the OES Client properties.

This would be my first suspicion, if you have issues, when switching adapters.

Hi Ken

Sometimes adapter goes down and windows notify the oes client driver but when it comes online again, it does not communicate to oes client driver so oes client things it is still down. Try to change this settings:

- Set DWORD "HKLM\SOFTWARE\Novell\Client\Parameters\NetworkAdapterPowerEventHandling" to 0 in registry.

- Allow the computer to turn off this device to save power setting is disable on the network card

- Increase the value of the "Server Connection Retries" setting. Find the setting by navigating to:

OES client Blue icon > Novell Client Properties > Advanced Login tab > Server Connection Retries

Thanks Gonzalo.  I will give that a try and see what happens.

Gonzalo,

I think that is helping, but I need to do more testing.  However, I have discovered something more.  If a user disconnects from the wired connection and their laptop goes to the WiFi connection, and the drives disconnect, they can take the following steps to get them back.

1. Open Windows Explorer and select This PC.

2. Instead of selecting the drives in the list immediately below This PC, double-click a drive in the main pane under Network locations.,

Doing this makes everything work again.  I don't know why this works, but so far my minimal testing shows that it does.  Any thoughts on what we can do to make this work on its own without people having to open Windows Explorer?

Ken

Not going to spoil your hopes, but this works sometimes, but not always. Truth to be told is, that the OES Client can't properly deal with network disconnects. There is a bug in it somewhere for *at least* a decdae, if not longer.
It *will* eventually fail, no matter what you do. It will survive the PC going to sleep a dozen times, but eventually it won't reconnect when you wake it up again, and the only cure possible will be a reboot. You will not be able to re-login (or logout).
The same with "real" disconnects or network changes, like switching between wired and wireless network. It may or will work every so often, but it will eventually break.