I have set up a replication group and folder between two 2012R2 servers.  Replication works fine until I reboot one of them.  Then I get Error 1202  in the Events log with this message:

The DFS Replication service failed to contact domain controller  to access configuration information. Replication is stopped. The service will try again during the next configuration polling cycle, which will occur in 60 minutes. This event can be caused by TCP/IP connectivity, firewall, Active Directory Domain Services, or DNS issues.
 
Additional Information:
Error: 160 (One or more arguments are not correct.)

I cannot tell which argument is not correct. 

I am also puzzled why I was able to set up the replication initially, and it works fine, if the two systems can't talk to the domain controller.

I am not sure there is a shutdown timeout and that I am falling in to the 'Dirty shutdown' scenario because I can't find the events 1006 or 1008 indicating DFS stopping/stopped events.  This is Windows Server 2012, so the hotfix for 2008 to change the DFS recovery should be applied.  And, this is NOT a very active folder so, I expect there is nothing replicating at the time I issue a reboot. 

And, when I try the wmic command to resume replication I get an error.

And, I get these messages after reboot.

20180806 16:09:10.500 2572 SYSM  3830 Migration::SysVolMigration::Connect [MIG] Trying to connect to Local or any writable Dc AD
20180806 16:09:10.500 2572 CFAD   311 Config::AdConnection::Connect Binding to dcAddr:\\my.dc.ip.address dcDnsName:\\my.dc.dns.name
20180806 16:09:10.500 2572 CFAD   143 Config::AdConnection::BindToAd Trying to connect. hostName:my.dc.dns.name
20180806 16:09:10.500 2572 CFAD   162 Config::AdConnection::BindToAd Bound. hostName:my.dns.host.name
20180806 16:09:10.500 2572 CFAD   199 Config::AdConnection::BindToDc Try to bind. hostName:\\my.dc.domain.name domainName:<null>
20180806 16:09:10.500 2572 CFAD  3373 [ERROR] Config::DsSession::Bind Failed to DsBind(). dc:\\my.dc.domain.name domainName:<null> Error:5
20180806 16:09:10.500 2572 CFAD   215 Config::AdConnection::BindToDc (Ignored) Failed to bind. hostName:\\my.dc.domain.name domainName:<null> Error:[Error:5(0x5) Config::DsSession::Bind ad.cpp:streetAddress Access is denied.]
20180806 16:09:10.500 2572 CFAD   199 Config::AdConnection::BindToDc Try to bind. hostName:\\my.dc.IP.address  domainName:<null>
20180806 16:09:10.500 2572 CFAD  3373 [ERROR] Config::DsSession::Bind Failed to DsBind(). dc:\\my.dc.IP.address domainName:<null> Error:87
20180806 16:09:10.500 2572 CFAD   215 Config::AdConnection::BindToDc (Ignored) Failed to bind. hostName:\\my.dc.IP.address domainName:<null> Error:[Error:87(0x57) Config::DsSession::Bind ad.cpp:street address The parameter is incorrect.]
20180806 16:09:10.500 2572 W2CH   779 [WARN] ConfigurationHelper::PollAdConfigNow Failed to get migration status. Error:
+    [Error:160(0xa0) Migration::SysVolMigration::IsLocalComputerLongHornLevelDc migration.cpp:StreetAddress One or more arguments are not correct.]
+    [Error:160(0xa0) Migration::SysVolMigration::Connect migration.cpp:StreetAddress One or more arguments are not correct.]
+    [Error:160(0xa0) Config::AdConfig::ConnectToLocalDc ad.cpp:StreetAddress One or more arguments are not correct.]

So, Why am I able to create the DFSR group, and it works until reboot, then it breaks?  If there is an AD parameter wrong, which is it, and why does it not find that when I create the replication group?

I inherited 2 DFS-R hosts connected via a WAN.  We'll call them Michigan and California.  We have several replication groups, one of which is massive, in the realm of 1.4million files and 1.6 Terabytes after deduplication.  About 2 weeks ago, all of a sudden we had a 1.4 million file back log.  For whatever reason, that backlog jumped back up to 1.4 million at least once since then.  Fast forward to earlier this week and the backlog of files being sent from California to Detroit is ZERO. However, the backlog of files being sent from Detroit to California is seemingly stuck at right around 80,000 and growing (as users continue to make changes).  For the life of me, I can't figure out what's the hold up.  The DFSR logs are pretty much greek to me.  I've seen suggestions to disable membership of the backlogged node, wait for the changes to replicate in AD and get picked up by the member servers, then re-enable it, to kick off an initial sync.  The problem is, I'm under the impression if I do that I'll lose data that hasn't replicated from Detroit to California yet, since California would become the "master".  Sure I can run a preemptive backup, but there's still a chance that someone will change something while that 18 hour backup runs.

