Re: [Samba] Samba and XP
Vo Dai Chuyen wrote: What for ? I think that most people that talk about this are interested in making XP into a domain controller. Which generally means they are a Windows user who doesn't want to spend money, or a *nix zealot who objects in principle to a proper windows server, either way it tends to be bad news. *Michael Heydon - IT Administrator * [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and XP
Deon Steyn wrote: Is it possible to run Samba on Xp Pro I think a better question is - why? I see from your previous posting that you've had Samba running under XP via Cygwin. Why use Samba, when Windows has SMB/CIFS support built in? -- Curtis Maloney [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and XP
On Tue, Jun 10, 2008 at 09:38:37PM +0200, Deon Steyn wrote: Is it possible to run Samba on Xp Pro No. Volker pgpd8IReIbNeT.pgp Description: PGP signature -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and XP
On Tue, Jun 10, 2008 at 09:38:37PM +0200, Deon Steyn wrote: Is it possible to run Samba on Xp Pro No. You could run Samba in a *nix VM sitting on top of a XP host. Performance is going to suck, but it can be done. Greg -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and XP
What for ? 2008/6/11 Greg J. Zartman, P.E. [EMAIL PROTECTED]: On Tue, Jun 10, 2008 at 09:38:37PM +0200, Deon Steyn wrote: Is it possible to run Samba on Xp Pro No. You could run Samba in a *nix VM sitting on top of a XP host. Performance is going to suck, but it can be done. Greg -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and XP
Greg J. Zartman, P.E. wrote: On Tue, Jun 10, 2008 at 09:38:37PM +0200, Deon Steyn wrote: Is it possible to run Samba on Xp Pro No. You could run Samba in a *nix VM sitting on top of a XP host. Performance is going to suck, but it can be done. Greg If you go this route, make sure to set XP performance setting for background services rather than programs. OT: *rant* /I'll never understand Windows memory management... it seems like the more hardware you throw at it, the less it uses. I've had programs that I haven't used hours cached in memory while I'm just short of thrashing with VMs running, and by the sounds of the harddrive it's not doing much of a read ahead. Sorry, just wasted about an entire day babysitting virtual machines that moved at the same pace with 256 MB RAM as a full gig, since they were starved while RAM essentially sat idle. I/O bound for linear reads on separate channels, and yet a gig of RAM sits as cache for stale programs from hours ago/. */rant* -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba PDC - XP Client refuses to join!
smc1:/var/lib/samba # cat /etc/samba/smb.conf # smb.conf is the main Samba configuration file. You find a full commented # version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the # samba-doc package is installed. # Date: 2007-12-04 [global] workgroup = SUSSEXMC netbios name = SMC1 server string = Samba PDC time server = Yes domain logons = Yes domain master = Yes preferred master = Yes wins support = Yes os level = 65 #map acl inherit = Yes passdb backend = ldapsam:ldap://localhost ldap suffix = dc=sussexmc,dc=com ldap admin dn = cn=admin,dc=sussexmc,dc=com ldap user suffix = ou=People ldap group suffix = ou=Groups ldap machine suffix = ou=Computers ldap passwd sync = Yes log file = /var/log/samba/log.%m log level = 1 max log size = 50 syslog = 0 security = user encrypt passwords = true Dos charset = 850 unix charset = LOCALE preserve case = yes short preserve case = yes case sensitive = no interfaces = eth0, lo bind interfaces only = Yes enable privileges = Yes username map = /etc/samba/smbusers name resolve order = wins bcast hosts printcap name = CUPS printing = cups printer admin = root passwd program = /usr/sbin/smbldap-passwd -u %u add machine script = /usr/sbin/smbldap-useradd -w %u add user script = /usr/sbin/smbldap-useradd -m %u delete user script = /usr/sbin/smbldap-userdel %u add group script = /usr/sbin/smbldap-groupadd -p %g delete group script = /usr/sbin/smbldap-groupdel %g add user to group script = /usr/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/sbin/smbldap-usermod -g %g %u socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 [homes] comment = '%u' browseable = no writable = yes public = no create mask = 0600 directory mask = 0700 [sysvol] path = /var/lib/samba/netlogon read only = no [netlogon] comment = Network Logon Service path = /var/lib/samba/netlogon/sussexmc.com/scripts guest ok = yes browsable = no writable = no ;root preexec = /usr/bin/ntlogon -u %U -g %G -o %a -d /var/lib/samba/netlogon/sussexmc.com/scripts ;root postexec = rm -f /var/lib/samba/netlogon/sussexmc.com/scripts/%U.bat [Profiles] path = /var/lib/samba/profiles browseable = no guest ok = yes create mask = 0600 directory mask = 0700 [EMAIL PROTECTED] wrote: paste your smb.conf Hi all, I have been setting up a samba3 domain controller, all seems to work fins on the samba side, until i try to join a workstation to the domain. From a windows XP client, the following happens... Enter computer properties, computer name tab... click Change... Enter SUSSEXMC.COM in the domain box, click ok Now is where things start going wrong.. XP waits for a little while, before responding with: A Domain Controller for the domain SUSSEXMC.COM could not be contacted Clicking details reveals: DNS was succesfully queried for the service location (SRV) resource record used to locate a domain controller for the domain: SUSSEXMC.COM The query was for the SRV record for _ldap._tcp.dc._msdcs.SUSSEXMC.COM The following domain controllers were identified by the query: smc1.sussexmc.com Common causes of this error include: - Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses - Domain controllers registered in DNS are not connected to the network or are not running. Now ALL using the same XP client... I can verify that the A records are correct using nslookup (Server ip is 10.10.1.1, reported by DNS server at 10.10.1.1 (Also the machine gets its IP address from DHCP on the same server, and this correctly updates the forward and reverse dns zones to reflect this)) I can also verify the DC is running, as if i manually enter \\smc1 or \\smc1.sussexmc.com into windows explorer (the first time) i am prompted for a username/password (and providing valid credntials allows me to logon and see the main shares on the PDC (sysvol, netlogon, printers), as well as the users home folder). What am I missing?? James -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba PDC - XP Client refuses to join!
in your previous email why are you trying to join the domain SUSSEXMC.COM when in your smb.conf it is just SUSSEXMC? on my computer properties, computer name, change, type in SUSSEXMC in the domain box. James Tandy wrote: smc1:/var/lib/samba # cat /etc/samba/smb.conf # smb.conf is the main Samba configuration file. You find a full commented # version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the # samba-doc package is installed. # Date: 2007-12-04 [global] workgroup = SUSSEXMC netbios name = SMC1 server string = Samba PDC time server = Yes domain logons = Yes domain master = Yes preferred master = Yes wins support = Yes os level = 65 #map acl inherit = Yes passdb backend = ldapsam:ldap://localhost ldap suffix = dc=sussexmc,dc=com ldap admin dn = cn=admin,dc=sussexmc,dc=com ldap user suffix = ou=People ldap group suffix = ou=Groups ldap machine suffix = ou=Computers ldap passwd sync = Yes log file = /var/log/samba/log.%m log level = 1 max log size = 50 syslog = 0 security = user encrypt passwords = true Dos charset = 850 unix charset = LOCALE preserve case = yes short preserve case = yes case sensitive = no interfaces = eth0, lo bind interfaces only = Yes enable privileges = Yes username map = /etc/samba/smbusers name resolve order = wins bcast hosts printcap name = CUPS printing = cups printer admin = root passwd program = /usr/sbin/smbldap-passwd -u %u add machine script = /usr/sbin/smbldap-useradd -w %u add user script = /usr/sbin/smbldap-useradd -m %u delete user script = /usr/sbin/smbldap-userdel %u add group script = /usr/sbin/smbldap-groupadd -p %g delete group script = /usr/sbin/smbldap-groupdel %g add user to group script = /usr/sbin/smbldap-groupmod -m %u %g delete user from group script = /usr/sbin/smbldap-groupmod -x %u %g set primary group script = /usr/sbin/smbldap-usermod -g %g %u socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 [homes] comment = '%u' browseable = no writable = yes public = no create mask = 0600 directory mask = 0700 [sysvol] path = /var/lib/samba/netlogon read only = no [netlogon] comment = Network Logon Service path = /var/lib/samba/netlogon/sussexmc.com/scripts guest ok = yes browsable = no writable = no ;root preexec = /usr/bin/ntlogon -u %U -g %G -o %a -d /var/lib/samba/netlogon/sussexmc.com/scripts ;root postexec = rm -f /var/lib/samba/netlogon/sussexmc.com/scripts/%U.bat [Profiles] path = /var/lib/samba/profiles browseable = no guest ok = yes create mask = 0600 directory mask = 0700 [EMAIL PROTECTED] wrote: paste your smb.conf Hi all, I have been setting up a samba3 domain controller, all seems to work fins on the samba side, until i try to join a workstation to the domain. From a windows XP client, the following happens... Enter computer properties, computer name tab... click Change... Enter SUSSEXMC.COM in the domain box, click ok Now is where things start going wrong.. XP waits for a little while, before responding with: A Domain Controller for the domain SUSSEXMC.COM could not be contacted Clicking details reveals: DNS was succesfully queried for the service location (SRV) resource record used to locate a domain controller for the domain: SUSSEXMC.COM The query was for the SRV record for _ldap._tcp.dc._msdcs.SUSSEXMC.COM The following domain controllers were identified by the query: smc1.sussexmc.com Common causes of this error include: - Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses - Domain controllers registered in DNS are not connected to the network or are not running. Now ALL using the same XP client... I can verify that the A records are correct using nslookup (Server ip is 10.10.1.1, reported by DNS server at 10.10.1.1 (Also the machine gets its IP address from DHCP on the same server, and this correctly updates the forward and reverse dns zones to reflect this)) I can also verify the DC is running, as if i manually enter \\smc1 or \\smc1.sussexmc.com into windows explorer (the first time) i am prompted for a username/password (and providing valid credntials allows me to logon and see the main shares on the PDC (sysvol, netlogon, printers), as well as the users home folder). What am I missing?? James -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba PDC - XP Client refuses to join!
paste your smb.conf Hi all, I have been setting up a samba3 domain controller, all seems to work fins on the samba side, until i try to join a workstation to the domain. From a windows XP client, the following happens... Enter computer properties, computer name tab... click Change... Enter SUSSEXMC.COM in the domain box, click ok Now is where things start going wrong.. XP waits for a little while, before responding with: A Domain Controller for the domain SUSSEXMC.COM could not be contacted Clicking details reveals: DNS was succesfully queried for the service location (SRV) resource record used to locate a domain controller for the domain: SUSSEXMC.COM The query was for the SRV record for _ldap._tcp.dc._msdcs.SUSSEXMC.COM The following domain controllers were identified by the query: smc1.sussexmc.com Common causes of this error include: - Host (A) records that map the name of the domain controller to its IP addresses are missing or contain incorrect addresses - Domain controllers registered in DNS are not connected to the network or are not running. Now ALL using the same XP client... I can verify that the A records are correct using nslookup (Server ip is 10.10.1.1, reported by DNS server at 10.10.1.1 (Also the machine gets its IP address from DHCP on the same server, and this correctly updates the forward and reverse dns zones to reflect this)) I can also verify the DC is running, as if i manually enter \\smc1 or \\smc1.sussexmc.com into windows explorer (the first time) i am prompted for a username/password (and providing valid credntials allows me to logon and see the main shares on the PDC (sysvol, netlogon, printers), as well as the users home folder). What am I missing?? James -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba - Win XP authentication failure
OK it is solved... It was Zonealarm. It took some time to figure it out although it was not that difficult... Daniel -- View this message in context: http://www.nabble.com/Samba---Win-XP-authentication-failure-tp14593586p14595942.html Sent from the Samba - General mailing list archive at Nabble.com. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba with XP Client: The user name could not be found
Monte L. Early wrote: I am trying to connect an XP Pro workstation to a Samba server configured as PDC. I can access shares from the XP client by simply mapping the resource and entering login/pass. However, whenever I attempt to connect to the domain, it gives me the error: The user name could not be found. I am using the same user name in Samba, Linux and XP. Any suggestions? Have you tried profile acls = yes in smb.conf? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba with XP Client: The user name could not be found
Ah, if you are attempting to join the domain, then it could be that the user name has not been set up properly. Samba can map Windows users if the names are different or use the Windows name if it is the same as a Unix name (handy in XP Home workstations which don't have domain logins). Have you joined the computer to the domain? Have you set up the Windows user account on the Samba server? Have you enabled the Windows user account on the Samba server? Monte L. Early wrote: I just tried that and it and I am getting the same error when I attempt to join the domain. - Original Message - From: Gary Dale [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Friday, February 09, 2007 1:03 PM Subject: Re: [Samba] Samba with XP Client: The user name could not be found Monte L. Early wrote: I am trying to connect an XP Pro workstation to a Samba server configured as PDC. I can access shares from the XP client by simply mapping the resource and entering login/pass. However, whenever I attempt to connect to the domain, it gives me the error: The user name could not be found. I am using the same user name in Samba, Linux and XP. Any suggestions? Have you tried profile acls = yes in smb.conf? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA - Windows XP Long Filenames
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/04/2006 05:07 AM, Alex Howe escreveu: Hello I have a Debian Sarge Server http://www.linuxforums.org/forum/# running samba with two Disks. The first disk has the OS on it with all home directories etc. in other words (/). The second disk has a partition called /work mounted on it used as a shared repository for Windows xp http://www.linuxforums.org/forum/# clients. The problem I have is when a file with a long filename (65 chrs) is copied from an xp machine to /work I get an xp error of filename too long, but when I copy the same file to /home (which is on the other disk http://www.linuxforums.org/forum/#) it works fine. I have carried out a few tests i.e creating a directory within /home with the same file path length as the offending directory in /work to see if I can replicate the problem, and I can't. The same WinXP client is able to write the long file name in any share which path is inside /home? The two disks are providing different results. Has anybody experienced a similar problem? Maybe a special mount option needs to be specified within /etc/fstab. I can't seem to find any answers!!! That's quite strange. Are you using different filesystems? Are you using different mount options? Any help is appreciated Also, a not-directly-related information about long filenames: http://lists.samba.org/archive/linux-cifs-client/2006-March/001230.html Thanks Kind regards, - -- Felipe Augusto van de Wiel [EMAIL PROTECTED] Coordenadoria de Tecnologia da Informação (CTI) - SEDU/PARANACIDADE http://www.paranacidade.org.br/ Phone: (+55 41 3350 3300) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFFK7VFCj65ZxU4gPQRAhbCAKDNu2kYNXOfH61Si9Ook+r6j2rW0gCeJCd+ tzUKZrx/E84TpUjEpoi2qYA= =fsUg -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
RE [Samba] Samba, win xp and acls
Hi, [EMAIL PROTECTED] a écrit sur 04/08/2005 17:26:59 : Hello all, I'm working and searching for a few days to obtain this result : * I want to share some directories between differents users and groups (windows XP clients) using a minimum but efficient configuration with samba and posix acls. * I would like that users windows configuration stay on locals machines (no roaming accounts), * When registering users and computers on the domain, users must keep there configuration, * I want to manage users and groups using srvtools.exe I use tdbsam, posix acls work fine and samba (3.0.14a) runs as a PDC. My problems are : * On windows (with administrator account), some directories don't have the acl (security) panel, * On other directories, the panel is present but I cannot modify permissions, If you specify that the admin user is root, the administrator user don't have the right to admin the system. * Users configurations are never stored locally, * Creating new users with srvtools not possible, * How to keep old users windows configuration when entering the domain ? * No way to find a good tutorial answering my needs... SAMBA-HOWTO-COLLECTION and samba by-example in samba web-site Here is my configuration : smb.conf : [global] interfaces = 192.168.1.120/24 enable privileges = yes nt acl support = yes security = user netbios name = FSERVER workgroup = FWSERVER passdb backend = tdbsam server string = File Server add user script = /usr/sbin/useradd -m '%u' add group script = /usr/sbin/groupadd '%g' add user to group script = /usr/sbin/usermod -G '%g' '%u' add machine script = /usr/sbin/useradd -s /bin/false -d /dev/null '%u' logon script = scripts\logon.bat logon path = logon drive = H: domain logons = yes username map = /etc/samba/smbusers admin users = root socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=4096 SO_RCVBUF=4096 encrypt passwords = yes wins support = yes os level = 50 domain master = yes local master = yes preferred master = yes name resolve order = lmhosts host wins bcast preserve case = yes short preserve case = yes unix password sync = yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n . [public] writable = yes path = /share/public public = yes create mode = 0777 directory mask = 0777 admin users = root nt acl support = yes [technique] writable = yes path = /share/technique public = no create mode = 0770 directory mask = 0770 valid users= @technique, @admins admin users = root nt acl support = yes [stagiaires] writable = yes path = /share/stagiaires public = no create mode = 0770 directory mask = 0770 valid users= @stagiaires, @admins admin users = root nt acl support = yes [secretariat] writable = yes path = /share/secretariat public = no create mode = 0770 directory mask = 0770 valid users= @secretariat @admins admin users = root nt acl support = yes [finances] writable = yes path = /share/finances public = no create mode = 0770 directory mask = 0770 valid users = @finances @admins admin users = root nt acl support = yes --- My groupmaps seems to be good : System Operators (S-1-5-32-549) - -1 Replicators (S-1-5-32-552) - -1 Guests (S-1-5-32-546) - -1 Domain Admins (S-1-5-21-3171617769-241562045-158900556-512) - admins Power Users (S-1-5-32-547) - -1 Domain Guests (S-1-5-21-3592376627-3846121942-908627037-514) - -1 Domain Users (S-1-5-21-3592376627-3846121942-908627037-513) - -1 Print Operators (S-1-5-32-550) - -1 Administrators (S-1-5-32-544) - admins Domain Users (S-1-5-21-3171617769-241562045-158900556-513) - ntusers Account Operators (S-1-5-32-548) - -1 Secretariat (S-1-5-21-3171617769-241562045-158900556-3003) - secretariat Technique (S-1-5-21-3171617769-241562045-158900556-3005) - technique Finances (S-1-5-21-3171617769-241562045-158900556-3007) - finances Stagiaires (S-1-5-21-3171617769-241562045-158900556-3009) - stagiaires Domain Guests (S-1-5-21-3171617769-241562045-158900556-514) - -1 Backup Operators (S-1-5-32-551) - -1 Users (S-1-5-32-545) - -1 Thx for help. Max -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba --- Stéphane PURNELLE [EMAIL PROTECTED] Service Informatique Corman S.A. Tel : 00 32 087/342467-- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + windows xp + roaming profiles
Xavier Callejas wrote: Hi, I'm having a problem with the roaming profiles and windows xp. The problem is that when a new user creates automatically a roaming profile and when he logs out the profile stay in the home dir. when he 'relogin' the 'desktop.ini' files stop working beacuse they are not 'hidden' anymore, and all the folders loss its propertis. Why is that?? what is the solution You can only store so much information in the UNIX permissions. My solution was to activate extended attribute support and disable the old style attribute mapping: ea support = yes map archived = no map hidden = no map system = no store dos attributes = yes This way the system stores the DOS attributes in the extended attributes. You need to have a filesystem that supports extended attributes (e.g. ext3 xfs) for this to work. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + windows xp + roaming profiles
nop, it din't work out. anyway thankyou very much, do you have an other idea?? :) El Mar 03 Ago 2004 13:38, Alex Grönholm escribió: Xavier Callejas wrote: Hi, I'm having a problem with the roaming profiles and windows xp. The problem is that when a new user creates automatically a roaming profile and when he logs out the profile stay in the home dir. when he 'relogin' the 'desktop.ini' files stop working beacuse they are not 'hidden' anymore, and all the folders loss its propertis. Why is that?? what is the solution You can only store so much information in the UNIX permissions. My solution was to activate extended attribute support and disable the old style attribute mapping: ea support = yes map archived = no map hidden = no map system = no store dos attributes = yes This way the system stores the DOS attributes in the extended attributes. You need to have a filesystem that supports extended attributes (e.g. ext3 xfs) for this to work. -- Xavier Callejas IT Manager (MIS) International Bonded Couriers El Salvador E-Mail: xcallejas at ibcinc.com.sv msn: xcallejas at msn.com icq: 6224 --- Open your Mind, use Open Source. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + windows xp + roaming profiles
Xavier Callejas wrote: nop, it din't work out. anyway thankyou very much, do you have an other idea?? :) El Mar 03 Ago 2004 13:38, Alex Grönholm escribió: Xavier Callejas wrote: Hi, I'm having a problem with the roaming profiles and windows xp. The problem is that when a new user creates automatically a roaming profile and when he logs out the profile stay in the home dir. when he 'relogin' the 'desktop.ini' files stop working beacuse they are not 'hidden' anymore, and all the folders loss its propertis. Why is that?? what is the solution You can only store so much information in the UNIX permissions. My solution was to activate extended attribute support and disable the old style attribute mapping: ea support = yes map archived = no map hidden = no map system = no store dos attributes = yes This way the system stores the DOS attributes in the extended attributes. You need to have a filesystem that supports extended attributes (e.g. ext3 xfs) for this to work. Depending on your distribution, you may have to recompile the kernel with extended attribute support turned on, and mount the filesystem with the extended attribute support option enabled. This is the only proper way to get this to work. It seemed to work out of the box with Fedora Core 2. Keep in mind that once the desktop.ini files have been created, any tweaking you do to samba will not give them the proper attributes. I recommend that you go to your profile dir (on Windows) and: attrib +h +s desktop.ini /s This will restore the proper attributes to desktop.ini in all subdirectories. If the desktop.ini still shows up, you may want start with a fresh profile if that is an option for you. If, despite all your efforts you cannot get it to work, you can try mapping the hidden attribute to UNIX execute permissions: map archived = no map hidden = yes map system = no Doing so will most likely cause most of your files to become invisible though :) But understand that you can only map _ONE_ attribute at a time with the old system! -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + windows xp + roaming profiles
ok, with the first option: I have fc2, stock kernel, don't you know if it support extended attribute??? or I have to recompile the kernel?? and what parameters are requieres to mount a ext3 system with extended attribute?? El Mar 03 Ago 2004 14:35, Alex Grönholm escribió: Xavier Callejas wrote: nop, it din't work out. anyway thankyou very much, do you have an other idea?? :) El Mar 03 Ago 2004 13:38, Alex Grönholm escribió: Xavier Callejas wrote: Hi, I'm having a problem with the roaming profiles and windows xp. The problem is that when a new user creates automatically a roaming profile and when he logs out the profile stay in the home dir. when he 'relogin' the 'desktop.ini' files stop working beacuse they are not 'hidden' anymore, and all the folders loss its propertis. Why is that?? what is the solution You can only store so much information in the UNIX permissions. My solution was to activate extended attribute support and disable the old style attribute mapping: ea support = yes map archived = no map hidden = no map system = no store dos attributes = yes This way the system stores the DOS attributes in the extended attributes. You need to have a filesystem that supports extended attributes (e.g. ext3 xfs) for this to work. Depending on your distribution, you may have to recompile the kernel with extended attribute support turned on, and mount the filesystem with the extended attribute support option enabled. This is the only proper way to get this to work. It seemed to work out of the box with Fedora Core 2. Keep in mind that once the desktop.ini files have been created, any tweaking you do to samba will not give them the proper attributes. I recommend that you go to your profile dir (on Windows) and: attrib +h +s desktop.ini /s This will restore the proper attributes to desktop.ini in all subdirectories. If the desktop.ini still shows up, you may want start with a fresh profile if that is an option for you. If, despite all your efforts you cannot get it to work, you can try mapping the hidden attribute to UNIX execute permissions: map archived = no map hidden = yes map system = no Doing so will most likely cause most of your files to become invisible though :) But understand that you can only map _ONE_ attribute at a time with the old system! -- Xavier Callejas IT Manager (MIS) International Bonded Couriers El Salvador E-Mail: xcallejas at ibcinc.com.sv msn: xcallejas at msn.com icq: 6224 --- Open your Mind, use Open Source. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + windows xp + roaming profiles
Xavier Callejas wrote: ok, with the first option: I have fc2, stock kernel, don't you know if it support extended attribute??? or I have to recompile the kernel?? and what parameters are requieres to mount a ext3 system with extended attribute?? El Mar 03 Ago 2004 14:35, Alex Grönholm escribió: Xavier Callejas wrote: nop, it din't work out. anyway thankyou very much, do you have an other idea?? :) El Mar 03 Ago 2004 13:38, Alex Grönholm escribió: Xavier Callejas wrote: Hi, I'm having a problem with the roaming profiles and windows xp. The problem is that when a new user creates automatically a roaming profile and when he logs out the profile stay in the home dir. when he 'relogin' the 'desktop.ini' files stop working beacuse they are not 'hidden' anymore, and all the folders loss its propertis. Why is that?? what is the solution You can only store so much information in the UNIX permissions. My solution was to activate extended attribute support and disable the old style attribute mapping: ea support = yes map archived = no map hidden = no map system = no store dos attributes = yes This way the system stores the DOS attributes in the extended attributes. You need to have a filesystem that supports extended attributes (e.g. ext3 xfs) for this to work. Depending on your distribution, you may have to recompile the kernel with extended attribute support turned on, and mount the filesystem with the extended attribute support option enabled. This is the only proper way to get this to work. It seemed to work out of the box with Fedora Core 2. Keep in mind that once the desktop.ini files have been created, any tweaking you do to samba will not give them the proper attributes. I recommend that you go to your profile dir (on Windows) and: attrib +h +s desktop.ini /s This will restore the proper attributes to desktop.ini in all subdirectories. If the desktop.ini still shows up, you may want start with a fresh profile if that is an option for you. If, despite all your efforts you cannot get it to work, you can try mapping the hidden attribute to UNIX execute permissions: map archived = no map hidden = yes map system = no Doing so will most likely cause most of your files to become invisible though :) But understand that you can only map _ONE_ attribute at a time with the old system! I have the stock kernel and I haven't modified /etc/fstab so no special mount options are used. Roaming profiles started working correctly for me after I made the aforementioned config changes so I can only assume it's working :) -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] samba 2.2.8a, XP pro workgroup question.
Chris, Thank you! The 'map to guest' worked great along with the setting to enable password encryption. I can now use my laptop from another domain on my workgroup samba share. Thanks again! ~Nate -Original Message- From: McKeever Chris [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 25, 2003 9:05 PM To: [EMAIL PROTECTED]; KD7NWG; @prupref.com Subject: Re: [Samba] samba 2.2.8a, XP pro workgroup question. On Tue, 25 Nov 2003 16:56 , KD7NWG [EMAIL PROTECTED] sent: Gang, This is my first post here so if I screw up please let me know. I run samba 2.2.8a on Solaris at home (UltraUX). I have several XP pro and win98 clients on this same network (192.168.1.x). I feel that my primary problem is when I try to access the share it is populating the username field 'Guest' and asking me for a password when I want this share to be completely open regardless of workgroup or domain name. I have had this problem a bunch of times. I _believe_ that it is caused by samba using the username/password and then failing (guest access is only when there is no usernmae/password..does that make sense?)..There is a setting which allows you to fallback to a username if the original username/password pair fails (in the docs this is said 'to cause confusion for sys-admins') I believe if you poke around with 'map to guest' and 'bad password' you should be able to come up with a solution. This may or may not be possible, but I'd sure like to know if I can make this share work, without changing my laptops workgroup/domain name. Here is my smb.conf; --- # This is /usr/local/samba/lib/smb.conf [global] netbios name = UltraUX workgroup = Galvinonline log level = 2 log file = /var/adm/log/sambalog security = share wins support = yes hosts allow = 192.168.1.0/255.255.255.0 127.0.0.1 EXCEPT 192.168.1.1 hosts deny = ALL [share] path = /share/ browseable = yes guest ok = yes public = yes read only = no I was under the impression that the settings; 'security = share', 'public = yes', and 'guest ok = yes' in my smb.conf would be all that's required for this type of access to work but if anybody has any suggestions or can provide help I'd be greatly appreciative. If you have a document containing specific information regarding this topic I'd love to read it. Thanks, ~Nate -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba --- Chris McKeever If you want to reply directly to me, please use cgmckeever--at--prupref---dot---com http://www.prupref.com Prudential Preferred Properties www.prupref.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba 2.2.8a, XP pro workgroup question.
On Tue, 25 Nov 2003 16:56 , KD7NWG [EMAIL PROTECTED] sent: Gang, This is my first post here so if I screw up please let me know. I run samba 2.2.8a on Solaris at home (UltraUX). I have several XP pro and win98 clients on this same network (192.168.1.x). I feel that my primary problem is when I try to access the share it is populating the username field 'Guest' and asking me for a password when I want this share to be completely open regardless of workgroup or domain name. I have had this problem a bunch of times. I _believe_ that it is caused by samba using the username/password and then failing (guest access is only when there is no usernmae/password..does that make sense?)..There is a setting which allows you to fallback to a username if the original username/password pair fails (in the docs this is said 'to cause confusion for sys-admins') I believe if you poke around with 'map to guest' and 'bad password' you should be able to come up with a solution. This may or may not be possible, but I'd sure like to know if I can make this share work, without changing my laptops workgroup/domain name. Here is my smb.conf; --- # This is /usr/local/samba/lib/smb.conf [global] netbios name = UltraUX workgroup = Galvinonline log level = 2 log file = /var/adm/log/sambalog security = share wins support = yes hosts allow = 192.168.1.0/255.255.255.0 127.0.0.1 EXCEPT 192.168.1.1 hosts deny = ALL [share] path = /share/ browseable = yes guest ok = yes public = yes read only = no I was under the impression that the settings; 'security = share', 'public = yes', and 'guest ok = yes' in my smb.conf would be all that's required for this type of access to work but if anybody has any suggestions or can provide help I'd be greatly appreciative. If you have a document containing specific information regarding this topic I'd love to read it. Thanks, ~Nate -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba --- Chris McKeever If you want to reply directly to me, please use cgmckeever--at--prupref---dot---com http://www.prupref.com Prudential Preferred Properties www.prupref.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba PDC + XP: still not solved?
HI, please update to version 3 and you dont need seal stuff anymore you can get via apt-get install Best Regards - Original Message - From: Robin Edgar - Tripany [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 21, 2003 6:45 PM Subject: [Samba] Samba PDC + XP: still not solved? Hi all, I've been reading and there's a lot to read but no solution! I'm using samba 2.2.3a-12.3 for Debian and I seem to have set everything I can: changed the signsecurechannel, sealsecurechannel in the registry to 0 (and back to 1), Changed the policies for autoenrollent and the password encryption (put that off in samba and in windows and then back on again) But ALWAYS do I get the following problem - when I change the settings in the computer properties samba makes the accounts fine (in passwd, shadow and smbpasswd), and I get the welcome to domain screen. When I reboot and try to log in, it can't find the PDC or it won't accept my logon. When I have a look in the logfile all it shows is: [2003/11/21 18:03:37, 2] smbd/server.c:exit_server(458) Closing connections [2003/11/21 18:03:50, 2] lib/access.c:check_access(321) Allowed connection from (192.168.0.28) [2003/11/21 18:04:01, 2] smbd/server.c:exit_server(458) Closing connections [2003/11/21 18:07:11, 1] smbd/reply.c:reply_sesssetup_and_X(1052) Username guest is invalid on this system (last message after I log into the XP machine instead of the domain). I've seen this message a few times, but nowhere is there any real solution! SOMEONE must have fixed this by now! -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba PDC + XP: still not solved?
On Fri, 21 Nov 2003 18:45 , Robin Edgar - Tripany [EMAIL PROTECTED] sent: Hi all, I've been reading and there's a lot to read but no solution! I'm using samba 2.2.3a-12.3 for Debian and I seem to have set everything I can: changed the signsecurechannel, sealsecurechannel in the registry to 0 (and back to 1), Changed the policies for autoenrollent and the password encryption (put that off in samba and in windows and then back on again) But ALWAYS do I get the following problem - when I change the settings in the computer properties samba makes the accounts fine (in passwd, shadow and smbpasswd), and I get the welcome to domain screen. When I reboot and try to log in, it can't find the PDC or it won't accept my logon. When I have a look in the logfile all it shows is: [2003/11/21 18:03:37, 2] smbd/server.c:exit_server(458) Closing connections [2003/11/21 18:03:50, 2] lib/access.c:check_access(321) Allowed connection from (192.168.0.28) [2003/11/21 18:04:01, 2] smbd/server.c:exit_server(458) Closing connections [2003/11/21 18:07:11, 1] smbd/reply.c:reply_sesssetup_and_X(1052) Username guest is invalid on this system (last message after I log into the XP machine instead of the domain). I've seen this message a few times, but nowhere is there any real solution! SOMEONE must have fixed this by now! make sure that you have run smbpasswd -w THELDAPPASSWORD and that you havent changed the machine name since. Can you send your SMB.CONF from the PDC? are you using any LDAP replication to othewr 'semi-bdc' servers? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba Prudential Preferred Properties www.prupref.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba/LDAP XP Authentication Weirdness
logs below: -- Jason Williams Wrote: Weird stuff happening eh? Just to get a few things out of the way, the user that is having problems logging on, they have an account on the PDC? --- all done through ldap, logs show authenticating user fine (below) The machine account will be there since it has already connected to the PDC. --- machine account is in the LDAP The original user works, but when you create a new user on the XP box and try and log on, you get errors right? --- I am not creating a new user, just trying to log in (as I did with the first user that works). I did however try to add that user to the list of power users and that didnt help either. Anything the logs say? --- see comments below -Original Message- From: _Chris McKeever_ [mailto:[EMAIL PROTECTED] Samba 2.2.8a, RH7.3 I have successfully connected machines running XP to the samba controlled domain. There are 3 XP machines, each with only one user designated as a power user (ie domain\username power user). Each can log into any of the three machines without a problem. Now I am trying to log a different person into any of these machines and I get the message System Could Not Log You On. I can log into any of these machines with the administrator or my account (neither of which are set up in the local users - other than computername\administrator). Any ideas of what is going on? Did I miss something? I thought that with domain logins that any user can log into the XP machine as long as they are set-up correctly via samba, which they are since they can access resources from windows 98 machines to samba shares. Thanks From the logs it seems like the user is authenticating fine against ldap/samba: problem user: [2003/07/10 12:46:59, 3] rpc_server/srv_netlog_nt.c:_net_sam_logon(605) SAM Logon (Interactive). Domain:[PRUPREF.COM]. User:[jearhart] [2003/07/10 12:46:59, 3] smbd/sec_ctx.c:push_sec_ctx(296) push_sec_ctx(99, 99) : sec_ctx_stack_ndx = 1 [2003/07/10 12:46:59, 3] smbd/uid.c:push_conn_ctx(285) push_conn_ctx(100) : conn_ctx_stack_ndx = 0 [2003/07/10 12:46:59, 3] smbd/sec_ctx.c:set_sec_ctx(328) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1 [2003/07/10 12:46:59, 5] passdb/pdb_ldap.c:ldap_open_connection(122) ldap_open_connection: starting... [2003/07/10 12:46:59, 10] passdb/pdb_ldap.c:ldap_open_connection(148) Initializing connection to winnetka.prupref.com on port 389 [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_open_connection(186) StartTLS issued: using a TLS connection [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_open_connection(217) ldap_open_connection: connection opened [2003/07/10 12:46:59, 0] passdb/pdb_ldap.c:ldap_connect_system(315) ldap_connect_system: Binding to ldap server as cn=root,dc=prupref,dc=com [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_connect_system(331) ldap_connect_system: succesful connection to the LDAP server [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_search_one_user(343) ldap_search_one_user: searching for:[((uid=jearhart)(objectclass=sambaAccount))] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [uid] = [jearhart] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:init_sam_from_ldap(576) Entry found for user: jearhart [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [pwdLastSet] = [1057792387] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [logonTime] = [0] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [logoffTime] = [2147483647] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [kickoffTime] = [2147483647] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [pwdCanChange] = [0] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [pwdMustChange] = [2147483647] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [cn] = [Jeff Earhart] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(435) get_single_attribute: [homeDrive] = [does not exist] [2003/07/10 12:47:00, 5] passdb/pdb_ldap.c:init_sam_from_ldap(626) homeDrive fell back to [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(435) get_single_attribute: [smbHome] = [does not exist] [2003/07/10 12:47:00, 4] lib/substitute.c:automount_server(183) Home server: prupref-winn [2003/07/10 12:47:00, 5] passdb/pdb_ldap.c:init_sam_from_ldap(635) smbHome fell back to \\prupref-winn\jearhart [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(435) get_single_attribute: [scriptPath] = [does not exist] [2003/07/10 12:47:00, 5] passdb/pdb_ldap.c:init_sam_from_ldap(644) scriptPath fell back to [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(435)
RE: [Samba] Samba/LDAP XP Authentication Weirdness
some more logs (sorry, these buggers are big and comparing them is making me cross-eyed) -Original Message- From: _Chris McKeever_ Sent: Thursday, July 10, 2003 1:25 PM To: _Chris McKeever_; [EMAIL PROTECTED] Subject: RE: [Samba] Samba/LDAP XP Authentication Weirdness logs below: -- Jason Williams Wrote: Weird stuff happening eh? Just to get a few things out of the way, the user that is having problems logging on, they have an account on the PDC? --- all done through ldap, logs show authenticating user fine (below) The machine account will be there since it has already connected to the PDC. --- machine account is in the LDAP The original user works, but when you create a new user on the XP box and try and log on, you get errors right? --- I am not creating a new user, just trying to log in (as I did with the first user that works). I did however try to add that user to the list of power users and that didnt help either. Anything the logs say? --- see comments below -Original Message- From: _Chris McKeever_ [mailto:[EMAIL PROTECTED] Samba 2.2.8a, RH7.3 I have successfully connected machines running XP to the samba controlled domain. There are 3 XP machines, each with only one user designated as a power user (ie domain\username power user). Each can log into any of the three machines without a problem. Now I am trying to log a different person into any of these machines and I get the message System Could Not Log You On. I can log into any of these machines with the administrator or my account (neither of which are set up in the local users - other than computername\administrator). Any ideas of what is going on? Did I miss something? I thought that with domain logins that any user can log into the XP machine as long as they are set-up correctly via samba, which they are since they can access resources from windows 98 machines to samba shares. Thanks From the logs it seems like the user is authenticating fine against ldap/samba: problem user: [2003/07/10 12:46:59, 3] rpc_server/srv_netlog_nt.c:_net_sam_logon(605) SAM Logon (Interactive). Domain:[PRUPREF.COM]. User:[jearhart] [2003/07/10 12:46:59, 3] smbd/sec_ctx.c:push_sec_ctx(296) push_sec_ctx(99, 99) : sec_ctx_stack_ndx = 1 [2003/07/10 12:46:59, 3] smbd/uid.c:push_conn_ctx(285) push_conn_ctx(100) : conn_ctx_stack_ndx = 0 [2003/07/10 12:46:59, 3] smbd/sec_ctx.c:set_sec_ctx(328) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1 [2003/07/10 12:46:59, 5] passdb/pdb_ldap.c:ldap_open_connection(122) ldap_open_connection: starting... [2003/07/10 12:46:59, 10] passdb/pdb_ldap.c:ldap_open_connection(148) Initializing connection to winnetka.prupref.com on port 389 [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_open_connection(186) StartTLS issued: using a TLS connection [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_open_connection(217) ldap_open_connection: connection opened [2003/07/10 12:46:59, 0] passdb/pdb_ldap.c:ldap_connect_system(315) ldap_connect_system: Binding to ldap server as cn=root,dc=prupref,dc=com [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_connect_system(331) ldap_connect_system: succesful connection to the LDAP server [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_search_one_user(343) ldap_search_one_user: searching for:[((uid=jearhart)(objectclass=sambaAccount))] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [uid] = [jearhart] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:init_sam_from_ldap(576) Entry found for user: jearhart [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [pwdLastSet] = [1057792387] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [logonTime] = [0] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [logoffTime] = [2147483647] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [kickoffTime] = [2147483647] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [pwdCanChange] = [0] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [pwdMustChange] = [2147483647] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [cn] = [Jeff Earhart] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(435) get_single_attribute: [homeDrive] = [does not exist] [2003/07/10 12:47:00, 5] passdb/pdb_ldap.c:init_sam_from_ldap(626) homeDrive fell back to [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(435) get_single_attribute: [smbHome] = [does not exist] [2003/07/10 12:47:00, 4] lib/substitute.c:automount_server(183) Home
RE: [Samba] Samba/LDAP XP Authentication Weirdness
update - I turned cachedlogoncount to 0 via the registry and now no one can log in... while this sounds bad, I think at least it helps me try to figure out what is going on. now, with this information, any suggestions? -Original Message- From: _Chris McKeever_ [mailto:[EMAIL PROTECTED] Sent: Thursday, July 10, 2003 2:03 PM To: '[EMAIL PROTECTED]' Subject: RE: [Samba] Samba/LDAP XP Authentication Weirdness some more logs (sorry, these buggers are big and comparing them is making me cross-eyed) -Original Message- From: _Chris McKeever_ Sent: Thursday, July 10, 2003 1:25 PM To: _Chris McKeever_; [EMAIL PROTECTED] Subject: RE: [Samba] Samba/LDAP XP Authentication Weirdness logs below: -- Jason Williams Wrote: Weird stuff happening eh? Just to get a few things out of the way, the user that is having problems logging on, they have an account on the PDC? --- all done through ldap, logs show authenticating user fine (below) The machine account will be there since it has already connected to the PDC. --- machine account is in the LDAP The original user works, but when you create a new user on the XP box and try and log on, you get errors right? --- I am not creating a new user, just trying to log in (as I did with the first user that works). I did however try to add that user to the list of power users and that didnt help either. Anything the logs say? --- see comments below -Original Message- From: _Chris McKeever_ [mailto:[EMAIL PROTECTED] Samba 2.2.8a, RH7.3 I have successfully connected machines running XP to the samba controlled domain. There are 3 XP machines, each with only one user designated as a power user (ie domain\username power user). Each can log into any of the three machines without a problem. Now I am trying to log a different person into any of these machines and I get the message System Could Not Log You On. I can log into any of these machines with the administrator or my account (neither of which are set up in the local users - other than computername\administrator). Any ideas of what is going on? Did I miss something? I thought that with domain logins that any user can log into the XP machine as long as they are set-up correctly via samba, which they are since they can access resources from windows 98 machines to samba shares. Thanks From the logs it seems like the user is authenticating fine against ldap/samba: problem user: [2003/07/10 12:46:59, 3] rpc_server/srv_netlog_nt.c:_net_sam_logon(605) SAM Logon (Interactive). Domain:[PRUPREF.COM]. User:[jearhart] [2003/07/10 12:46:59, 3] smbd/sec_ctx.c:push_sec_ctx(296) push_sec_ctx(99, 99) : sec_ctx_stack_ndx = 1 [2003/07/10 12:46:59, 3] smbd/uid.c:push_conn_ctx(285) push_conn_ctx(100) : conn_ctx_stack_ndx = 0 [2003/07/10 12:46:59, 3] smbd/sec_ctx.c:set_sec_ctx(328) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1 [2003/07/10 12:46:59, 5] passdb/pdb_ldap.c:ldap_open_connection(122) ldap_open_connection: starting... [2003/07/10 12:46:59, 10] passdb/pdb_ldap.c:ldap_open_connection(148) Initializing connection to winnetka.prupref.com on port 389 [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_open_connection(186) StartTLS issued: using a TLS connection [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_open_connection(217) ldap_open_connection: connection opened [2003/07/10 12:46:59, 0] passdb/pdb_ldap.c:ldap_connect_system(315) ldap_connect_system: Binding to ldap server as cn=root,dc=prupref,dc=com [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_connect_system(331) ldap_connect_system: succesful connection to the LDAP server [2003/07/10 12:46:59, 2] passdb/pdb_ldap.c:ldap_search_one_user(343) ldap_search_one_user: searching for:[((uid=jearhart)(objectclass=sambaAccount))] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [uid] = [jearhart] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:init_sam_from_ldap(576) Entry found for user: jearhart [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [pwdLastSet] = [1057792387] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [logonTime] = [0] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [logoffTime] = [2147483647] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [kickoffTime] = [2147483647] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute: [pwdCanChange] = [0] [2003/07/10 12:47:00, 2] passdb/pdb_ldap.c:get_single_attribute(441) get_single_attribute
Re: [Samba] Samba and XP - potential newbie questions
Thus spake Damian Gerow ([EMAIL PROTECTED]) [24/06/03 14:08]: We run Samba on our internal LAN (about 20 workstations, mostly XP), and until last night, we were using 2.2.6. I've since updated to 3.0b1, hoping to fix some *very* strange XP weirdness we're seeing. It would have been prudent of me to say that the upgrade did nothing to improve relations between the two systems. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba PDC - XP login problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 7 Feb 2003, Alecsandru CHIROSCA wrote: [2003/02/07 11:12:04, 2] rpc_parse/parse_samr.c:samr_io_userinfo_ctr(5824) samr_io_userinfo_ctr: unknown switch level 0x1a [2003/02/07 11:12:04, 0] rpc_server/srv_samr.c:api_samr_set_userinfo(672) api_samr_set_userinfo: Unable to unmarshall SAMR_Q_SET_USERINFO. [2003/02/07 11:12:04, 0] rpc_server/srv_pipe.c:api_rpcTNP(1215) api_rpcTNP: api_samr_rpc: SAMR_SET_USERINFO failed. [2003/02/07 11:12:04, 2] smbd/connection.c:utmp_yield(785) utmp_yield: lp_utmp() NULL [2003/02/07 11:12:04, 2] smbd/server.c:exit_server(440) Closing connections What is the 0x1a swich? Samba is compiled from souces and is working perfectly with Win98 clients. I can see, mount, work on the shares from any client (98 or XP) but no domain under XP. The XP client has the signorseal patch applied and the encryption options (LocalPolicy) disabled - this is what I could find on the list / howto. The 0x1a is an unknown info level. The client should back down to a lower one that we can decode. cheers, jerry -- Hewlett-Packard- http://www.hp.com SAMBA Team -- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc You can never go home again, Oatman, but I guess you can shop there. --John Cusack - Grosse Point Blank (1997) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE+S9R9IR7qMdg1EfYRAuW6AJ9j6n16WeXhabA2YTqspF/OsdxftACbBvft sJYpWVAmVGUrJNr6NpLhXsg= =qBKp -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba/Windows XP and SSH tunnelling
Do you mean to say that MS Windows (any version) supports SSL? Of course not. I'm using PuTTY as an SSH client and it works fine. I can connect to the samba server and port forward port 139 without any problems. However, I really don't think my SSH connection has anything to do with the problem I described... Thanks anyways From: John H Terpstra [EMAIL PROTECTED] To: François Mayrand [EMAIL PROTECTED] CC: [EMAIL PROTECTED] Subject: Re: [Samba] Samba/Windows XP and SSH tunnelling Date: Mon, 10 Feb 2003 08:37:01 + (GMT) On Mon, 10 Feb 2003, [iso-8859-1] François Mayrand wrote: Hi, I've been trying to get SSH tunnelling working with Samba. I'm using a Windows XP and a RedHat 8.0 box. I've closely followed the instructions from the HOWTO manual in order to set this up to no avail. Do you mean to say that MS Windows (any version) supports SSL? - John T. I think the problem comes from the fact that my lmhosts file has no effect on the NetBIOS name cache when I preload it with the command 'nbtstat -R'. I checked the cache with 'nbtstat -c'. This is what I have in my lmhosts file: 127.0.0.1 SAMBASERVER #PRE If I change the IP to something other than 127.0.0.1 then it appears in the NetBIOS cache. I get the following error message when I run the command 'net view \\sambaserver': System error 52 has occurred. You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again. Thanks for any leads Franky _ MSN Messenger : discutez en direct avec vos amis ! http://messenger.fr.msn.ca/ -- John H Terpstra Email: [EMAIL PROTECTED] _ MSN Messenger : discutez en direct avec vos amis ! http://messenger.fr.msn.ca/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba/Windows XP and SSH tunnelling
I'm using PuTTY as an SSH client and it works fine. I can connect to the samba server and port forward port 139 without any problems. Are you forwarding *just* 139? Can you provide a list of everything you're forwarding, what it's forwarding to, etc? Perhaps as a plink command line? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba/Windows XP and SSH tunnelling
Oops, dat was 'posed to go to [EMAIL PROTECTED], too (: /dev/idal --- Chris de Vidal [EMAIL PROTECTED] wrote: --- Jon Niehof [EMAIL PROTECTED] wrote: I'm using PuTTY as an SSH client and it works fine. I can connect to the samba server and port forward port 139 without any problems. Are you forwarding *just* 139? Can you provide a list of everything you're forwarding, what it's forwarding to, etc? Perhaps as a plink command line? The firewall on my workstation (inside our otherwise firewalled network) has UDP 137+8 and TCP 139 open, so you should probably forward those UDP ports, too. I don't know if PuTTY will let you forward UDP though. /dev/idal __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba/Windows XP and SSH tunnelling
You cannot forward UDP using SSH. This is why the hack to set the remote server's Netbios name to 127.0.0.1 using lmhosts is used. I tried this before and it seems that Windows 2000/XP refuse to load the loopback address as a valid netbios destination IP. Can the original poster tell me what happens when he tries to ping the remote hostname? Does he get replies from 127.0.0.1? Or does it just not resolve and using 'nbtstat -c' shows no evidence of it being loaded from the lmhosts? I suspect the latter - try changing the entry in lmhosts to something other than the loopback and then do a 'nbtstat -R' to flush the cache. An 'nbtstat -c' will then show it listed in the cache. HTH Noel The firewall on my workstation (inside our otherwise firewalled network) has UDP 137+8 and TCP 139 open, so you should probably forward those UDP ports, too. I don't know if PuTTY will let you forward UDP though. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba/Windows XP and SSH tunnelling
Hi Noel, Great! I'm glad to see you had the same problem caching the loopback on Windows XP. How did you solve this? Here is my setup info and the answers to your questions. My samba server's IP is 192.168.0.2 I have a firewall on the samba server blocking port 139. I want to block this port and force my file transfers to go through the SSH tunnel. I'm forwarding the local 139 port on the Windows box to the samba server's port 139 with PuTTY: plink 192.168.0.2 -l username -L 139:192.168.0.2:139 -v My lmhosts file contains: 127.0.0.1 SAMBASERVER #PRE I flushed the cache and preloaded it with 'nbtstat -R' I checked the cache with 'nbtstat -c' and the binding between 127.0.0.1 and SAMBASERVER doesn't appear. Can the original poster tell me what happens when he tries to ping the remote hostname? ping 192.168.0.2 -- It works Does he get replies from 127.0.0.1? net view 127.0.0.1 -- This shows my shares on my Windows XP box instead of my shares on SAMBASERVER If I change my lmhosts file to: 192.168.0.2 SAMBASERVER #PRE I can load it into the NetBIOS cache without any problems but... this doesn't solve the problem because when I run 'net view \\SAMBASERVER' I get an error 1234 (No service at port 139). This is because of my firewall on the server that blocks connections to port 139. In this configuration the Windows box is trying to connect directly to port 139 on the Samba box. That's the whole point of this exercise. I don't want to connect directly to port 139 on the server, I want it to go through the SSH tunnel. Thanks, François - Original Message - From: Noel Kelly [EMAIL PROTECTED] To: [EMAIL PROTECTED]; Jon Niehof [EMAIL PROTECTED]; 'François Mayrand' [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 10, 2003 2:24 PM Subject: RE: [Samba] Samba/Windows XP and SSH tunnelling You cannot forward UDP using SSH. This is why the hack to set the remote server's Netbios name to 127.0.0.1 using lmhosts is used. I tried this before and it seems that Windows 2000/XP refuse to load the loopback address as a valid netbios destination IP. Can the original poster tell me what happens when he tries to ping the remote hostname? Does he get replies from 127.0.0.1? Or does it just not resolve and using 'nbtstat -c' shows no evidence of it being loaded from the lmhosts? I suspect the latter - try changing the entry in lmhosts to something other than the loopback and then do a 'nbtstat -R' to flush the cache. An 'nbtstat -c' will then show it listed in the cache. HTH Noel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba/Windows XP and SSH tunnelling
François I am afraid you have reached the exact same conclusions that i did and from what i could figure there was no way it would work becasue of the refusal of 2000/XP to load the loopback from lmhosts. If you do figure it out then let me know! It would certainly be very useful but for the moment i am using Freeswan, Cheers, Noel -Original Message- From: François Mayrand [mailto:[EMAIL PROTECTED]] Sent: 10 February 2003 20:30 To: Noel Kelly Cc: [EMAIL PROTECTED] Subject: Re: [Samba] Samba/Windows XP and SSH tunnelling Hi Noel, Great! I'm glad to see you had the same problem caching the loopback on Windows XP. How did you solve this? Here is my setup info and the answers to your questions. My samba server's IP is 192.168.0.2 I have a firewall on the samba server blocking port 139. I want to block this port and force my file transfers to go through the SSH tunnel. I'm forwarding the local 139 port on the Windows box to the samba server's port 139 with PuTTY: plink 192.168.0.2 -l username -L 139:192.168.0.2:139 -v My lmhosts file contains: 127.0.0.1 SAMBASERVER #PRE I flushed the cache and preloaded it with 'nbtstat -R' I checked the cache with 'nbtstat -c' and the binding between 127.0.0.1 and SAMBASERVER doesn't appear. Can the original poster tell me what happens when he tries to ping the remote hostname? ping 192.168.0.2 -- It works Does he get replies from 127.0.0.1? net view 127.0.0.1 -- This shows my shares on my Windows XP box instead of my shares on SAMBASERVER If I change my lmhosts file to: 192.168.0.2 SAMBASERVER #PRE I can load it into the NetBIOS cache without any problems but... this doesn't solve the problem because when I run 'net view \\SAMBASERVER' I get an error 1234 (No service at port 139). This is because of my firewall on the server that blocks connections to port 139. In this configuration the Windows box is trying to connect directly to port 139 on the Samba box. That's the whole point of this exercise. I don't want to connect directly to port 139 on the server, I want it to go through the SSH tunnel. Thanks, François - Original Message - From: Noel Kelly [EMAIL PROTECTED] To: [EMAIL PROTECTED]; Jon Niehof [EMAIL PROTECTED]; 'François Mayrand' [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, February 10, 2003 2:24 PM Subject: RE: [Samba] Samba/Windows XP and SSH tunnelling You cannot forward UDP using SSH. This is why the hack to set the remote server's Netbios name to 127.0.0.1 using lmhosts is used. I tried this before and it seems that Windows 2000/XP refuse to load the loopback address as a valid netbios destination IP. Can the original poster tell me what happens when he tries to ping the remote hostname? Does he get replies from 127.0.0.1? Or does it just not resolve and using 'nbtstat -c' shows no evidence of it being loaded from the lmhosts? I suspect the latter - try changing the entry in lmhosts to something other than the loopback and then do a 'nbtstat -R' to flush the cache. An 'nbtstat -c' will then show it listed in the cache. HTH Noel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 27/01/2003 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.449 / Virus Database: 251 - Release Date: 27/01/2003 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + apache + XP ... weird
You will need to turn off the webclient under services, unless you need to access shares through http. Patrick joao marka wrote: I´m having samo strange behaviour from my XP machines. Sometimes (most always) my XP machines logged onte the sambe (as PDC on the corporate network, 40 clients +-) are serching for the samba shares into the apache server, causing some performance issues in browsing the shares, sometimes even hanging the client´s explorer. the apache log says : 10.11.16.15 - - [27/Jan/2003:06:57:45 -0200] OPTIONS / HTTP/1.1 200 - - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:06:57:46 -0200] PROPFIND /netlogon HTTP/1.1 404 280 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:06:57:51 -0200] OPTIONS / HTTP/1.1 200 - - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:06:57:51 -0200] PROPFIND /avupdate HTTP/1.1 404 280 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:06:58:43 -0200] PROPFIND /custos_geral HTTP/1.1 404 284 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:18:01 -0200] OPTIONS / HTTP/1.1 200 - - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:18:01 -0200] PROPFIND /homes HTTP/1.1 404 277 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:18:05 -0200] PROPFIND /avupdate HTTP/1.1 404 280 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:07:31:59 -0200] OPTIONS / HTTP/1.1 200 - - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:07:31:59 -0200] PROPFIND /aplic HTTP/1.1 404 277 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:34:42 -0200] OPTIONS / HTTP/1.1 200 - - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:34:42 -0200] PROPFIND /custos_geral HTTP/1.1 404 284 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:34:48 -0200] PROPFIND /homes HTTP/1.1 404 277 - Microsoft-WebDAV-MiniRedir/5.1.2600 where 10.11.16.11 / 15 are the clients IP and after PROPFIND / are the samba share´s name which the client are serarching into the apache server. the microsoft site says absolutly nothing worthy about this (or i haven´t found...) but it seems to be an office 2k issue. does anyone knows anything about this ? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba + apache + XP ... weird
thanks a lot! At 13:01 27/01/03, you wrote: You will need to turn off the webclient under services, unless you need to access shares through http. Patrick joao marka wrote: I´m having samo strange behaviour from my XP machines. Sometimes (most always) my XP machines logged onte the sambe (as PDC on the corporate network, 40 clients +-) are serching for the samba shares into the apache server, causing some performance issues in browsing the shares, sometimes even hanging the client´s explorer. the apache log says : 10.11.16.15 - - [27/Jan/2003:06:57:45 -0200] OPTIONS / HTTP/1.1 200 - - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:06:57:46 -0200] PROPFIND /netlogon HTTP/1.1 404 280 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:06:57:51 -0200] OPTIONS / HTTP/1.1 200 - - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:06:57:51 -0200] PROPFIND /avupdate HTTP/1.1 404 280 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:06:58:43 -0200] PROPFIND /custos_geral HTTP/1.1 404 284 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:18:01 -0200] OPTIONS / HTTP/1.1 200 - - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:18:01 -0200] PROPFIND /homes HTTP/1.1 404 277 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:18:05 -0200] PROPFIND /avupdate HTTP/1.1 404 280 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:07:31:59 -0200] OPTIONS / HTTP/1.1 200 - - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.15 - - [27/Jan/2003:07:31:59 -0200] PROPFIND /aplic HTTP/1.1 404 277 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:34:42 -0200] OPTIONS / HTTP/1.1 200 - - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:34:42 -0200] PROPFIND /custos_geral HTTP/1.1 404 284 - Microsoft-WebDAV-MiniRedir/5.1.2600 10.11.16.11 - - [27/Jan/2003:07:34:48 -0200] PROPFIND /homes HTTP/1.1 404 277 - Microsoft-WebDAV-MiniRedir/5.1.2600 where 10.11.16.11 / 15 are the clients IP and after PROPFIND / are the samba share´s name which the client are serarching into the apache server. the microsoft site says absolutly nothing worthy about this (or i haven´t found...) but it seems to be an office 2k issue. does anyone knows anything about this ? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and XP - Updated Registry - Still no go
I am fairly certain that, at least in its original release, XP Home couldn't join a domain. You should search the Microsoft web site to be sure, or, maybe someone who knows for sure will respond. Joel On Sun, Jan 19, 2003 at 08:03:54PM -0500, Glenn J. Rowe wrote: Is there a restriction that the Home Edition can not join a domain? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba and XP - Updated Registry - Still no go
Thats correct. A far as I am aware XP Home cannot connect to a domain. You will need XP Pro to do this. Regards Peter | -Original Message- | From: Glenn J. Rowe [mailto:[EMAIL PROTECTED]] | Sent: Monday, 20 January 2003 11:04 am | To: [EMAIL PROTECTED] | Subject: [Samba] Samba and XP - Updated Registry - Still no go | | | | One user on our church network is using XP Home Edition. I | updated the | registry as I have seen posted on various sites. | | He is still not able to connect. I have the feeling it is | because he has | joined a workgroup and not a domain. I am able to change | the workgroup | name but I can't seem to figure out how to join a domain instead. | | Is there a restriction that the Home Edition can not join a domain? | | Glenn Rowe | Volunteer | -- | To unsubscribe from this list go to the following URL and read the | instructions: http://lists.samba.org/mailman/listinfo/samba | -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and XP - Updated Registry - Still no go
Hi Glenn J. Rowe, you wrote: One user on our church network is using XP Home Edition. I updated the registry as I have seen posted on various sites. He is still not able to connect. I have the feeling it is because he has joined a workgroup and not a domain. I am able to change the workgroup name but I can't seem to figure out how to join a domain instead. Is there a restriction that the Home Edition can not join a domain? yes, that's one of the restrictions of the XP Home Edition from the money making company MS ;o) The only trick I know ist to use http://download.microsoft.com/download/whistler/Install/2/WXP/EN-US/Twe akUiPowertoySetup.exe and here you have to configure an autologon to the domain. But this is very insecure and you have to change this new for every user, which want to log on to the domain. der tom -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba and XP - Updated Registry - Still no go
Hi GUys, Just for the record: I installed a new notebook computer this weekend. It came with Windows XP Home Edition. Home Edition does NOT have any Domain security awareness. It appears to have different network drivers as well as a different NTFS file system driver. In fact, one could be forgiven (?) for thinking that Home Edition is a half-way house between Windows ME and Windows XP Professional. I bought a copy of Windows XP Professional and did an Update installation over the top of MS Windows XP Home. It took 65 minutes on a 1.8GHz P4 Mobile chipset with 512MB RAM and a fast 30GB HDD. Installation of SuSE 8,1 on it took 30 minutes by comparison! I now have all the domain stuff, and I noted that ACLs I had set on the file system were all gone! Had to redo all of this. My conclusion is that MS Windows XP Professional is a totally different game compared with MS Windows XP Home. A little deception by M$ maybe? By calling them both Windows XP aren't they kind of implying that both are the same product with just additional features in XP Pro? Oh well, another lesson in the ways of the mighty! So summarizing: 1. MS Windows XP Home can act only in what Microsoft calls Home Networking mode. This used to be called WORKGROUP networking, but there are some subtle differences in XP Home. You get to use a special system account for workgroup type behaviour. 2. I had NO difficulties connecting from Win XP Home to any Samba server. No need for the SignOrSeal disabling registry upadate. 3. MS Windows XP Home edition can not do any form of network logon, unlike MS Windows 9X/ME, which could. So in one way, it does less than the old platform it replaces! 4. Windows XP Professional has all the Domain security capability you need, as well as a lot of baggage that is likely NOT needed. 5. The cost of upgrading from Windows XP Home to Windows XP Professional is $199USD. I found out that if you order the upgrade with a new notebook it costs only $50 for the upgrade, but if you walk out of the store and then back in to buy the upgrade it costs $199USD. Nice one! Of course when I bought the notebook the salesman could not tell me what XP Home lacks that might cause me to want XP Pro. So is the upgrade worth the expense? No! But if you want Domain logon capability you have no choice. You see, if you are the dumb ass that did not know what the difference between Home and Pro is, it will cost you an extra $149USD to find out. Cheers, John T. On Mon, 20 Jan 2003, Peter Caitens wrote: Thats correct. A far as I am aware XP Home cannot connect to a domain. You will need XP Pro to do this. Regards Peter | -Original Message- | From: Glenn J. Rowe [mailto:[EMAIL PROTECTED]] | Sent: Monday, 20 January 2003 11:04 am | To: [EMAIL PROTECTED] | Subject: [Samba] Samba and XP - Updated Registry - Still no go | | | | One user on our church network is using XP Home Edition. I | updated the | registry as I have seen posted on various sites. | | He is still not able to connect. I have the feeling it is | because he has | joined a workgroup and not a domain. I am able to change | the workgroup | name but I can't seem to figure out how to join a domain instead. | | Is there a restriction that the Home Edition can not join a domain? | | Glenn Rowe | Volunteer | -- | To unsubscribe from this list go to the following URL and read the | instructions: http://lists.samba.org/mailman/listinfo/samba | -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba with XP
On Fri, 3 Jan 2003, aman raheja wrote: Is there some documentation available to configure samba with XP? That is rather a wide open question! Can you be a bit more specific please. - John T. -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA WIN XP Sp1
DON'T, I mean literally uninstall SP1 from your computer immediately. It's bugged very bad and causes many computers to crash. My XP completely crashed and couldn't EVEN BOOT. Thank god, my backups rescued me. Formatted it and reinstall everyting but SP1. MS forums going crazy, just take a look at it, you'll understand better what I mean. Serhan. -- Original Message -- From: Jörg Nissen [EMAIL PROTECTED] Date: Tue, 1 Oct 2002 10:18:48 +0200 Hello, With Win XP I can Connect to Samba. But after I had Installed Win XP SP1 I coudn´t connect to my PDC. It comes an Error Message that my Profile coudn´t load. Can anyone help me ?. Jörg Nissen -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA WIN XP Sp1
I nearly missed your message since you replied to an unrelated message... (my mail reader threads according to message id) you need to make a change on the client in the gpedit.msc program set computer configuration-administrative templates-system-user profiles- do not check for user ownership of roaming profile folders to enabled Iff your pdc and your profile server share the same SID another possibility is to modify your server's profiles share to have nt acl support = yes brad On Tue, 2002-10-01 at 04:18, Jörg Nissen wrote: Hello, With Win XP I can Connect to Samba. But after I had Installed Win XP SP1 I coudn´t connect to my PDC. It comes an Error Message that my Profile coudn´t load. Can anyone help me ?. Jörg Nissen -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA WIN XP Sp1
On Tue, 2002-10-01 at 11:09, Serhan Sevim wrote: DON'T, I mean literally uninstall SP1 from your computer immediately. It's bugged very bad and causes many computers to crash. My XP completely crashed and couldn't EVEN BOOT. Thank god, my backups rescued me. Formatted it and reinstall everyting but SP1. MS forums going crazy, just take a look at it, you'll understand better what I mean. Serhan. I've applied SP1 and, aside from the samba problem, I've not been able to detect any problems... Keep in mind that I applied SP1 to a clean system image and i distribute a sysprepped version of XPSP1+apps to the clients so it's probably not the usual case... brad -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + Windos XP/2k + Netbench Problem
This may not be a samba problem per se. I just ran a test with a single client running 8 engines. With clean directory structure - Against Win2K server - 2 engines died (1 delete, 1 move) Against NT4.0 server - 6 engines died (3 create, 3 delete) Against samba 2.2.4 on IRIX - 6 engines died (1 create, 3 delete, 2 move) With old files present - Against a Win2K server - 2 engines died (1 create, 1 delete). Against NT4.0 server - 5 engines died (5 delete) Against samba 2.2.4 on IRIX - 6 engines died (6 delete) The servers used were as follows Win2K - 1P 200 MHz PentiumPro NT4.0 - 4P 400 MHZ Xeon Samba - 4P 500Mhz MIPS R14000 Dieter Stampfer wrote: Hi all, there is a problem with the 'Default: nt smb support = yes' option in smb.conf for at least Samba 2.2.3a and 2.2.4 (on FreeBSD 4.5-STABLE) when using Netbench 7.0.2 on WXP or W2k clients. If the client is set to run 2+ Netbench engines (to simulate 2+ real clients) and 'nt smb support = yes', all but one engine fail pretty quickly, usually during a movefile oder deletefile operation (as reported by the failing engine). This does not happen with W2k or Netware 6 servers, nor does it happen with NT4 clients. Running 1 Netbench engine per client works well regardless of client OS. It seems that setting 'nt smb support = yes' is well suited for NT4 clients but not entirely perfect for XP or 2k clients. I don't know about the significance of this problem outside Netbech testing with 2+ engines per client, but with 'nt smb support = no' the problem disappears entirely. Has anyone else seen this? Maybe it doesn't show in a normal environment? If this happens to be well known could someone please point me to the relevant information (there's not much mention of Netbench anywhere in the docs I've read)? Thanks, Dieter -- email: [EMAIL PROTECTED]Vienna Dieter voice: (+43 1) 4277-14063 University Stampfer fax : (+43 1) 4277-9140 Computer snail: Universitaetsstrasse 7, A-1010 Wien Center -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba + Windos XP/2k + Netbench Problem
Herb, fist off, thanks for your reply. I was perfectly ready to attribute the problem to Netbench until I found that 'nt smb support = no' fixes it for us. We've run 6 clients with 8 engines each successfully quite often since. Clean directory structure or old files present, no more engine failures. Did you try with 'nt smb support = no' ? Not a single engine should die or there's some contributing factor we're unaware of. Unless Netbench is complete crap, I don't like the idea that more engines die with Samba than with Win2k, even in your test. We have these servers to test with: Win2K - 2P 1GHz PIII Netware 6 - 2P 800 MHz PIII NT4.0 - 1P 1,266 GHz PIII-S Samba 2.2.4 - 1P 1,266 GHz PIII-S NT4 is not an option for us but we've had similar results, i.e. all but 2 or 3 engines died. It's too early to claim that Samba beats all others but it certainly looks a lot like it. If you can get around to test with 'nt smb support = no' I'd be quite interested in what you find. I guess 'nt smb support = no' is safe in terms of keeping all other functionality the same? We'll try again with Win2k to see if we can duplicate your results there. Thanks, Dieter On Mon, 13 May 2002, Herb Lewis wrote: This may not be a samba problem per se. I just ran a test with a single client running 8 engines. With clean directory structure - Against Win2K server - 2 engines died (1 delete, 1 move) Against NT4.0 server - 6 engines died (3 create, 3 delete) Against samba 2.2.4 on IRIX - 6 engines died (1 create, 3 delete, 2 move) With old files present - Against a Win2K server - 2 engines died (1 create, 1 delete). Against NT4.0 server - 5 engines died (5 delete) Against samba 2.2.4 on IRIX - 6 engines died (6 delete) The servers used were as follows Win2K - 1P 200 MHz PentiumPro NT4.0 - 4P 400 MHZ Xeon Samba - 4P 500Mhz MIPS R14000 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
