<div>
I do not have any issue with Windows 10 disconnecting from servers. <br />
<br />
For disconnects: Make sure your default Power Profile is NOT airplane mode. Check to a different default.<br />
<br />
For default viewers: &nbsp;Go to Settings, System/Notifications and set Default Apps to the ones you want. I use IE (not Edge), Standard Photo View. &nbsp;It is a personal choice, so set what you wish.
</div>


<div>
I can't seem to pinpoint what is causing the issue but something in our environment is causing an issue with Windows 10 machines.<br />
There is no airplane mode power plan that I can see but regardless, that would only affect wireless communication and these PCs are using network cables.<br />
<br />
I know how to set the defaults for each file type; the issue is that Windows 10 just sets it back (even when I tell it to use the new program as the default moving forward). &nbsp;It doesn't necessarily happen right away but I've seen it happen right in front of my eyes. &nbsp;I had a user this morning contact me because he was getting an error when attempting to open a JPG. It was defaulting to the W10 &quot;Photos&quot; app and for some reason that app wouldn't open on his PC.<br />
I had to modify the registry so that the older Windows Photo Viewer would show up as an option (this is a fresh W10 install and apparently they hid the old Photo Viewer app). When I right-clicked on the jpeg and chose the old Windows Photo Viewer as the default app for viewing JPEGs moving forward, I watched as all of the PDFs icons on his Desktop changed from the PDF app he was using, back to Edge. There was no reason for this. We made the change to JPEGs; why would W10 reset the default PDF app???? It doesn't make any sense.
</div>


<div>
Make sure in device manager that the network card cannot be turned off. I ensure power management is not turning anything off. I have been using Windows 10 for more than 6 months and no issues. <br />
<br />
With respect to defaults, ALL standard defaults in Windows 10 are different from Windows 7. <br />
<br />
If you upgraded from Windows 7, that is a bad base to upgrade from .<br />
<br />
Take one machine, do a fresh install of Windows 10, upgrade BIOS, chipset and drivers and test connectivity before loading software
</div>


<div>
Double check the DNS. &nbsp;I have noticed as we deploy windows 10, that during updates, it will wipe the DNS settings, causing some users to lose access.
</div>


<div>
What exactly would you like me to check regarding DNS?<br />
I'm not sure what you mean by that.
</div>


<div>
<div class="content wysiwyg-content">
Hi all.<br />
Domain environment across 3 subnets.<br />
2 DCs in each branch running Server 2008 R2.<br />
File servers in main branch are running Server 2008 R2.<br />
As I'm starting to upgrade users to Windows 10, I'm starting to see some frustrating issues.<br />
The one with the most potential for headaches seems to be users getting disconnected for what seems like no reason at all.<br />
You can have Windows Explorer open to S:\Test\Temp and open a PDF; next thing you know you minimize the PDF and see an error saying you were disconnected from the network drive.<br />
Has anyone experienced this?<br />
We have Exchange 2007 running Server 2003 R2 and don't see any issues so far with W10 users being disconnected from Outlook or anything like that.<br />
While the issue doesn't seem to be related to any particular amount of time, I suppose it is a possibility that there is some type of network time out going on.<br />
Very frustrating...that along with Windows 10 CONSTANTLY changing the default viewers/programs back to what Windows 10 <u>thinks</u> it should be (Ex: Edge to open PDFs, Photos to open images, etc) but that's a topic for another day.
</div>
</div>


Hi all.
Domain environment across 3 subnets.
2 DCs in each branch running Server 2008 R2.
File servers in main branch are running Server 2008 R2.
As I'm starting to upgrade users to Windows 10, I'm starting to see some frustrating issues.
The one with the most potential for headaches seems to be users getting disconnected for what seems like no reason at all.
You can have Windows Explorer open to S:\Test\Temp and open a PDF; next thing you know you minimize the PDF and see an error saying you were disconnected from the network drive.
Has anyone experienced this?
We have Exchange 2007 running Server 2003 R2 and don't see any issues so far with W10 users being disconnected from Outlook or anything like that.
While the issue doesn't seem to be related to any particular amount of time, I suppose it is a possibility that there is some type of network time out going on.
Very frustrating...that along with Windows 10 CONSTANTLY changing the default viewers/programs back to what Windows 10 thinks it should be (Ex: Edge to open PDFs, Photos to open images, etc) but that's a topic for another day.

Windows 10 Users Being Disconnected from Server 2008 R2 Network Shares

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.

Windows Server 2008

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.