Are there any ideas of what I can do.  I'd love to narrow this down to figure out what exactly is the hold up.  I'm at my wit's end with this thing.

Long term, the plan is to replace this current DFS solution with something else or to at least prune it down and/or break it into smaller parts.  However, I'm stuck with what I've got for the moment.

Any help would be GREATLY appreciated.

Microsoft-Windows-WorkFolders/Operational
Event ID 2100 "Error while connecting to server" error: (0x80072ee2)

That's basically means a timeout.
It seems to be temporally problem and occurs also when the machine is connected via LAN very well to the server.
the server log syncshare//Operational logs nothing at this time.
Is there another log on the server where we can see if the request arrived the server or not, such the w3svc log.

Thanks
Eckhard

Eckhard

I have several quota templates configured for different user's home folder, so user can't use over the quota template limits which they belong to. Recently, I found more and more users have space usage issue after they reached quota templates limits. 

For example, userA is belong to 1GB template for his folder. He ran out of space, so he deleted all his files, but it still shows o space on client side. Also under File Server Resource console, I still see userA used 100% of his space. To help userA gets back his space, I will have to delete userA's template, and re-apply it. Can someone tell me why this happened? Thanks!

We've just deployed Work Folders in our organisation and so far we're loving it. It solves a lot of issues and enhances our user's experience.

I have a question about .ini files. 

We have essentially created a work folder on their laptops containing C:\Users\Username\Work Folders\...

• Documents
• Desktop
• Downloads

We've used GP to redirect their associated folders to this new location using folder redirection. This allows remote workers to save and open files without the files going over the WAN everytime as we've set it to always be available whilst offline. 

One big problem we have at the moment is with the sync icons. When I look at File Explorer, it'll show Desktop, Downloads and Documents with a BLUE Sync Arrows. If I click on those folders, everything is green ticks. This simple GUI glitch throws the user into thinking it's not synchronising correctly. My understanding of this behaviour is a result of the desktop.ini file. Work Folders ignore .ini .tmp files. So if a user has those, then the top level folder shows as continuously syncing, even though it's not. 

Now, I'm new to this feature and as far as I understand, it has been about since Windows Server 2012 R2. Does this always happen? Is it normal behaviour to show the top level folders with the blue sync arrows, even though everything inside has synced or is it a relatively new GUI bug that affects Windows 10 1803?

You can replicate this behaviour simply by adding a .ini file inside a work folder. The top-level folder will show the syncing icons. The sync control panel will show green - syncronised. 

Does anybody have a workaround so I don't throw the users experience off? I'm getting support calls because they think it' not syncing.

Thank you

