Unable to access folder on server

I manage a small network of a dozen machines all running XP that attach to a server running Win 2003.

The subject machine can access several shared folders on the server, but one folder is not accessible. It is accessible from other machines, but just not this one. I have checked everything I can think of and compared it to machines that can access it.

Can someone point me in the right direction?

Thanks in advance
TheTechnicalDoctorAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
PeteJThomasConnect With a Mentor Commented:
Agreed, this is very strange, especially seeing as the Effective Permissions confirm that she has FC of that folder, which means there are no explicit denies set in any of the inherited permissions.

If the share permissions are also set correctly (which they seem to be, if adding the 'Everyone' group resolves the problem) there is no feasible reason why she cannot access that folder if her name is in the permissions list.

I have to admit it's been a long time since I worked with Workgroups instead of Domains, but there is one more thing i'd like to clarify (maybe either of you can educate me!!) In a workgroup, you use local accounts on each client machine correct?

If so, how do you even add a local user on a client to the permissions list of a share on another computer entirely? Can you specify like this on the share - <computername>\<username>?

Sorry if i'm confusing things again, but my line of thought is that in a workgroup, when connecting to a share on another machine, do you not need to have 2 local accounts (one on the 'server' containing the share, and the other on the client connecting to that share) which would need EXACTLY the same username AND password set?

Maybe my brain hasn't kicked in yet, it is early after all... :)
0
 
PeteJThomasCommented:
Ok - When you say you can't access it, what exactly do you mean? You can't even see the folder, or you get an access denied error, or what?
0
 
JohnjcesCommented:
If it is shared and cannot be seen from any machine, (and surely one should be able to see it), then there is an NT security issue going on with that share.

If you go to Sharing on that folder, are the permissions AND the secuity identical to all of the others?

Usually it is Security. That is where I go to set shares for for specific users.

IF the folder cannot be seen on the network as a shared folder, (as you should stil be able to 'see' it, then I would move the files off of that share, delete the share, delete the folder and recreate.

Make sure too that your share name is not some Windows reserved keyword or ends in a $ dollar sign.

John
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
TheTechnicalDoctorAuthor Commented:
Thanks for the comments.  As mentioned, other comnputers can open the subject folder.  The machine in question can see the folder, can browse to the folder, and can open other folders on the server.  But, when you attemp to open it (double click) you get the error.
0
 
PeteJThomasCommented:
But what error is it you're receiving? I can't see it written anywhere in your original post... :)
0
 
JohnjcesCommented:
Pete has it right... what error?

And are the permissions and securities on that one folder 100% identical to the folders that one PC can browse on that server?
0
 
TheTechnicalDoctorAuthor Commented:
The message is something like this "Impactservero1/hr on impactserver01 is not accessable.  You do not have permission to access....."

I am not at the site, so until I reutrn I can not give you the exact message.
0
 
JohnjcesCommented:
Permissions issue...

Got to check and make certain that one PC is or user or whatever is not denied.
0
 
PeteJThomasCommented:
I agree with John! It must be a permissions issue... Send us a print screen of the permissions set on that particular folder if you want more specific help... :)
0
 
TheTechnicalDoctorAuthor Commented:
The error message is "\\impact01\impact\hr is not accessible.  You might not have permission to the this network resource.  Contact administration of this erver to find out if you have access permission."

As suggested, I created a new folder on the server and set the permissions for this user and still could not open the new folder.  I then added selection, "Everyone" to the permission list and was able to access the folder from the subject machine.  

I am looking for further direction and will be posting the exact permissions for this user that is having the problem.

0
 
JohnjcesCommented:
Are you on AD with a domain? If so...

If you remove 'user' from the sharing permissions tab, then no user at all will be able to use the share. You must have 'User' present but you can users to this share.  But...

You lock down the share permissions and can deny everyone else under the security tab.

Anxious to see the exact pemrission for this as well as your other working shares.

John
0
 
TheTechnicalDoctorAuthor Commented:
This is a simple setup without a domain.  I am working on the screen shots
0
 
PeteJThomasCommented:
Excellent - Once we have the screenshots it should be much easier to figure out what's wrong... Just bare in mind (and sorry if you already know this well) but there are 2 sets of permissions if you have actually shared the folder.

The share permissions are much simpler, and it's easier to just add the 'Everyone' group and grant them either change or Full Control.

Then you can get specific with the NTFS permissions on who can access the folder itself. Awaiting the screen shots! :)
0
 
