Windows 10: Windows 10 Pro - backup to NAS part of DOMAIN

Environment:Home Domain Controller - Server 2019Multiple Windows 10 computers - all fully updated to 21H2NAS: TrueNAS 10.0-U7 joined to the DomainProblem:I have the DC backing up to the NAS no problems at all...using an AD account - and password. This was easily setup after the proper ACL was set on the NAS to allow this account access to the SMB share it uses SMB v2/v3 Did not have to enable SMB v1 on the DC to allow backups. The issue is with the Windows 10 machines - none of them will back to the SAME location on the NAS. I am able to MAP a drive to the NAS folder with no issues f

:)

 

Windows 10 - NAS Drive

Hi,

We appreciate you for being a part of Windows 10.

We need more information to help you better.

• 
  Is the system connected to domain network?
  
• 
  Have you updated the network drivers in your computer?
  

Reference: Meanwhile, I suggest you to refer to the suggestions provided by the
Smithhead9 on May 7, 2015 and check if it helps.

http://answers.microsoft.com/en-us/...echnical/2e7dd6fb-5dd9-49f1-a46f-915a174432b9

Kindly let us know if you need any further assistance with the issue. We are glad to assist you.

Thank you.

 

Access Non-Domain NAS on a Domain PC

How in the world can I connect a Non-Domain NAS to a Domain PC running Windows 10 Enterprise 64-Bit.

First attempt it neither showed up on PC or on my Phone (Android 8 Custom Rom). Second attempt, the day after it worked and showed up on my Phone, but on my PC it only shows up, but it doesnt work. When I try to connect it just prompts with Username and
Password but it doesnt matter if enter PC Username and Password or NAS Username or Password. Changing Domain by writing domain\username in username field does not work either. Tried with both PC Name and NAS Name. It wont let me access.

Anyone got a clue of whats going on?

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW