Hello,

I am running Slackware 10.1 w/ the 2.6.12.5 kernel, and Samba 3.0.14a. Until recently, the Samba share that I had created between my Slackware and Windows XP boxes was working properly. Now, I keep receiving the following error message when trying to connect to my share via my Windows machine:

Logon Failure: The target account name is incorrect.

I have not changed either the username or password with which I was connecting, and have removed and created my Samba account on my Slackware machine using the same settings as before. I have had limited success with removing and installing Samba, and after a kernel recompile my share was accessible to Windows for a few days w/o any problems, until now. I am perplexed about this, so if anyone could shed some light on this issue for me I would be grateful. Thank you.

The way i see it there are two possible basic things that can go wrong:

1) the linux box is not sharing samba
2) the windows box is not authenticating itself properly.

Although the fact that it occured after a kernel recompile may tell us something. That said it was a few days.

Anyway, my first advice would be to try a different windows machine. and in that way you can isolate where the problem actually lies.

I haven't heard too much about different kernel versions having an effect on samba. Unless you somehow disabled support for something in the kernel.

I presume you have also tried creating a NEW samba user. Also what level of security are you using? if it's server or domain, you didn't change your windows username did you?

ps this post should be in networking!

I have tried creating different users, but this does not seem to resolve anything. What's interesting is that after being logged on to my Windows machine for some time, I am able to access my Samba share. After rebooting, however, I am locked out, receiving the error mentioned in my original post. But, I do not beleive that it is machine-centric, since I have tried other machines on the network and am unable to log into my Smaba share as well. I'll have to keep looking for an answer to this.