Chris Green
2006-Jan-06 10:07 UTC
[Samba] "Access is denied" after connection is apparently successful
We have a small home network with Samba running on a Slackware Linux
10.1 system, it's been running happily for several months or even
maybe a year or so. It's running Samba version 3.0.4
Recently one of the Win2k clients is getting errors when trying to
access Samba shares. The other clients are all still working OK and
the same user can access shares from other client machines.
Running the command:-
net use e: \\server\tmp
works, i.e. one gets "command completed successfully", however if you
try and go to drive E: or access any files there it gives an "Access
is denied" message.
Similarly with the GUI an icon appears for drive E: with no red cross
but the moment you try and access drive E: a pop-up message says "E:
Access is Denied".
We can't think of anything that has changed on the client machine
where the error occurs, can anyone suggest what the problem might be?
--
Chris Green (chris@areti.co.uk)
"Never ascribe to malice that which can be explained by
incompetence."
Chris Green
2006-Jan-07 14:57 UTC
[Samba] Re: "Access is denied" after connection is apparently successful
On Fri, Jan 06, 2006 at 10:07:41AM +0000, Chris Green wrote:> We have a small home network with Samba running on a Slackware Linux > 10.1 system, it's been running happily for several months or even > maybe a year or so. It's running Samba version 3.0.4 > > Recently one of the Win2k clients is getting errors when trying to > access Samba shares. The other clients are all still working OK and > the same user can access shares from other client machines. > > Running the command:- > net use e: \\server\tmp > > works, i.e. one gets "command completed successfully", however if you > try and go to drive E: or access any files there it gives an "Access > is denied" message. > > Similarly with the GUI an icon appears for drive E: with no red cross > but the moment you try and access drive E: a pop-up message says "E: > Access is Denied". > > We can't think of anything that has changed on the client machine > where the error occurs, can anyone suggest what the problem might be? >Was this just a silly question or does no one have any suggestions? -- Chris Green (chris@areti.co.uk) "Never ascribe to malice that which can be explained by incompetence."