Windows 7 SP1 - DFS Problem
I am getting an error accessing DFS on Windows 7 SP1 64 bit.
This is happening on both upgrading from Windows 7 64bit no service pack and a new install of Windows 7 SP1 64bit straight from the media downloaded from the Volume Licensing Service Center website.
The error is Error Code: 0x80070035 'The network path was not found'
All other operating systems in our organisation don't have this problem it is only Windows 7 SP1 64bit.
Has anyone else had a similar problem?
March 28th, 2011 4:09am
Some additional details:
Windows Network Diagnostics
Publisher details
Issues found
Windows can't find "\\domain\global\App Deployment"
Windows can't find "\\domain\global\App Deployment"
Detected
Verify that you typed the name correctly, and then try again
Completed
Issues found
Detection details
5
Windows can't find "\\domain\global\App Deployment"
Detected
Verify that you typed the name correctly, and then try again
Completed
Windows can't find "\\domain\global\App Deployment". The name might be misspelled.
Detection details
Network Diagnostics Log
File Name:
68098F56-EBD2-4A17-9553-6EAC4ED7BD2C.Diagnose.0.etl
Other Networking Configuration and Logs
File Name:
NetworkConfiguration.cab
Collection information
Computer Name:
GRP-D0048
Windows Version:
6.1
Architecture:
amd64
Time:
Tuesday, March 29, 2011 10:34:22 AM
Publisher details
Free Windows Admin Tool Kit Click here and download it now
March 29th, 2011 3:38am
Hi,
Could these Windows 7 SP1 access other server or share folder?
According to the error message, the issue related with network path, please first make sure the network path is correct. And use “ping DFSIPaddress” in
command prompt to DSF and see the result.
Also you can perform these tests to troubleshoot the issue:
1 Login with
Clean Boot
2 Temporally disable firewall
3 Enable NetBIOS over TCP\IP
4 Try using these KBs:
http://support.microsoft.com/kb/977511
http://support.microsoft.com/kb/983620
Hope that helps.
Regards,
Leo HuangPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
March 30th, 2011 12:07pm
Hi,
Could these Windows 7 SP1 access other server or share folder?
According to the error message, the issue related with network path, please first make sure the network path is correct. And use “ping DFSIPaddress” in
command prompt to DSF and see the result.
Also you can perform these tests to troubleshoot the issue:
1 Login with
Clean Boot
2 Temporally disable firewall
3 Enable NetBIOS over TCP\IP
4 Try using these KBs:
http://support.microsoft.com/kb/977511
http://support.microsoft.com/kb/983620
Hope that helps.
Regards,
Leo Huang
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Hi,
Thanks for your reply :)
I tried the sugested my results below.
1 Login with
Clean Boot - Didn't fix the problem
2 Temporally disable firewall - Didn't fix the problem
3 Enable NetBIOS over TCP\IP - Didn't fix the problem
4 Try using these KBs:
http://support.microsoft.com/kb/977511 - Didn't work.
http://support.microsoft.com/kb/983620 - Does not install as it SP1 is installed
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2011 4:25am
Try disabling "Offline Files"
I hope that helps!
April 4th, 2011 8:39pm
Try disabling "Offline Files"
I hope that helps!
Just gave that a go, unfortunately it didn't work.
Have also tried a suggestion here about the master browser, didnt work either.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_26923781.html
This one really has me stumped.
Free Windows Admin Tool Kit Click here and download it now
April 5th, 2011 6:53am
I'm running into this issue as well. Anyone have any other suggestions?
April 6th, 2011 7:44pm
Just to add further info.
I have enabled net bios, disabled IPv6, updated drivers all to no avail.
I can ping the DFS path ok, I can access the DFS root ok. Just seems to be when I access a share in the DFS root. If i type my local server where the path is actually shared from I can access that ok.
The share \\domain\global\App Deployment < Doesn't work
The share \\IP\Global\App Deployment < Doesnt work
My local server share \\server\appdep_global$ < This works ok
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2011 1:30am
More info.
When I right click on the folder under DFS and go to the DFS tab the folder I cannot access, the "Referral List" is pointing to the "Namespace Server" List rather than the "Folder Target" list.
April 7th, 2011 8:23am
Has anyone else come across this issue?Russo
Free Windows Admin Tool Kit Click here and download it now
April 14th, 2011 7:52am
Hi Guys,
We are having tjhe same issue but only for our emea reginal domain. All other domains seem to be ok..very strange!!
Going to try wireshark..
Anybody managed to resolve yet?
April 14th, 2011 12:25pm
Still havent resolved this yet. Have you come accross anything else? Are you only getting the issue on Windows 7 SP1?Russo
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2011 4:09am
I tried the hotfix but it didn't work on win 7 sp1 machine. Any other suggestions?
May 5th, 2011 11:39pm
I have a solution!!!
From a Windows 7 Install (No service Pack) copy dfsc.sys from C:\Windows\System32\drivers.
On the PC with Windows 7 SP1 overwrite dfsc.sys with this version.
You will need to take ownership of th existing file to replace it.
Browse to C:\Windows\System32\Drivers
Right click dfsc.sys and go to Properties
Go to the Security Tab and click Advanced
Go to the Owner Tab, click edit. Select "Administrators".
Press ok on all dialog boxes.
Again right click dfsc.sys and go to Properties
Go to the Security Tab and click Edit
Assign Full Control to all groups/users
Restart your PC and viola.
Test and confirm that it works.
**Note: dfsc.sys from this hotfix
http://support.microsoft.com/kb/983620 does not resolve the issue. If you wish to test you will need to extract the MSU file as it will not install on Windows 7 SP1 x64. To extract:
expand -F:* Saved_MSU_File_Name.msu c:\MSUFolder
expand -F:* Saved_MSU_File_Name.cab c:\MSUFolder
Russo
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 6:17am
Hi Russo,
Can you post version of dfsc.sys you downgrading to? We have similar problem with Win 7 32-bit (both RTM and SP1)
May 12th, 2011 4:14pm
I confirmed that others had found the above fix.
http://www.bench3.com/2011/05/error-0x80070035-network-path-was-not.html
Was hopeful my issue would be resolved but no go. Replaced my SP1 DFSsc.sys file with a pre SP1 version - Version 6.1.7600.16385 Date 7/13/2009 but it still didn't work.
The MS hotfix didn't work for me either.
Note: dfsc.sys from this hotfix
http://support.microsoft.com/kb/983620 does not resolve the issue.
Free Windows Admin Tool Kit Click here and download it now
May 13th, 2011 9:20pm
Hi Aoisola,
It is version 6.1.7600.16385, 14/07/2009 9:23AM, x64
Russo
May 16th, 2011 2:23am
http://www.bench3.com/2011/05/error-0x80070035-network-path-was-not.html was taken from this very forum :)
When you say "The MS hotfix didn't work for me either." Did you manually extract the file? I found just running that msu does not install for Windows 7 SP1.
The file from KB 983620 is 6.1.7600.20714 17-May-2010 22:53 x64Russo
Free Windows Admin Tool Kit Click here and download it now
May 16th, 2011 2:30am
Hi Russo,
Good catch on the fix link :)
On the MS hotfix issue, I get the following error when trying to install it: "The update not applicable to your computer."
May 17th, 2011 1:29am
Hi Autoxr,
I've updated my answer about how to extract the file from the hotfix. Hope that helps :)
http://support.microsoft.com/kb/983620 If you wish to test you will need to extract the MSU file as it will not install on Windows 7 SP1 x64. To extract:
expand -F:* Saved_MSU_File_Name.msu c:\MSUFolder
expand -F:* Saved_MSU_File_Name.cab c:\MSUFolder
Russo
Free Windows Admin Tool Kit Click here and download it now
May 17th, 2011 1:40pm
Did you have any luck with the latest version of dfsc.sys?Russo
June 15th, 2011 7:07am
Hi Russo,
I'll try out your fix and post an update.
Free Windows Admin Tool Kit Click here and download it now
June 21st, 2011 1:07am
Hi Russo,
Just tried your fix. I now have dfsc.sys version 6.1.7600.20714 and rebooted. Unfortunately, it still doesn't work for me. Note, I my workstation is not joined to the domain that is hosting the Domain DFS root but before SP1, I was
able to. Please let me know what you think and thanks for your help.
June 22nd, 2011 11:37pm
Hmm..
Go to event viewer and start going through system logs to see if you can find anything out of the ordinary.
What OS is your DFS sitting on?Russo
Free Windows Admin Tool Kit Click here and download it now
June 29th, 2011 7:44am
We also had the "Mapped DFS Share on Client points to wrong site server" problem in our company environment (Server: Windows Server 2003 DC, Client: Windows 7 SP1).
The problem could be resolved by changing the offline settings on the share of the local server.
They were set onto: Files or programs from the share will not be available offline.
I've changed this into: Only the files and programs that users specify will be available offline, which now let the client map the DFS share from the local server instead of a remote one.
However, some of the W7 clients needed this additional task (changing the site server while normal user logged in doesn't work permanently):
Logged in with (Domain) Admin account on this client Mapped the DFS share once - a wrong site server was selected now Changed it to the local site server After a reboot, logged in with normal user account, and finally the site server for the mapped DFS Share was the local one
November 26th, 2011 2:16am
I just checked my local server hosting DFS for that setting and it was already set to
Only the files and programs that users specify will be available offline.
Also tried the extra step for the client and it still didnt work. I currently have MS support looking into the issue, when they find their fix I will post back here.Russo
Free Windows Admin Tool Kit Click here and download it now
November 28th, 2011 4:38pm
Hello Russo,
I've just worked through this same problem and believe I've found a workaround. Perhaps the information will help MS Support.
After resolving all of the issues with the wrong DFSC.SYS, and name resolution I still had intermittent problems with mapping some of the DFS drives (some DFS drives mapped just fine). The ones that did not map failed with an error 55 - network resource
not available and showed up in my computer with a red X.
Manually attempting to disconnect or reconnect the drives using Net Use failed.
I found that after using explorer to directly access the DFS share via the UNC, I was able to successfully map the share to the drive letter.
I found that I could also do this from a command prompt via the command:
C:\>DIR \\DFSDOMAIN\DFSShare > nul
I then edited my drive mapping script and added that line before the net use commands and it seems to have taken.
If your ticket is still open, Please share this information with Microsoft and see if they can do anything useful with it.
Dennis
December 6th, 2011 1:12am
Hi Dennis,
My MS case was closed yesterday as I got my issue resolved. One of the namespaces was not working for me from my DFS share but others were, I believe something to do when we transferred from a 2003 Domain to a 2008 domain.
For my issue it was a combination of 2 things to get it working.
1. I had to install this hotfix onto my client machines
http://support.microsoft.com/kb/2549311
2. I had to recreate the namespace that I could not access.
After doing that I was able to access the share.
MattRusso
Free Windows Admin Tool Kit Click here and download it now
December 6th, 2011 1:20am
We had the same problem (Windows 7 x64 Enterprise) and hotfix KB2549311 fixed the problems we had with GPO mapped dfs namespaces in our environment.
We had the symptoms described in KB983620 and KB2549311 fixes the problem. Seems like this hotfix is coming with Windows 7 SP2 later this year.
March 25th, 2012 6:11am