Hello,  We have an existing dfs namespace simply named domain.com\dfs that has 3 replicated folders, Applications, Users, BranchData.  At each branch office there is a local file and print server, and each office is in its on site in AD Sites and Services.  This has been working perfectly for a number of years, but now we have a new office under construction and I am working on getting the new office server ready for deployment.  When I try to add this new server with the new member wizard (simply by right clicking on our domain.com\dfs under Replicaiton in DFS Management, I can get through to finish out but I get an error for each folder:

\\server\Applications.  The folder target \\server\applications cannot be added to the folder.  The file exists.

\\server\Users.  The folder target \\server\users cannot be added to the folder.  The file exists.

\\server\BranchData.  The folder target \\server\BranchData cannot be added to the folder.  The file exists.

I close out of the wizard, and those folders are created and shared properly on the server.  However for local path it shows <not Defined> and has a yellow exclamation point next to it.

Someone on another forum said to try it from another DFS Management console.  I did try from the new server (Server 2016), an existing Server 2012 R2, an existing Server 2008 R2, and also my Windows 10 1803 with the RSAT tools.  All DFS Management consoles produce the same result.  I tried creating the folders and shares on the new server first, and I also tried it with those three folders and shares not on the new server at all... both ways it fails on that error.  This is the first 2016 server in the domain so I wonder if that's part of the difficulty.

Hi Guys,

We have a folder replicating via DFS. The replication is set up for over 400 machines. We had someone delete the entire Replication group. Is it possible to audit or log when any changes are made to the DFS replication group by any user?

Like when someone adds or removes a server from the replication group or when someone deletes the whole replication group.

Cheers,

Edward

Hi,

In one our server, network drive is not working. It's shows as disconnected drive but able to open it, when try to list the mapped drive from command prompt using "net use" command it's not showing the mapped drive details. Hence it's affecting the applications installed in the server, where applications are using the drive. 

However i have fixed the issue using psexec tool to unmap and remapped with persistent option enabled. I want to know the root casue for this issue.

Recently we installed KB4103718 in the server, this rollup have known issue (refer the below link) with network interface controller. After installing the patch static IP's were removed from the NIC cards. So we have removed the hidden NIC's and assigned the IP address back.

Is something caused the mapped network to stopped working?

https://support.microsoft.com/en-in/help/4103718/windows-7-update-kb4103718

Thanks in advance.

vicky

I don't understand what to Microsoft Storage Spaces Controller do?

Can I disable it?

The problem is this:

We had a user that about 6 months ago decided to rename 4 folders in a Data Directory used to store data for a database.  As this was done 6 months ago, many new records have since been created using the renamed folders in their document paths.  

However, any records created before she renamed those folders have the original folder name in the path for the documents that belong to those records.  Needless to say, this is something that NEVER should have been done.  But i have to deal with the current situation if i can find a way to fix things.

My first thought was to recreate the original folder names and put a copy of every document in them that exists in the renamed folders.  This way, when the database is used, it wont come up with "document not found errors" due to those documents now existing with just a single folder name being changed in their path.

However:  There are thousands of documents that would have to be copied as these are huge folders.  And there is no easy way to sort out which were stored with the original folder names in their path and which were stored with the new name in their path.

I was wondering if there was a way to create virtual junction of sorts or a path "alias" where Windows would treat a path with both the old name and the new name in as if they were the same?  

Example  R:\Folder\A\filename.docx   =   R:\#1 Folder\A\filename.docx.   

With All the documents actually existing only in the new path.

The person who did this did exactly that when she created this problem.  She renamed four of the already in use main data folders by adding #1,#2,#3,#4 to the front of those folder names

No one even noticed as no one has tried to look up any of the filed document until now.  And of course by now there are hundreds if not thousands of documents that have their paths stored as R:\#1 Folder\A\filename.docx  as well as the original thousands that had their paths stored as R:\Folder\A\filename.docx.

I would like to find a way (if one exists) to make Windows treat any calls to find files located at either path end up going to the one as it is named now. 

I have already contacted the database software company to see if we can mass edit the records in the database to change those paths as that would probably be the most logical solution but all of their software is proprietary.  Unless we can get them to do it, it is unlikely that an open-source tool is available to work on their database structure.

I am also open to any other ideas that anyone can offer.  Keeping two copies of every document in the database just so they would exists at the end of both paths would be extremely wasteful of space but may be our only alternative if we cannot find another way

I believe I am seeing a problem with ISCSI Initiator.  When a Command PDU that's sent by ISCSI Initiator is rejected by my target (Reject PDU), it appears ISCSI Initiator retries the same Command PDU but fails to increment CmdSN.  So my ISCSI target, seeing an "old" CmdSN, simply drops it which eventually leads to Task management by ISCSI Initiator.

Here the order I observe:

1. ISCSI Initiator issues command PDU with CmdSN 0x50.

2. Target rejects with Reject PDU, ExpCmdSn in Reject PDU is 0x51.

3. ISCSI Initiator retries command PDU again with CmdSN 0x50.  (against spec)

4. Target ignores the retry.

5. ISCSI Initiator issues LUN Reset because target never responds.  LUN Reset has CmdSN 0x51.

6. Target processes LUN Reset.

I believe this is a problem with ISCSI Initiator as commands, even retried commands, should never repeat CmdSNs.  Is anyone else seeing an issue like this?  Is there a method to formally file a bug against this?

Hi,

How would we get Shadowcopy to send notification of status - e.g. successful shadowcopy - with some stats.  Either email or event log alerts would do. 

Any alerts or reports?

thanks,

Hi All, 

I had a windows 7 machine built to share a folder on my workgroup network. I slowly grew my network and begun getting an error that there was too many simultaneous connections. 

I was told to upgrade to server 2016 STD so i purchased it and have it installed and running still as a workgroup and have shared the folder but it still seems to be happening. Have i missed something ?? 

They are all windows machine either 7 or 10 and they are all using one users credentials to auth the shared folder. Should we be using seperate usernames and passwords to authenticate the shared folder?

thanks in advance 

Anthony

Hi,

We have DC1, DC2, fileserver and they has DFS roles installed

DC2 is FSMO roles master and it is only one from which I can access DFS management

From DC1 and fileserver I get error:

\\domain\namespace: Delegation information for the namespace cannot be queried.  The specified domain either does not exist or could not be contacted.

Is it normal that I cant access DFS management form DC1 and fileserver ?

Is it true: http://www.itsupportforum.net/topic/the-namespace-cannot-be-queried-the-specified-domain-does-not-exist/

Hello,

We have for some weeks on some PCs with Windows 7 prof. errors in the Workfolders.

"Error while synchronizing. Workfolderpath C:\Users\username\work Folders\; error 0x80072efe"

Event-ID 2100

see pic:

Not on all W7 Prof. Clients occurs this error. So is must be a Client mistake not a Workfolder Server error.

Whats wrong? 

Thanks for help.

Danke und liebe Grüße Oliver Richter

Hey guys!

You can see the topic of this discussion in the title. I want to create a Junction and it should be pointing to another server. Is there a way to create this with Windows 2012 R2. I believe a DFS Domain Named Space or Server based DFS is not the solution. Maybe someone knows about Novell OES DFS Junction. It's pretty easy to create Junctions with Novell. By the way I grew up with windows. I only use Novell at my work because I have a large filserver environment to manage with up to 60TB. I'm wondering because with windows I find no function to create Junctions.

Why is my text so small? I don't know.

Hi I have plan to build s2d two node cluster with 4x 800 12gb SAS Write intensive SSD for cache, 2x960 GB SATA mixed use for performance tier and 10x 2.4 TB SAS 10k for capacity. It's possible to have such scenario. Is it supported?

Thank you OOSOO

Hi There,

Massive shot in the dark here but I am struggling with a pretty major issue atm.  We have a production file server that is hosted on the following:

Dell MD 3220i -> iSCSI -> Server 2008 R2 Hyper-v Cluster -> Passthrough Disk -> Server 2012 R2 File Server VM

Essentially 3 times now, roughly a month or so apart.  The file server stops accepting connections.  During this time, the server is perfectly accessible through rdp or with a simple ping.  I can browse the files on the server directly but no-one appears to be able to access the shares over SMB.  A reboot of the server fixes the issue.  

As per a KB article I removed nod antivirus from the server to rule out a conflicting filter mode driver after the second fault.  Sadly yesterday it happened again.

The only relevant errors in the servers log files are:

SMB Server Event ID 551
SMB Session Authentication Failure

Client Name: \\192.168.105.79
Client Address: 192.168.105.79:50774
User Name: HHS\H6-08$
Session ID: 0xFFFFFFFFFFFFFFFF
Status: Insufficient server resources exist to complete the request. (0xC0000205)

Guidance:

You should expect this error when attempting to connect to shares using incorrect credentials.

This error does not always indicate a problem with authorization, but mainly authentication. It is more common with non-Windows clients.

This error can occur when using incorrect usernames and passwords with NTLM, mismatched LmCompatibility settings between client and server, duplicate Kerberos service principal names, incorrect Kerberos ticket-granting service tickets, or Guest accounts without Guest access enabled

and

SMB Server event ID 1020
File system operation has taken longer than expected.

Client Name: \\192.168.105.97
Client Address: 192.168.105.97:49571
User Name: HHS\12J.Champion
Session ID: 0x2C07B40004A5
Share Name: \\*\Subjects
File Name: 
Command: 5
Duration (in milliseconds): 176784
Warning Threshold (in milliseconds): 120000

Guidance:

The underlying file system has taken too long to respond to an operation. This typically indicates a problem with the storage and not SMB.

I have checked the underlying disk/iscsi/network hyper-v cluster for any other errors or issues, but as far as I can tell everything is fine. 

Is it possible that something else is left over from the NOD antivirus installation?  

Looking for suggestions on how to troubleshoot this further.

Thanks