Windows 10: Windows 10 Issue with Domain share folder

Hi to all.Today I noticed some strange behavior in windows 10One user try to access a share folder in our DC server.For many years in windows 7 we use //xxx.xxx.xxx.xxx and we are able to see and open the share folders.Me try the same in windows 10. We are able to see the share folders but when the user try to open one they get permission denided and ask for user name and passwordWe don't face similar issue if instead of IP we use the name of the server.Why we face this issue?Thanks and regards.

:)

 

?? How do I PW protect Folders in windows

hmmm?
Sharing files and folders overview You can share the files and folders stored on your computer, on a network, and on the Web. The method you choose depends on whom you want to share files with, and what computer they will use to access the files.

When you share files or folders, they are not as protected as they are when you do not share them. People with access to your computer or your network might be able to read, copy, or change files that are in a shared folder. You should always be aware that the files and folders that you share are available to other people and be sure to monitor your shared files and folders on a regular basis.

Important

If your computer is not joined to a domain, you can use the Network Setup Wizard to automatically turn file and printer sharing on or off. To start the Network Setup Wizard, click Start, click Control Panel, click Network and Internet Connections, and then click Network Setup Wizard.
If you both use the same computer

You can put the files you want to share in the Shared Documents folder. Files stored in the Shared Documents folder or its subfolders are always available to other users on your computer.

Step-by-step procedure
Note

If you are connected to a network domain, the Shared Documents, Shared Pictures, and Shared Music folders are not available.
If both computers are on the same network

You can share a folder or drive on your computer with others on the network. You can also control whether the files in the shared folder can be modified by other users.

If your computer is connected to a network domain, use this procedure:

Step-by-step procedure
If your computer is connected to a workgroup, use this procedure:

Step-by-step procedure
Note

If you are connected to a network domain, you will need to set the Access control for the folder or drive after sharing it. For more information, go to To set, view, change, or remove file and folder permissions.
If you want to share your files online

You can publish pictures and documents on the Web using the Web Publishing Wizard. The files will be stored in a private, online folder that you manage.

Step-by-step procedure

If you don't want others to access your files

You can prevent other users from accessing your folders and the files they contain. When your computer is connected to a domain, this is called setting permissions for your file or folder. When your computer is connected to a workgroup, this is called making your folders private.

If your computer is connected to a network domain, use this procedure:

Step-by-step procedure
If your computer is connected to a workgroup, use this procedure:

Step-by-step procedure

'HELP' it can be your friend *Smile

 

How to stop sharing folder for windows 10?

Referring to following link, I would like to know on how to stop sharing folder for windows 10.

I cannot find Stop Sharing option on step 5.

Use these steps to stop sharing any folder on Windows 10:

1. Open Start.
   
2. Search for Computer Management and click the top result to open the experience.
   
3. Expand the Shared Folders branch from the left pane.
   
4. Click the Shares item.
   
5. Right-click the folder that you no longer want to share and the Stop Sharing option.
   

Furthermore, ADMIN$ is found to be Remote Admin under computer management.

There is no option to stop it as well.

Does anyone have any suggestions on how to stop sharing and remote?

Thanks in advance for any suggestions

How to stop sharing network folder on Windows 10 - Pureinfotech

 

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