Windows 10: Windows 10 File Shares not accessible from Server 2012

We have a newly imaged Windows 10 box that we will be using as an SCCM DP. Currently the Central server cannot access the file shares on the Windows 10 box, after digging deeper we have found that other Windows 10 boxes can hit file shares on it, but Server 2012 R2 systems can not. I have listed the configurations and work we have done below.


Configuration -
Servers:
• Location 1
o SCCM-Central1-loc1
 Windows 2012 R2
 10.70.4.228/24
• Location 2
o SCCM-DP1-loc2
 Windows 10 Build 1803
 172.22.65.4/24
 No Symantec Endpoint Protection
o FILESERVER-FS1-loc2
 Windows 2012 R2

 172.22.65.231/24
• Location 3
o SCCM-DP2-loc3
 Windows 10 Build 1803
 172.22.186.4/24
 Symantec Endpoint Protection
• Location 4
o SCCM-DP3-loc4 (Tega)
 Windows 10 Build 1803
 172.22.207.4
 Symantec Endpoint Protection
 Citrix Receiver
• Location 5
o SCCM-DP4-loc5 (PTZA)
 Windows 10 Build 1803
 172.22.185.4
 Symantec Endpoint Protection
 Citrix Receiver

• We need to be able to attach to the f$ share on each of the “SCCM-DPx-LOCx” servers from the “SCCM-Central1-loc1”.
o Issue Attempting to connect to
 \\172.22.65.4\f$
 \\ SCCM-DP1-loc2\f$
 \\ SCCM-DP1-loc2.DOMAIN.com\f

:)

 

Server 2012

IF you want to try seizing the FSMO roles to see if it will help, here is a quick guide (this should be done on the DC you want to keep):

https://blogs.technet.microsoft.com...ation-master-roles-in-windows-server-2012-r2/

Knowing that this is a DC now I'm really convinced that something is wrong with the AD account for this particular server. It's possible that the promotion to a DC didn't work correctly leaving you with a sort of broken DC.

A reboot is always worth a shot; has that been tried Ahhzz? If it has, then the next step would be to demote this DC and rejoin it to the domain. Once rejoined you can run DCPromo again. Microsoft best practice is to have at least 2 DCs for redundancy.

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

Cannot file shared to windows server 2003 using windows 10 build 1703

Hi Rose,

• Did you get any error messages when you try share file? Yes,i got error windows cannot access \\192.168.1.15\public (error code : 0x80004005)
• Does this happen to all files you want to share or to just specific file only? this happen when i use windows 10 and some windows 7. (but the older computer can access file in windows server 2003).
• What troubleshooting steps have you done so far? I have check connection with LAN cable working, ping with ip and name server to server it working to.

any solution for this error?

Thank You.

Regards,