Re: [Samba] XP/W2K on Samba 3
Greetings! So Bernd, previously I wanted do the same, but I didn´t get success because the profiles from Windows 2000 and Windows XP are differents (when a user logs in on a Windows 2000 and after that he tries to log in on a Windows XP, it returns some errors)... But, if you want, you can look for the profiles section that will avoid you do that. When you configure it with this option, the Windows client will use remote profiles automagically! : ) [ ]´s On 10/3/06, Bernd Kloss [EMAIL PROTECTED] wrote: Hello, maybe it is not the right place to ask Windows-related questions, but i'll give it a try. I am running a Debian-Etch-Server with Samba 3 and Windows2000 and XP-clients. Everything is working fine except: For every user logging in from a Win-client, the client generates a local user-profile and local user-directories. What has to be done within Samba and what has to be done on the clients to avoid that and get all userdata stored in the user's share. Thank you! ___ Viren-Scan für Ihren PC! Jetzt für jeden. Sofort, online und kostenlos. Gleich testen! http://www.pc-sicherheit.web.de/freescan/?mc=02 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba -- Bruno Rodrigues Neves [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] Dissapearing printer drivers with 3.0.23c
Hi Bostjan, How often does this problem occur? o/ -- Bruno Rodrigues Neves [EMAIL PROTECTED] On 9/23/06, Bostjan Müller [EMAIL PROTECTED] wrote: Hi, we have been using Samba as PDC, netlogon and printing server for some time now, but after upgrading to Samba version 3.0.23c the printer drivers seem to dissapear. It has happened multiple times now, and I have set up a script to be run every five minutes and check the diff between all the printer drivers. Tonight at 00:35 AM _ALL_ the printer drivers have dissapeared - yes each and every one of them was gone. There is no error in the logs at that time (at least nothing I could find), but we only have logging level of 0 set, because otherwise we have too much logs at the same time. Can anyone recomend a procedure, how am I at least to debug this sort of problem, what can I check, to try to get to the bottom of this, and not have drivers dissapear any more. Regards, Bostjan -- buhdej evridej -- 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 printer share
Hi, And if you add something like that into the smb.conf: [global] disable spoolss = yes [print$] comment = Printer Drivers path = /var/lib/samba/printers [hp2300] path = /tmp writeable = yes browseable = yes printable = yes guest ok = yes what happens? -- Bruno On 9/21/06, Kostya Berger [EMAIL PROTECTED] wrote: Hello, dear colleagues using SAMBA. Who could possibly tell me what I am missing in order to make my SAMBA printer share visible on the windows network( i.e., accessing it from a MS Windows machine's explorer, for example )? It is SAMBA 3.0.23 on Linux 2.4.33 machine(originally RedHat 7.3. based, but so much upgraded, even to GLIBC-2.3.6). here are the linked libraries: = #ldd /usr/local/samba/sbin/smbd libcups.so.2 = /usr/lib/libcups.so.2 (0x40023000) libpthread.so.0 = /lib/libpthread.so.0 (0x40056000) libm.so.6 = /lib/libm.so.6 (0x400a8000) libcrypt.so.1 = /lib/libcrypt.so.1 (0x400cb000) libresolv.so.2 = /lib/libresolv.so.2 (0x400f8000) libnsl.so.1 = /lib/libnsl.so.1 (0x40109000) libdl.so.2 = /lib/libdl.so.2 (0x4011d000) libpopt.so.0 = /usr/lib/libpopt.so.0 (0x40121000) libc.so.6 = /lib/libc.so.6 (0x40128000) libpthread.so.20 = /usr/lib/libpthre And here, at last, my smb.conf: [global] log file = /usr/local/samba/var/log.%m load printers = yes socket options = TCP_NODELAY username map = /etc/samba/user.map interfaces = 192.168.0.1/27 domain master = yes null passwords = yes public = yes wins support = true guest account = nobody dns proxy = no netbios name = Samba netbios aliases = Samba printing = cups server string = Samba default = global local master = yes workgroup = QUBICA os level = 65 printcap name = cups security = share max log size = 50 [Server_files] map archive = no writeable = yes path = /mnt/nfs hide dot files = no public = yes case sensitive = yes [printers] postscript = yes printer = hp_LaserJet_3015 lpq command = lpstat -o %p browseable = yes printable = yes print command = lpr -P %p -o raw %s -r comment = All Printers lprm command = cancel %p-%j printer admin = root === My printer here is installed via HPLIP, CUPS is running OK, everything's OK, except that I can't see the printer through windows network browsing, neither from linux, nor from windows machines. Of course, I did the RTFM search and corrected everything accordingly, but still. The [Server_files] share IS visible, the [printers] is NOT. ANY IDEAS? THANKS IN ADVANCE FOR YOUR KIND SUPPORT AND YOUR PRECIOUS TIME! Kostya -- 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] can't access Samba share when clocks skew is too great
Hi Leonid, I don´t know the cause of this problem, but if you try add into your netlogon script a line such as a set time in order to set the clock to the same from the server? Regards! -- Bruno On 9/22/06, Leonid Zeitlin [EMAIL PROTECTED] wrote: Hi all, I have a Samba 3.0.23c server joined to an Windows 2003 AD domain. Users access it from Windows workstations (XP, 2000). The problem is that if a workstation has its time off by more than 5 minutes, Samba server cannot be accessed. I understand that Kerberos cannot authenticate the clients due to clock skew; however, I thought that in such case Samba could falls back to NTLM auth. At least, the workstations with the wrong clock can access Windows file servers, but not Samba. Is Samba's behavior in this case intentional? Is this supposed to work? How can I help or debug this situation? Any help is appreciated. Thanks, Leonid -- 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