TheTechnicalDoctorAuthor Commented:
Here are the screen shots.  Ashlie is the person who can see, but can not open the HR folder unless "everyone' is part of her profile.  Also you will find the properties for the folder in question.

If you need anything else, just ask.
SP32-20080201-073109.gif
SP32-20080201-073129.gif
SP32-20080201-073135.gif
SP32-20080201-073140.gif
SP32-20080201-073145.gif
SP32-20080201-073152.gif
SP32-20080201-073155.gif
SP32-20080201-073159.gif
SP32-20080201-073204.gif
SP32-20080201-073326.gif
SP32-20080201-073328.gif
SP32-20080201-073337.gif
SP32-20080201-073348.gif
0
 
PeteJThomasCommented:
Ok, admittedly all appears ok at first glance - But can you now show me the 'Share Permissions' for that folder as well? You can view these permissions by going into the 'Sharing and Security' tab on the folder, and clicking the 'Permissions' button, as in the pic below -
Share-Permissions.bmp
0
 
TheTechnicalDoctorAuthor Commented:
Here you go, let me know if you need more snaps
SP32-20080201-081217.gif
0
 
PeteJThomasCommented:
Ok, and can I just clarify - What exactly is it that fixes the problem?

Is it if you add the 'Everyone' group to the security list, and give it Modify/Full Control?
0
 
TheTechnicalDoctorAuthor Commented:
I am not sure I understand your request.  

If Ashlie is on the list, she can only see the folder, not open it.

If I add 'Everyone" to the permissions list, then she can open it.

Does that answer your question?
0
 
PeteJThomasCommented:
Yes it does!

You could try copying her profile (c:\documents and settings\<username>) to a safe location (just to ensure any data in her My Docs etc is not lost), then delete her account completely, and recreate it, ensuring that the memberships are set correctly again.

It's also worth trying this before you do that -

Go to the folder properties again, > Security tab > Advanced > Effective Permissions tab > Select button and find the user within the workgroup, and select her (in the pics below).

This will show you exactly what permissions are applying to that folder for that particular user. It's useful just to clarify that Full Control is the result - If it's not, then there must be a problem with the permissions somewhere... Try it and take a pic of the result (same as my second pic) and show me, then if still not resolved it's probably worth trying my other suggestion (delete and recreate)...

Let me know! :)
Effective-Permissions.bmp
Example.bmp
0
 
TheTechnicalDoctorAuthor Commented:
I have two monitors, its the one on the left.  I am accessing the server via a VPN connection.
SP32-20080201-104111.gif
0
 
TheTechnicalDoctorAuthor Commented:
Tried both suggestions, still have the issue.

Let me clarify a  little more.  Ashlie can see all the folders and can open any folder that has "everyone" in the permission area and can not open any other folder, even if her name is in the permission list.

It's like there is a black list against her and being on the white list does not matter.

She is the only user on this server that I am having an issue with.
0
 
JohnjcesConnect With a Mentor Commented:
I have gone over your stuff many times. I do not know. Add Users and it works remove and it stops. I am assuming that users is not in your permissions on any of your other shares.

This is an odd one!

Sorry!

John
0
 
TheTechnicalDoctorAuthor Commented:
I need some help understanding your question - "In a workgroup, you use local accounts on each client machine correct?"  By local account do me that individuals account on that machine?

Let me also ask a releated question.  Would changing this over from a workgroup to a domain help resolve the issue.

I have never setup a domain and would need some assitance.  I will be willing to post other questions with points to be awarded to help me accomplish that task.
0
 
PeteJThomasCommented:
Ok let me try to reword my question...

On your images, the account we're talking about is shown as 'IMPACTSERVER01\Ashlie.Martin'

That would indicate that this account is a LOCAL account on IMPACTSERVER01 (which I guess is the name of the server where the share is located?).

When she then logs on to her client machine, surely she would need to log on as ANOTHER local account that is located on her client machine, which would be <clientcomputername>\Ashlie.Martin?

So if i'm right, there would be TWO accounts for that user, one located on the server (IMPACTSERVER01) and another on the client machine she is connecting from?

I suppose what i'm trying to get at here, is whether or not when one of your users logs on to their PC, do they log on to the PC itself, or to the WORKGROUP?

I can't remember how it works, as it's been so long since I dealt with a workgroup!!

I'll wait for your reply to that, and if you understand what I mean, then i'll continue...
0
 
