Samba problem with just one Windows client
I run Samba on my Slackware Linux system. All our client computers except one can access the Samba shares OK. On the one that fails it connects OK and the network drive icon appears but when you click on the icon you get a message saying:- E: Access is Denied The same user can connect successfully from other computers on the network. We've checked all the obvious things like the client system is in the right workgroup and the IP address is right at both ends. Other things work fine (HTTP, telnet, etc.) A "net use E: \\server\homes" returns success but if you then try to go to drive E: you get "Access is denied". What are we missing? -- Chris Green (chris@areti.co.uk) "Never ascribe to malice that which can be explained by incompetence."
On Fri, Jan 06, 2006 at 12:03:04AM +0000, Steve Fosdick wrote:
On Thu, 5 Jan 2006 22:31:50 +0000
What are we missing?
Are you using encrypted passwords? Is the service pack level of the manfunctioning machine the same as the others?
You're thinking down the same routes as us. Yes, we are using encrypted passwords but it's been that way for a long time now (several months). As far as I know the machine which doesn't work is at the same level as the (only) other Win2k machine. The error seems to have arisen recently, some files were saved on a Samba shared drive from that machine just before Christmas. Now it doesn't work. We're racking our brains to think of something that's changed but really can't think of anything. It's a very odd error as the shared drive icon appears indicating everything is OK but you can't actually access the files on the shared drive. -- Chris Green (chris@areti.co.uk) "Never ascribe to malice that which can be explained by incompetence."
On Fri, 2006-01-06 at 08:45 +0000, Chris Green wrote:
We're racking our brains to think of something that's changed but really can't think of anything. It's a very odd error as the shared drive icon appears indicating everything is OK but you can't actually access the files on the shared drive.
It's very odd that the same user works from another machine, other than that it sounds like a problem with the smbpasswd > passwd mapping. I assume you are not running Samba in DC mode ? At the point of authentication is there anything funny appearing in Samba's logs (I am guessing that you don't see the actual failure but I am just wondering if there are any clues before that) You could try turning off encrypted passwords on the 2k machine as a test (I am not suggesting you leave it like that). The best way to do this (a lot of people seem to resort to hacking about in the registry) is through Admin Tools, Local Security Policy, Security Settings, Local Policies, Security Options, Enable "Send unencrypted passwords to 3rd party SMB Servers"
On Fri, Jan 06, 2006 at 09:38:25AM +0000, Wayne Stallwood wrote:
On Fri, 2006-01-06 at 08:45 +0000, Chris Green wrote:
We're racking our brains to think of something that's changed but really can't think of anything. It's a very odd error as the shared drive icon appears indicating everything is OK but you can't actually access the files on the shared drive.
It's very odd that the same user works from another machine, other than that it sounds like a problem with the smbpasswd > passwd mapping.
I assume you are not running Samba in DC mode ?
What's that? As I don't know what it is I doubt if I am running Samba in DC mode.
At the point of authentication is there anything funny appearing in Samba's logs (I am guessing that you don't see the actual failure but I am just wondering if there are any clues before that)
No, I looked at the logs, I can't see any difference between the connections that work from other machines and the one that fails.
You could try turning off encrypted passwords on the 2k machine as a test (I am not suggesting you leave it like that). The best way to do this (a lot of people seem to resort to hacking about in the registry) is through Admin Tools, Local Security Policy, Security Settings, Local Policies, Security Options, Enable "Send unencrypted passwords to 3rd party SMB Servers"
OK, thanks, I might try that. -- Chris Green (chris@areti.co.uk) "Never ascribe to malice that which can be explained by incompetence."
Chris Green wrote: [SNIP] Chris, Have you installed SP2 for W2K recently? Cheers, Laurie. -- -------------------------------------------------------------------- Laurie Brown laurie@brownowl.com --------------------------------------------------------------------
On Fri, Jan 06, 2006 at 11:10:07AM +0000, Laurie Brown wrote:
Chris Green wrote:
[SNIP]
Chris,
Have you installed SP2 for W2K recently?
It's Ben's (my son's) machine that has the problem, I'll ask him but I don't think he's installed any upgrades recently. -- Chris Green (chris@areti.co.uk) "Never ascribe to malice that which can be explained by incompetence."
On 1/6/06, Chris Green <chris@areti.co.uk> wrote:
On Fri, Jan 06, 2006 at 11:10:07AM +0000, Laurie Brown wrote:
Have you installed SP2 for W2K recently?
It's Ben's (my son's) machine that has the problem, I'll ask him but I don't think he's installed any upgrades recently.
The latest service pack for Windows 2000 is SP4. Certainly XP SP2 changed a large number of security settings, but this hasn't stopped such PCs talking to Samba servers. Tim.
Tim Green wrote:
On 1/6/06, Chris Green <chris@areti.co.uk> wrote:
On Fri, Jan 06, 2006 at 11:10:07AM +0000, Laurie Brown wrote:
Have you installed SP2 for W2K recently?
It's Ben's (my son's) machine that has the problem, I'll ask him but I don't think he's installed any upgrades recently.
The latest service pack for Windows 2000 is SP4. Certainly XP SP2 changed a large number of security settings, but this hasn't stopped such PCs talking to Samba servers.
SP4! That's the one! Goes to show how much I use Window$ these days... Anyway, similar changes to those required by XP Pro are required on W2K SP4. A google will help you there. There're registry changes and some group policy changes required. Cheers, Laurie. -- -------------------------------------------------------------------- Laurie Brown laurie@brownowl.com --------------------------------------------------------------------
On Fri, 2006-01-06 at 18:05 +0000, Laurie Brown wrote:
There're registry changes and some group policy changes required.
One or the other should do as per my previous post, that said I am sure you can get it to work with recent version of samba without, certainly I have had win2k sp4 and XP sp2 machines connecting to samba before without such modifications. The last time I had to use it was with VisionFS (shudder) on a SCO box (shudder some more) Personally I prefer to do it through the policy because it's cleaner.
On Fri, Jan 06, 2006 at 09:54:39AM +0000, Chris Green wrote:
At the point of authentication is there anything funny appearing in Samba's logs (I am guessing that you don't see the actual failure but I am just wondering if there are any clues before that)
No, I looked at the logs, I can't see any difference between the connections that work from other machines and the one that fails.
Try incrementaly turning up the loglevel, by the time you get to "debug" it should become apparent what the problem is. Just be warned that you can end up using *lots* of space as the Samba logs can be quite verbose. Thanks Adam -- jabberid = quinophex@jabber.earth.li AFFS || http://www.affs.org.uk/ || Not a filesystem
On Fri, 2006-01-06 at 09:54 +0000, Chris Green wrote:
I assume you are not running Samba in DC mode ?
What's that? As I don't know what it is I doubt if I am running Samba in DC mode.
Samba can operate as a Windows Domain Controller (therefore amongst other things managing Windows client logons and authentication) but you're right, you would know if you were using it :-)
participants (6)
-
Adam Bower -
Chris Green -
Laurie Brown -
Steve Fosdick -
Tim Green -
Wayne Stallwood