Force Attrib to Continue if File Not Found
DIR command is failing when specific file name is searched...
dir file.txt returns File Not Found
What do you see against this command:
dir /a *.txt
Was this reply helpful?
Since I can't reproduce it on my system, I have to wait for users to respond.
Windows 7 non-working system running dir /a *.txt
returns File Not Found
Interestingly, when the user maps the share via net use command it is not prompting them for uid/password. So now I'm wondering if this is a side effect of not properly authenticating to the share and using some form of cached credentials. I did not see anything in the non-working Windows 7 credential manager for the share site...is there another place to look or way to force invalidation of stored network credentials?
Was this reply helpful?
Interestingly, when the user maps the share via net use command it is not prompting them for uid/password. So now I'm wondering if this is a side effect of not properly authenticating to the share and using some form of cached credentials. I did not see anything in the non-working Windows 7 credential manager for the share site...is there another place to look or way to force invalidation of stored network credentials?
The user might be sailing on some remembered credentials. You should start with a clean slate, e.g. like so:
net use * /del /y
net use Q: \\SomeServer\SomeShare
dir > Q:\Test.txt
dir /od Q:\*.txt
Was this reply helpful?
stepping back to last/initial test...
- Windows 7 non-working system...
- User NOT prompted for login credentials and the net use drive mapping command succeeded successfully
- cd to the mapped drive letter successds
- ATTRIB command returns 'The target of the symbolic link [path\filename] does not exist' for all 20 files in the shared folder
- dir /a *.txt returns File Not Found
- Windows 10 non-working system...
- User IS prompted for login credentials and the net use drive maping command succeeded successfully
- cd to the mapped drive letter succeeds
- ATTRIB command returns 'The target of the symbolic link [path\filename] does not exist' for all 20 files in the shared folder
- dir /a *.txt returns File Not Found
With same behavior from no login and login I'm back to thinking this is once again something in the local system...some sort of policy or cached offline content or something else.
What would cause windows to see real files in a network shared folder as sym links???
Was this reply helpful?
Sorry, can't help you, because with this type of bizarre behaviour I need to look at things with my own eyes.
Was this reply helpful?
jeffersonmandiess77.blogspot.com
Source: https://answers.microsoft.com/en-us/windows/forum/all/dir-and-attrib-command-not-showing-all-files/b5de16ce-3d56-4ca0-a224-4c250f93ca02
0 Response to "Force Attrib to Continue if File Not Found"
Post a Comment