When Windows network settings affect Thin Client installations
Important Notice for Thin Client Installations
This article explains a common Windows networking behavior that can impact Thin Client installations and outlines general areas that IT professionals may review when addressing it.
Rossware Support Scope
Rossware does not perform or provide guidance for:
- Editing the Windows registry
- Changing network adapter (NIC) hardware or power settings
- Modifying Windows network security or sharing configurations
Because these changes affect system-level behavior, Rossware recommends working with a qualified IT professional or managed service provider.
Additional information can be found here.
Why this issue can occur
Some customers report that after a Windows Update or a restart of the computer, their computer’s network changes from Private to Public.
In Microsoft Windows, this setting determines how the system treats the network:
- Private network → Trusted (allows file sharing)
- Public network → Untrusted (restricts sharing and access)
When a network is set to Public, Windows applies stricter security rules that may block access to shared files.
Common symptoms you may notice
If this issue occurs, you may experience:
- Mapped network drives disconnecting
- Errors such as “Path not found” or “Cannot access network location”
- ServiceDesk unable to open or locate shared data
- Intermittent access that works until the next restart
Note: This is a known Windows behavior and is not typically caused by ServiceDesk itself.
Why this matters for Thin Client installations
Thin Client setups rely on consistent access to shared data across the network.
If Windows switches the network to Public:
- File sharing may be restricted
- Network discovery may be disabled
- Applications like ServiceDesk may lose access to required data
Why Windows may change the Network Type
Windows uses a feature called Network Location Awareness (NLA) to classify networks.
Microsoft Documentation:
NLA evaluates factors such as:
- Network identification
- Hardware state during startup
- Network response timing
After updates or restarts, changes in these factors can cause Windows to reclassify a network as Public instead of Private.
How IT Professionals typically approach this
When this issue happens repeatedly, IT professionals may review:
1. Network Profile Behavior
How Windows is identifying and storing the network classification.
2. Network Adapter Behavior
- Driver initialization timing
- Power management settings
- Hardware communication during startup
3. System Updates and Changes
Recent updates or system changes that may affect how the network is detected.
Rossware recommendation
If ServiceDesk loses access to shared data after a reboot or update:
- The issue is often related to Windows network classification
- This behavior occurs at the operating system level
Rossware recommends contacting a qualified IT professional to review:
- Network profile settings
- File sharing configuration
- Network adapter behavior
Additional resources
Change network profile in Windows:
Network Location Awareness (Microsoft):
File sharing troubleshooting (Microsoft):