TheTechnicalDoctorAuthor Commented:
Hang on, you might have something there.  I am not at the site, but when I get there I need to check that out.

Will get back to you
0
 
JohnjcesCommented:
Good one Pete!

I work on a domain.... things are "easier"! I'll bet that's it....

John
0
 
PeteJThomasCommented:
It's funny as I can't remember anything about workgroups, but I have a nagging thought that you need to create local accounts for each person on every machine they connect to, and the usernames and passwords have to be identical...

I could be barking up the the wrong tree completely (or just barking) but fingers crossed that's it!

I know what you mean John! You don't appreciate domains until you have to go back to a workgroup and try to get your head around it! lol
0
 
JohnjcesCommented:
Pete,

You are absolutely correct! If you want to access a resource on another PC in your workgroup, or even if it is not on your workgroup, you have to have that user's  logon name and password on that "server" or shared PC for files, folders and printers.

If a user changes a password, then you must change it on all the PCs that he/she accesses in that workgroup.

That's why a domain makes life a tad easier... and one forgets this stuff. (Age adds to that forgetfulness as well)!

John
0
 
PeteJThomasCommented:
Ah that's interesting... God workgroups must be a complete nightmare if you have a lot of client machines!

@TheTechnicalDoctor - In that case I would be willing to bet (famous last words) that your issue is simply that the password for the account IMPACTSERVER01\Ashlie.Martin is not the same as the password for <clientcomputername>\Ashlie.Martin...

If you find out what password the user actually logs on with, and reset the password for that user account on IMPACTSERVER01 so that it is identical, your problem will be solved!

The only problem I can come up with is that makes me wonder why adding the 'Everyone' group to the permissions on that share solved the problem... Unless somehow that allows Everyone regardless of Workgroup/username/password etc...?

Anyway no matter, it's worth a try whatever happens! :)
0
 
TheTechnicalDoctorAuthor Commented:
Ok, I have tried everything I can come up with and nothing has change.

However, I do have this observation that might be the key.  Ashlie never needs to sign on to the server.  Everyone else must enter their ID and password, she is never challenged.
0
 
TheTechnicalDoctorAuthor Commented:
Also, even though she can not open the folder, the shares active window show that a client is connected.  Is this strange or what?
0
 
PeteJThomasCommented:
Give me a little more time, i'll get back to you again! Shame that didn't work though... :(
0
 
PeteJThomasCommented:
Ok ok, i've thought up a couple more tests... (let me know if we've already done something like these before).

Go to another PC and create a local account for Ashlie.Martin and set exactly the same password again, and see if you can connect ok. (will be interesting to see if it's something to do with the account details etc or the PC you're connecting from).

If that works ok, try removing the particular PC you're trying all this on from the workgroup (i.e. just change the workgroup to a different name, then change it back again) and see if this makes any difference?

Clutching at straws here but SOMETHING's got to work!! :)
0
 
JohnjcesCommented:
Ya know, this is almost better than a good book! I am anxiously awaiting a fix too!
:)

John
0
 
PeteJThomasCommented:
lol, as long as this book has a happy ending! Perseverence/Patience is a practically a pre-requisite in this line of work these days... :)

Annoyingly, you can guarantee there's a bunch of experts out there who have never seen this question but could probably tell you what's wrong in as much time as it's taking me to write this...

I think i'd be a little deflated if someone came along and did that now though... :(
0
 
TheTechnicalDoctorAuthor Commented:
Ok, I have a solution  - sort of,,,,'

I tried everything and nothing was working.  I was browsing around the configurations and shares and noticed that Ashlie's Docs where open up Jennifer's ID (That's the person who had the machine before Ashlie).

I thought I had completely removed Jennifer via the user group, but something must have stuck in there.  When I put Jennifer's name in the permissions, everything worked!!!

I chalk this one up to the great MS workgroup code not cleaning up after itself.

Thanks for all the help.
0
 
TheTechnicalDoctorAuthor Commented:
Excellent help from all.  Wish I could have given all that helped 500 points.
0
 
JohnjcesCommented:
I'm glad you found it!

I'll remember this one.

John
0
 
PeteJThomasCommented:
HaHa! I'm very glad you found it too! What a strange problem to have! :)
0
 
TheTechnicalDoctorAuthor Commented:
Strange ain't the word for it.  The good news is they contract with me and I get paid by the hour.
0
All Courses

From novice to tech pro — start learning today.