OES Client losing mapped drives when switching between wired and wireless

Windows 11 23H2 and 10 22H2.  OES Client 24.1

When sitting at their desks, users dock their laptops.  If they go to a conference room or collaboration space, they usually connect to wifi.  Wifi is typically set to connect automatically.  The docked connection and the wifi connection provide IP addresses from the same range.  Most of the time this is a seamless transition as they move back and forth between wired and wireless.  Mapped drives are always accessible and everything just works.  But I have some users that sometimes lose their mapped drives.  Drives will either come back slowly or they will need to do an OES Login to get them back after switching between wired and wireless.  Are there known issues around this?  Or are there some recommended OES Client settings that will make the transition more reliable and/or faster?


Thanks!

Ken

Parents
  • Suggested Answer

    0  

    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

  • 0 in reply to   

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

  • 0 in reply to 

    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

Reply
  • 0 in reply to 

    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

Children
  • 0   in reply to 

    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.