InterwebsGuy Posted November 28, 2011 Posted November 28, 2011 Morning guys, I have just posted the below on Server Fault regarding an issue we are having with some of our desktops and users. I was just wondering if any of our friends in the world of academia had also come across this problem? Cheers Adam ---------- We have an interesting issue with one of our server shares, or possibly, our Win 7 desktops. When our users try to save files in a sub folder, either via copy/paste or through an application, to a mapped drive on our DC they receive an error saying "Path not found". They can however browse this folder and open files from it. This is where the "Path Not Found" error doesn't seem to stack up in my opinion. Users can however save files fine in the root folder of the mapped drive, it appears only to affect sub folders. It seems to be random which users and machines this affects. The users can log on to a different machine and be able to save in sub folders fine, on the same mapped drive. Event viewer hasn't been much help either. Currently, the only solution we have found is to image the machines affected which solves the issue. Our servers are Server 2008 R2 with Win 7 Pro desktops. Any help/pointers/suggestions would greatly be appreciated. windows server 2008 - "Path Not Found" when attempting to write to a sub folder within a mapped drive - Server Fault
Michael Posted November 28, 2011 Posted November 28, 2011 From the server, if you right click the share and select 'Properties'. Click the Security tab > Advanced > Change Permissions, then tick 'Replace all child object permissions with inheritable permissions from this object'. Click on Apply and wait for the process to complete. The reason I suggest this is because it appears more a permissions issue rather than 'path not found', as users can browse the network drive. 1
InterwebsGuy Posted November 29, 2011 Author Posted November 29, 2011 Hi Michael Thanks - I will investigate that, it is certainly worth having a look at. My first thoughts are it wouldn't be a perms issue, because it does work fine when the user moves to a different machine. However you can never rule anything out. Thanks for your input. Adam
glennda Posted November 29, 2011 Posted November 29, 2011 Hi Michael Thanks - I will investigate that, it is certainly worth having a look at. My first thoughts are it wouldn't be a perms issue, because it does work fine when the user moves to a different machine. However you can never rule anything out. Thanks for your input. Adam If it is a perms issue then its worrying it works on another machine! It's not if they create the folder then try and save into it? We've had that a few times where it is still trying to save to "New Folder" when actually you have named the folder something else. 1
InterwebsGuy Posted November 29, 2011 Author Posted November 29, 2011 (edited) If it is a perms issue then its worrying it works on another machine! It's not if they create the folder then try and save into it? We've had that a few times where it is still trying to save to "New Folder" when actually you have named the folder something else. We have just checked the perms and they do appear to be correct, which kind of makes sense as they have always been as they are and worked. @glennda - no, it is not similar to that, it is applying to folders that have been created previously. As I have just mentioned on ServerFault, shortly before we started to have this issue, a network cable was knocked out the back of the server causing a lost connection for a moment or two. I'm not sure how this could be related or cause this issue, but is probably worth mentioning. We are using folder redirection and then in addition a basic vbs script to map the drives in [My] Computer. Thanks for your input people so far. Edited November 29, 2011 by InterwebsGuy
Michael Posted November 29, 2011 Posted November 29, 2011 It is weird the root's OK but not sub folders. This is why I suggested permissions. Are you using the FQDN in your VBS script? What about the length of folder names? Does the problem happen on wired and wireless? Have you checked your switches for any errors or maybe try changing the patch leads if wired?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now