I've been very frustrated with getting XP to connect to samba. I added a machine account on Linux useradd -g workstation -d /dev/null -s /bin/false xpmachine$ then pdbedit -a -m -u xpmachine on XP i change the name to xpmachine and connect as root. I'm welcomed into my domain as expected When I reboot I cannot login because my account isn't recognized although I can login as administrator and browse, map etc. The Samba log says no account exists for XPMACHINE$ (uppercase) even though it's lowercase in pdbedit and /etc/passwd. In XP you can't change the machine name case but you can change from a domain to a workgroup, then back again and go to uppercase... and now I can login to my domain!! Until it breaks again and I have to do this all over again. I've looked at every registry tweak I can find. Everything I read says machine accounts are not case sensitive. Is there any setting, either in Samba or XP that will put an end to this? Thanks winxp (fresh install updated to sp2) samba-3.0.10-1.fc2.i386.rpm (tdbsam backend)
On Mon, 2005-11-07 at 18:36 -0500, Tom Conway wrote:> I've been very frustrated with getting XP to connect to samba. > I added a machine account on Linux > useradd -g workstation -d /dev/null -s /bin/false xpmachine$ > then pdbedit -a -m -u xpmachine > on XP i change the name to xpmachine and connect as root. > I'm welcomed into my domain as expected > When I reboot I cannot login because my account isn't recognized > although I can login as administrator and browse, map etc. > > The Samba log says no account exists for XPMACHINE$ (uppercase) even > though it's lowercase in pdbedit and /etc/passwd. > > In XP you can't change the machine name case but you can change from a > domain to a workgroup, then back again and go to uppercase... and now I > can login to my domain!! Until it breaks again and I have to do this all > over again. I've looked at every registry tweak I can find. Everything > I read says machine accounts are not case sensitive. Is there any > setting, either in Samba or XP that will put an end to this? > > Thanks > winxp (fresh install updated to sp2) > samba-3.0.10-1.fc2.i386.rpm (tdbsam backend)---- Just in case because I may misunderstand what you are saying... machine accounts are trust accounts but they aren't a user account and you can't log in as you would with a user account. 1 - you seem to be making this way too difficult. You should have appropriate scripts for adding users and adding machine accounts to domain. Machine accounts should be created on the fly with the right script. I've never considered fooling with machine accounts in pdbedit but perhaps there are reasons for doing so. 2 - Suggest that you work through one of the 'By Example' of John's excellent documentation, perhaps chapter 2... http://us3.samba.org/samba/docs/man/Samba-Guide/small.html Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
On Tue, 2005-11-08 at 06:53 -0700, SRS0+gsMU+45 +tecsol.org=tconway@mail15.alevelhigher.com wrote:> by www.tecsol.org with HTTP; Tue, 08 Nov 2005 08:27:36 -0500> > Thanks Craig, I appreciate your input. I'm not trying to login as a > machine account and I understand what they're for. I haven't used the > on the fly add scripts. They used to be very unreliable. Most Samba > howtos have you add users and machines using smbpasswd (I've tried both > pdbeidt and smbpasswd). I will look at the howto you've suggested. > > I can only assume that the on-the-fly scripts pass the same parameters to > smbpasswd and are there to make the admins lifer easier.=20 > > My bottom line is why would a machine that worked fine yesterday, stop > working today. Then simply fiddling with the machine accounts, make it > work again?---- hmmm...alevelhigher.com - you must be somewhere in Phoenix ;-) let's keep this on list if you don't mind...there are a lot of brighter minds than mine and off list cheats you from their benefit and makes it so no one else can benefit from your ultimate resolution. There were too few details for anyone to really 'know' what the issue is. Generally, the things that come to mind when it works for a while then doesn't work are things like cache's which get cleared or services that get restarted over night. My first thought is that system is having trouble locating PDC (is WINS functional on server and browseable from workstation?) Do you have other Windows systems that are locating PDC? My second thought are things like nscd (name server caching daemon), are you using it? Is it working, is it causing issues? My third thought is verifying accounts and access directly on samba server from command line... getent passwd |grep NAME_OF_USER smbclient -L NAME_OF_SAMBA_SERVER -U NAME_OF_USER You can always set loglevel higher (level 10 will debug a whole lot of stuff but should always tell you what is breaking). Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.