similar to: new user cannot logon to one computer in the domain

I have a very strange problem and I'm doomed. In a samba-domain with XP-clients certain users cannot logon to some computers. The user tries to logon but *immediately* gets the message "you cant get logged on. please check username and domain and retype your password" (translated from german) on the XP-machine. In the samba-logs (Loglevel=2) it says: [2009/05/19 16:47:16, 2]

I'm just migrating a medium sambainstallation from old samba2.2.8 to new samba 3.0. The server is acting as PDC and there is no BDC. The new samba is based on LDAP and is already successfully tested. Now I need to transfer the whole old smbpasswd to the new ldap-style to convert users and machines with minimal effort. Especially I dont want to break the relations between the machines and

Hi, plese have you some idea for this problem? thanks, Lukas -- ---------- Forwarded message ---------- Date: Wed, 30 Sep 2009 23:09:59 +0200 (CEST) From: extmaillist at linuxbox.cz To: pilsl at goldfisch.at, Volker.Lendecke at SerNet.DE Cc: samba at lists.samba.org X-Spam-Score: -1.0 (), 4 required Subject: Re: [Samba] user cannot logon to domain although log says "auth

I'm thinking about upgrading our NT4-clients to XP in the near future and I want to know how well XP is supported by SAMBA in the recent samba-versions. I found many single statements in usenet, but I wonder if there is a kind of XP-FAQ out there. (The one at samba-page is very outdated) Especially I need to know how well XP integrates in a existing NT4-domain (samba as PDC). Then I need

I'm just migrating a whole samba-installations ffrom old 2.2 to 3.0 with LDAP. I was successfully able to migrate all useraccounts with smbldap-useradd but now I'm stuck with the machine-accounts. All machines are part of the domain and they should be able to logon the new server without noticing any difference. I can add them with smbldap-useradd -w but the resulting ldap-entry does

By now we had running samba as PDC and fileserver for about 20 NT4-clients with roaming profiles. Now we start migrating NT4-clients to XP-clients and as I found out roaming userprofiles between XP and NT4 is not possible (NT4->XP works, but not vice versa). So I just thought about cloning all the profiles (docs and mails are not in the profiles so only bookmarks, adressbook and

Months ago there was a thread here about the implementation of a simple undelete-function (i.e: dont delete files, but move them to a folder). Is this this still a relevant idea or has this feature low priority ? thanx, peter ps: anyone knows about a 3rd-party software (propably on nt-side) that implements such a feature ? -- mag. peter pilsl phone: +43 676 3574035 fax : +43 676 3546512

A productional system (linux) running samba 2.2.5 runs 'cracy' from yesterday. There are lot of 'odd' behaviours. People cant logon or cant logoff. Access to files fails. Examining the logs the most eyecatching events are: (not that the keynumber started at 959 and went slowly down. I did not wait until it goes to zero and let the user reboot its machine before) Any idea ? thnx,

while looking for a solution for webbased access to our samba-servers I found a recommendation towards using DAV instead. I just took a first glance at DAV (www.webdav.org) and find it very interesting. Are there any documentes comparing these two strategies in intranet and internet (speed, reliability ...) I would also be greatly interested if anyone here uses DAV to allow roaming users to

samba2.07,nt4sp6a I run a samba-server with 15nt-clients on a 100MBit-Switch. Now I faced extremely poor performance and really have no idea why. I even dont know if it can be a samba-problem. When copying myriads of small file from a client to the server or vice versa I get bad performance: 1000 files a 16kb: ~80seconds = 200kb/second But this is highspeed compared to copying from nt to nt:

I'm using samba 2.2.3a as fileserver and domaincontroller for 12 NT4-clients (sp6a) and occassionally - when a user tries to logon - there comes the following messages on the nt-client: - No Windows NT Domain Controller is available for domain XXXX. There are currently no logonservers available to service the logonrequest. - and - server-side profile not available. The OS tries to log you on

When syncing huge data-folders (~50GB) with a remote server on a daily base I frequently (every 2nd to 3rd time) get the following error: Read from remote host goldfisch.at: Connection timed out rsync: writefd_unbuffered failed to write 4092 bytes: phase "unknown" [generator]: Broken pipe (32) rsync error: error in rsync protocol data stream (code 12) at io.c(1099) rsync error:

hi, i've tried all the modifications i-ve found to login with Windows XP Pro client on a Samba Server as PDC but nothing have worked. what else could i do or did i do something wrong ? modif. : -in regedit : HKEYLOCALMACHINE\...\Parameters\requiresignorseal -> 0 -in regedit : HKEYLOCALMACHINE\...\Parameters\signsecurechannel -> 0 i added : - in regedit :

I have a handful of machines with all of the latest windows updates, and the WinXP reghack wont stay. If I enter the EnablePlainTextPassword reghack, and reboot, all is fine, until the machine is logged off or rebooted, then it reverts back to EnablePlainTextPassword=no Seems to be only affected on machines using Novell 4.83.6 SP1 client... although something else could be the cause. Machines

Hello everyone! I'm facing a big problem with the samba server I just set up: System: FreeBSD 5.4 Samba ver: 3.0.20 (previuosly 3.0.12) Client(s): Windows XP Professional I configured the server to make use of roaming profiles. I was able to copy local profiles to the server, to login and voila - got my desktop. Also after creating a new user, the new profile gets copied to the server,

I had the same problem. We used samba 3.0.14 and upgraded to 3.0.20 After that profile were not loaded anymore. Th problen you are discribing looks like Windows is loading the local copy of your profile and after you deleted it it tries to load the profile from samba and fails. I found out that we had problems with "profile acls = Yes" wich was needed by the earlier samba releases.

Is there nobody who can help me :-( -----Oorspronkelijk bericht----- Van: samba-bounces+louis=van-belle.nl@lists.samba.org [mailto:samba-bounces+louis=van-belle.nl@lists.samba.org] Namens Louis van Belle Verzonden: woensdag 14 september 2005 17:08 Aan: samba@lists.samba.org Onderwerp: [Samba] XP Profile write ok, no read. Hi, I still have a problem with samba and profiles. The profile is

Hi I actually had this same problem when running up samba originally. Check that the user has a valid unix acount and that you have added that to the folder share/valid users section. B -----Original Message----- From: Tony Ricker [mailto:rickera2@SLU.EDU] Sent: Friday, 15 March 2002 5:21 AM To: David Brodbeck Cc: Samba Subject: Re: [Samba] Some users can't log in -- server shows

Yes, if you're using roaming profiles Vista will automatically accept your login (if your PDC is configured correctly, check the firewall on the clients and server also, write/read access to the profile for the current user, but i guess these things were already said here but I'm only replying to your last question without having read most of the rest) The profile is not needed to be

After being content with an old laptop running XP for years, my job decided to provide me with a shiny new one running Windows 7 Professional. The biggest problem with this is that I can't get the Windows 7 box to login to my Samba NT4-style domain controller. I have upgraded samba from 3.0.33 to 3.6.23, and copied my smbpasswd file to where the new samba expects to find it in