Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Suggested Answer
  • Replies replies
    5
  • Answers answer
    1
  • Subscribers subscribers
    25
  • Views views
    292
  • Users 0 members are here
Related
Options

OES Client losing mapped drives when switching between wired and wireless

Ken Etter

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
  • 0

    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.

Reply
  • 0

    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.

Children
No Data

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.