similar to: join domain problem with Samba 3.0 alpha18

Hi, We are migrating from Unix Server to Linux, so the ASU (Advanced Server for Unix) will be replaced by Samba. The pwdump for Nt is pretty for Windows NT, but I don't know if there is an Unix dump tool to transfer the ASU SAM database to the Samba's smbpasswd file. Any help is welcomed! Thanks in advance, Jianliang Lu Tiesse S.P.A. Via Jervis, 60 10015 Ivrea (TO) Italy Email:

Hi all, I repost the message about the signatur because I've not had any response. This time I hopefuly to get some ideas. When we put the parameter "server signing = auto or Yes" in smb.conf, the Windows XP clients can no longer connect to the samba (3.0.2), the "net use \\server\ipc$ /u:user password" return error 64. If I disabled the "server signing" the

There is OBVIOUSLY something wrong somewhere. EITHER a WHOLE bunch of us are stupider than we thought, the documentation left off a step, or there is something SO blatently obvious that we are ALL staring it in the face and missing it inches in front of our faces. This is exactly what I've had, (BUT I *D*I*D* have it running ok ...) and I STILL havent figured it out yet,... Subject:

On Tue Feb 17 11:14:15 GMT 2004, Andrew Bartlett wrote: >> Any suggestions for things to try (or even a guaranteed solution ;-) ) would >> be very much appreciated. >> server signing = no >Try this as yes. How did you get it work? I've tried the "server signing = yes or auto", but it didn't work. Could you kindly tell us how to set the XP to get it

Kristyan (and all) I just searched the samba website, and I couldnt find any reference to spnego except for a slide show (samba-lwny.ag ) that I can't open. ANYWAY. since I can't find any reference to the spnego parameter, could someone explain what it is, what it does, and HOW it can help us "stupid" people? It doesnt seem to be a parameter I've come across before..

I''m beginning to believe that the use of the last column in the rules file to designate redirection/forwarding is too subtle for many users. For 1.3, I think I''ll do something like the following: Current rule: ACCEPT net loc:192.168.1.3 tcp 80 - all New rule: FORWARD net loc:192.168.1.3 tcp 80 Current rule: ACCEPT net fw::3128 tcp 80 - all New rule: REDIRECT net

The rule: ACCEPT loc $FW::3128 tcp www doesn''t work propertly, the http access does not redirect to squid but directly exit. what''s wrong? Thanks ------- Dario Lesca (d.lesca@ivrea.osra.it) -------------------------------------- @@@@@@@ this is my shorewall-1.2.13 config: #[/etc/shorewall/common.def]-----------------------------------------------

Hi, on a system RedHat 8.0, only on this, not on other various RedHat8.0, I have see the follow strange error in /var/log/{messages,boot.log} ..... After the boot all it seems to work, the modules is loads.... I have already tried to install other versions of kernel but the problem is always the same one :-(( Someone has some idea of what is happening? Thanks... Dario Lesca

Hi, I tried to upgrade samba on a Linux from 2.2.8a to 3.0.0, and after the upgrade the printer sharing fails. I would like to participate in the search for the bug (if it is a bug), but I don't know how to start. If this is not a bug I would like to know why not, and how to work around, that the printer does not work with the attached smb.conf, while it works with samba version 2.2.8a

Warning .... The two interface samples contain samples of the three interface... [root@multilinux temp]# tar xvfz samples-1.4.4/two-interfaces.tgz three-interfaces/ three-interfaces/interfaces three-interfaces/routestopped three-interfaces/masq three-interfaces/policy three-interfaces/rules three-interfaces/zones ------- Dario Lesca (d.lesca@ivrea.osra.it)

Hello, I installed samba4 alpha18 and I added a new share named ?test? in smb.conf. When I try to go to my server from Windows 7 client, I can see netlogon, sysvol and test. When I try to access to test, I have an error message : element not found. I can access netlogon and sysvol fine but the other shares I cannot access. I tried this : http://www.spinics.net/lists/samba/msg101309.html but I

Hello list, Iam using Samba4 alpha18 with Debian Squeeze. Mi primary domain have Windows Server 2003 and my Secundary Domain have Samba4. When i create a user in active directory user and computer in Windows Server, i can see the user in active directory user and computer in samba4, and when i create a user in samba4 i can see this user en active directory windows server. the principal problem is

Ok, while I'm usually more comfortable installing an RPM or DEB package and having the package maintainer handle all the details for me - I don't get a choice here. The latest Ubuntu 12.04 package is the Alpha18 release. So, I've compiled my own copy of Samba4.01 - and surprise, surprise, it went well. So the crux of the question is: Where should I install it to. [What directory.]

Has anyone added windows 2000 computers to Samba3.0a20 PDC, I have been trying to do that and I always get "Incorrect Parameter" message on windows 2000 client, the same problem occured with alpha19, but joining alpha18 PDC used to work fine with me. Any suggestions? My smb.conf file [global] workgroup = ZSQUID netbios name = hsalin server string = Samba

xiphmont@xiph.org (Monty) writes: > Really, folks, several of you are debating the most fundamental of signal > processing concepts. Go get an undergraduate level book on signal > processing (eg, _Understanding Signal Processing_ or _Signals and Systems_) > and read it. This is all covered first month. On this subject, could you (all) recommend some good vorbis-relevant dsp and

We are proud to a announce another alpha release of Samba 4.0, alpha 18 What's new in Samba 4.0 alpha18 =============================== Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4 alpha series and the stable 3.x series. The primary additional features over Samba 3.6 are support for the Active Directory logon protocols

Hi, I'm using SAMBA 3.0 alpha19 to try the trust relationship between an NT 4.0 domain and the samba domain. The command I used was "net rpc trusdom", but it did'nt work, also the other "net" commands worked bad ( Segmentation Fault or return -1 ecc.). Could you kindly to tell me how to do to set the trust relationship with the SAMBA 3.0, or if there is any docs for

I use the above kernel, can i get a ext3 patch for this kernel,Or will ext3 work with this kernel. Cheers redhead

The configuration files has settings that seem to address the issues of using indexes on NFS (i.e. locking and mmap fixes), but we are using Dovecot on NFS, and when the load gets high we start to see a lot of NFS stale file handle errors, particularly with MS clients like Outlook. I see the discussion about these errors from last year. Any updates on the state of the code? Should we be using

Environment: Dovecot 1.0beta8 Host: 64 bit Red Hat AS4 Linux (2.6.9-34.0.1) Disks: NFS netapp In the case below, the two connections were going through two separate servers sharing disks via an NFS NetApp. Here is the sequence of operations: 1. Open a connection to a folder (say mail/Trash) 2. Open a connection to another folder (say Inbox) 3. Move messages from Inbox to Trash using this