Re: [Samba] Understanding NT_STATUS_OBJECT_PATH_NOT_FOUND
Are the directories in \\dapper\dfs in fact dfs referrals? Everything under \\dapper\dfs is all part of the same shared folder, which is F:\dfs on dapper. My deep knowledge of dfs is lacking, but our dfs setup is very simple - just one share in fact (so dfs probably overkill, but the previous admin may have been thinking for growth). In fact, when I say \\dapper\dfs, I am not sure if I am accessing that via DFS or accessing the underlying shared folder itself. \\cisnet\dfs takes you to the same place, perhaps that is DFS whereas \\dapper\dfs is just a regular old shared folder? Sorry I am not more knowledgeable about this, I am researching it now. A level 10 debug log on the client or a network trace with ethereal will help here. Here is a chunk of the level 10 client debug, the part where the errors are showing up (for brevity, I did not include all 2000+ lines of output but I can if needed). I'm not so good at parsing this to tell whether or not it was a client side or server side error, perhaps you can help... smb_bcc=0 get_sequence_for_reply: found seq = 17 mid = 11 simple_packet_signature: sequence number 17 client_check_incoming_message: seq 17: got good SMB signature of [000] 90 F1 E4 8F A4 DB C9 29 ...) dos_clean_name [\home\staff\fran\2005 LRF\2004 LRF Summary FINAL.doc] NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2004 LRF Summary FINAL.doc (\home\staff\fran\2005 LRF\) simple_packet_signature: sequence number 18 client_sign_outgoing_message: sent SMB signature of [000] FA C5 84 DC 54 14 B5 77 T..w store_sequence_for_reply: stored seq = 19 mid = 12 write_socket(5,180) write_socket(5,180) wrote 180 got smb length of 35 size=35 smb_com=0x2d smb_rcls=58 smb_reh=0 smb_err=49152 smb_flg=136 smb_flg2=51205 smb_tid=16387 smb_pid=13261 smb_uid=26624 smb_mid=12 smt_wct=0 smb_bcc=0 get_sequence_for_reply: found seq = 19 mid = 12 simple_packet_signature: sequence number 19 client_check_incoming_message: seq 19: got good SMB signature of [000] E8 6F 42 C3 EB 76 D4 60 .oB..v.` dos_clean_name [\home\staff\fran\2005 LRF\2004 LRF Summary Revised.doc] NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2004 LRF Summary Revised.doc (\home\staff\fran\2005 LRF\) simple_packet_signature: sequence number 20 client_sign_outgoing_message: sent SMB signature of [000] A7 83 3F 4D 0A 8F 0C 9C ..?M store_sequence_for_reply: stored seq = 21 mid = 13 write_socket(5,160) write_socket(5,160) wrote 160 got smb length of 35 size=35 smb_com=0x2d smb_rcls=58 smb_reh=0 smb_err=49152 smb_flg=136 smb_flg2=51205 smb_tid=16387 smb_pid=13261 smb_uid=26624 smb_mid=13 smt_wct=0 smb_bcc=0 get_sequence_for_reply: found seq = 21 mid = 13 simple_packet_signature: sequence number 21 client_check_incoming_message: seq 21: got good SMB signature of [000] A2 67 C2 AA 81 A7 5B 4A .g[J dos_clean_name [\home\staff\fran\2005 LRF\2005 LRF FINAL.doc] NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2005 LRF FINAL.doc (\home\staff\fran\2005 LRF\) simple_packet_signature: sequence number 22 client_sign_outgoing_message: sent SMB signature of [000] CE F1 F1 06 C9 58 D6 1C .X.. store_sequence_for_reply: stored seq = 23 mid = 14 write_socket(5,172) write_socket(5,172) wrote 172 got smb length of 35 size=35 smb_com=0x2d smb_rcls=58 smb_reh=0 smb_err=49152 smb_flg=136 smb_flg2=51205 smb_tid=16387 smb_pid=13261 smb_uid=26624 smb_mid=14 smt_wct=0 smb_bcc=0 get_sequence_for_reply: found seq = 23 mid = 14 simple_packet_signature: sequence number 23 client_check_incoming_message: seq 23: got good SMB signature of [000] E1 3C DB 81 34 99 3F A0 ...4.?. dos_clean_name [\home\staff\fran\2005 LRF\2005 LRF First Draft.doc] NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2005 LRF First Draft.doc (\home\staff\fran\2005 LRF\) simple_packet_signature: sequence number 24 client_sign_outgoing_message: sent SMB signature of -- Fran Fabrizio Senior Systems Analyst Department of Computer and Information Sciences University of Alabama at Birmingham http://www.cis.uab.edu/ 205.934.0653 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Understanding NT_STATUS_OBJECT_PATH_NOT_FOUND
it seems to be that the path \home\staff\fran is invalid on the target server. Can you verify that the full directory path does in fact exist ? Yep, it is definitely there. I have also made a significant new discovery, the older smbclient 3.0.1 can do the operation no problem: [EMAIL PROTECTED] /]# smbclient -V Version 3.0.1 [EMAIL PROTECTED] /]# smbclient dapper\\dfs password -U Administrator -E -W CISNET -D home\\staff\\fran -d0 -Tqca /tmp/test.tar [2006/04/18 20:33:57, 0] client/clitar.c:process_tar(1433) tar: dumped 27 files and directories [2006/04/18 20:33:57, 0] client/clitar.c:process_tar(1434) Total bytes written: 6813184 [EMAIL PROTECTED] /]# [EMAIL PROTECTED] ~]# smbclient -V Version 3.0.14a-2 [EMAIL PROTECTED] ~]# smbclient dapper\\dfs password -U Administrator -E -W CISNET -D home\\staff\\fran -d0 -Tqca /tmp/test.tar Domain=[CISNET] OS=[Windows Server 2003 3790 Service Pack 1] Server=[Windows Server 2003 5.2] NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2004 LRF Summary FINAL.doc (\home\staff\fran\2005 LRF\) NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2004 LRF Summary Revised.doc (\home\staff\fran\2005 LRF\) NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2005 LRF FINAL.doc (\home\staff\fran\2005 LRF\) [snip rest of errors] And the even newer 3.0.21b-2 also fails... [EMAIL PROTECTED] ~]# smbclient -V Version 3.0.21b-2 [EMAIL PROTECTED] ~]# smbclient dapper\\dfs password -U Administrator -E -W CISNET -D home\\staff\\fran -d0 -Tqca /tmp/test.tar Domain=[CISNET] OS=[Windows Server 2003 3790 Service Pack 1] Server=[Windows Server 2003 5.2] NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2004 LRF Summary FINAL.doc (\home\staff\fran\2005 LRF\) NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2004 LRF Summary Revised.doc (\home\staff\fran\2005 LRF\) NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2005 LRF FINAL.doc (\home\staff\fran\2005 LRF\) [snip] -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Understanding NT_STATUS_OBJECT_PATH_NOT_FOUND
[For those on both this and samba-technical - sorry for the duplication. I meant to send this here, but I experienced a user error. :-) ] I'm having a problem related to the NT_STATUS_OBJECT_PATH_NOT_FOUND error and I am having a little difficulty discovering what this means. [EMAIL PROTECTED] admin]# smbclient dapper\\dfs mypassword -U Myuser -E -W CISNET -D home\\staff\\fran -d0 -Tqca /tmp/test.tar Domain=[CISNET] OS=[Windows Server 2003 3790 Service Pack 1] Server=[Windows Server 2003 5.2] NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2004 LRF Summary FINAL.doc (\home\staff\fran\2005 LRF\) NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2004 LRF Summary Revised.doc (\home\staff\fran\2005 LRF\) NT_STATUS_OBJECT_PATH_NOT_FOUND opening remote file \home\staff\fran\2005 LRF\2005 LRF FINAL.doc (\home\staff\fran\2005 LRF\) ... and so on, one for each file in my directory. Now, the files are there... [EMAIL PROTECTED] admin]# smbclient dapper\\dfs mypassword -U Myuser -W CISNET Domain=[CISNET] OS=[Windows Server 2003 3790 Service Pack 1] Server=[Windows Server 2003 5.2] smb: \ cd home\staff\fran smb: \home\staff\fran\ ls . D0 Tue Mar 21 12:01:04 2006 .. D0 Tue Mar 21 12:01:04 2006 2005 LRFD0 Wed Dec 15 13:16:46 2004 CS640 D0 Thu Dec 9 14:01:27 2004 [snip] smb: \home\staff\fran\ cd 2005 LRF smb: \home\staff\fran\2005 LRF\ ls . D0 Wed Dec 15 13:16:46 2004 .. D0 Wed Dec 15 13:16:46 2004 2004 LRF Summary FINAL.doc 232448 Wed Dec 15 13:09:35 2004 2004 LRF Summary Revised.doc227840 Fri Dec 10 12:40:39 2004 [snip] This is happening on smbclient Version 3.0.14a-2. Has anyone seen this before or know what causes this error? Thanks, Fran -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] client use spnego
In the course of debugging my still-unsolved smbclient tar starts throwing SMB signature errors after 750MB of data or so error, I came across this apparent inconsistency... From the smb.conf man page: client use spnego (G) This variable controls controls whether samba clients will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000 servers to agree upon an authentication mechanism. SPNEGO client support for SMB Signing is currently broken, so you might want to turn this option off when operating with Windows 2003 domain controllers in particular. From the Official Samba-3 HOWTO (Section 6.6.3, page 80): Windows 2003 requires SMB signing. Client-side SMB signing has been implemented in Samba 3.0. Set client use spnego = yes when communicating with a Windows 2003 server. Coincidentally, I've tried my problem with it set both ways, and it still fails. Is it thus safe to assume that the client use spnego setting has no relation to the signing that's going on in relation to the Server packet had invalid SMB signature! errors I'm getting? Thanks, Fran -- Fran Fabrizio Senior Systems Analyst Department of Computer and Information Sciences University of Alabama - Birmingham [EMAIL PROTECTED] (205) 934-0653 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SMB Signature verification failed on incoming packet
Since posting this yesterday, I've been googling a great deal and there's almost nothing out there for this particular error message. Does anyone have even a general idea of what type of error messages these are? I'm completely at a loss of what to check - I've never seen it where smbclient works until it hits a certain file (also, to update the error, it died at a different file a little further along last night). Thanks, Fran On Tue, 2004-01-13 at 17:44, Fran Fabrizio wrote: My setup is Samba/smbclient version 3.0.1 on linux RedHat 9. \\snapper\dfs is a dfs share on snapper, a Win2k3 Active Directory server. My smb.conf contains: [global] realm = ciswinnet.cis.uab.edu workgroup=CISWINNET security = ADS encrypt passwords = yes password server = snapper.cis.uab.edu client use spnego = yes I am trying to run the following command: smbclient snapper\\dfs mypassword -U Administrator -E -W CISWINNET -D home -d0 -Tqca /tmp/junk.tar This command starts tarring up the contents of \\snapper\dfs\home until a very predictable point, when it fails with the error SMB Signature verification failed on incoming packet! I start the command, and it happily runs for about 3 minutes and then... [2004/01/13 17:39:21, 0] libsmb/clientgen.c:cli_receive_smb(121) SMB Signature verification failed on incoming packet! [2004/01/13 17:39:21, 0] client/clitar.c:do_atar(698) Error reading file \home\faculty\bryant\bryantback-brblt\Images\backups\backup20011126.zip : Server packet had invalid SMB signature! [2004/01/13 17:39:21, 0] client/clitar.c:do_atar(733) Didn't get entire file. size=50316714, nread=46322640 [2004/01/13 17:39:21, 0] client/clitar.c:do_atar(654) Server packet had invalid SMB signature! opening remote file \home\faculty\bryant\bryantback-brblt\Images\backups\b (\home\faculty\bryant\bryantback-brblt\Images\backups\) [2004/01/13 17:39:21, 0] client/clitar.c:do_atar(654) Server packet had invalid SMB signature! opening remote file \home\faculty\bryant\bryantback-brblt\Images\backups\b (\home\faculty\bryant\bryantback-brblt\Images\backups\) Server packet had invalid SMB signature! listing \home\faculty\bryant\bryantback-brblt\Images\c\* Server packet had invalid SMB signature! listing \home\faculty\bryant\bryantback-brblt\Images\f\* ...and so on for the rest of the \\snapper\dfs\home directory It always happens with the file \home\faculty\bryant\bryantback-brblt\Images\backups\backup20011126.zip and then continues to fail out for the rest of the files in the directory. I'm don't think Kerberos is coming into play here since I'm providing my authentication on the command line, but that's just a guess. Any pointers as to what's going wrong here? The end goal is to backup our dfs share via the Amanda backup software, and this command that I am running is exactly the one that Amanda is trying to run, and seeing the errors that I've outlined here. Thanks, Fran -- Fran Fabrizio Senior Systems Analyst Department of Computer and Information Sciences University of Alabama - Birmingham [EMAIL PROTECTED] (205) 934-0653 -- Fran Fabrizio Senior Systems Analyst Department of Computer and Information Sciences University of Alabama - Birmingham [EMAIL PROTECTED] (205) 934-0653 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] signing failures during smbclient tar operation: SMB signature check failed
(Samba 3.0.1, RedHat 9, share is a w2k3, security = ADS) Here is a snippet of debug level 3 output of an smbclient tar operation, with error at the end. Command is: # smbclient snapper\\dfs password -U Administrator -E -W CISWINNET -D home -d3 -Tqca /tmp/test.tar [2004/01/14 15:05:10, 3] lib/util.c:dos_clean_name(549) dos_clean_name [\home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip] [2004/01/14 15:05:10, 3] client/clitar.c:do_atar(673) file \home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip attrib 0x80 [2004/01/14 15:05:10, 3] client/clitar.c:do_atar(686) getting file \home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip of size 15593375 bytes as a tar file backup20010502.zipnread=0 [2004/01/14 15:05:10, 3] client/clitar.c:do_atar(693) nread=65520 [2004/01/14 15:05:10, 3] client/clitar.c:do_atar(693) nread=131040 [2004/01/14 15:05:10, 3] client/clitar.c:do_atar(693) nread=196560 [2004/01/14 15:05:10, 3] client/clitar.c:do_atar(693) nread=262080 [snip] [2004/01/14 15:05:12, 3] client/clitar.c:do_atar(693) nread=11597040 [2004/01/14 15:05:12, 1] libsmb/smb_signing.c:signing_good(205) signing_good: SMB signature check failed on seq 7! [2004/01/14 15:05:12, 0] libsmb/clientgen.c:cli_receive_smb(121) SMB Signature verification failed on incoming packet! [2004/01/14 15:05:12, 0] client/clitar.c:do_atar(698) Error reading file \home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip : Server packet had invalid SMB signature! [2004/01/14 15:05:12, 0] client/clitar.c:do_atar(733) Didn't get entire file. size=15593375, nread=11597040 [2004/01/14 15:05:12, 3] client/clitar.c:do_atar(770) (7059.76 kb/s) (average 4832.78 kb/s) This is a 15M file, and it's failing about 11.5M into it. What -- Fran Fabrizio Senior Systems Analyst Department of Computer and Information Sciences University of Alabama - Birmingham [EMAIL PROTECTED] (205) 934-0653 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] signing failures during smbclient tar operation: SMB signature check failed
[next time I won't hit send before finishing my thought, sorry] The interesting thing is that: # smbclient snapper\\dfs password -U Administrator -E -W CISWINNET -D home -d3 -Tqca /tmp/test.tar produces \home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip of size 15593375 bytes as a tar file backup20010502.zipnread=0 [2004/01/14 15:05:10, 3] client/clitar.c:do_atar(693) nread=65520 [snip] [2004/01/14 15:05:12, 3] client/clitar.c:do_atar(693) nread=11597040 [2004/01/14 15:05:12, 1] libsmb/smb_signing.c:signing_good(205) signing_good: SMB signature check failed on seq 7! [2004/01/14 15:05:12, 0] libsmb/clientgen.c:cli_receive_smb(121) SMB Signature verification failed on incoming packet! [2004/01/14 15:05:12, 0] client/clitar.c:do_atar(698) Error reading file \home\faculty\bryant\bryantback-brblt\Images\backups\backup20010502.zip : Server packet had invalid SMB signature! whereas # smbclient snapper\\dfs password -U Administrator -E -W CISWINNET -D home\\faculty\\bryant\\bryantback-brblt\\Images\\backups -d3 -Tqca /tmp/test.tar works fine. So it's not the particular file that causes it to fail, but perhaps when it hits a certain threshold for total amount of data? Should I be taking this to one of the more technical lists? Thanks, Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] SMB Signature verification failed on incoming packet
My setup is Samba/smbclient version 3.0.1 on linux RedHat 9. \\snapper\dfs is a dfs share on snapper, a Win2k3 Active Directory server. My smb.conf contains: [global] realm = ciswinnet.cis.uab.edu workgroup=CISWINNET security = ADS encrypt passwords = yes password server = snapper.cis.uab.edu client use spnego = yes I am trying to run the following command: smbclient snapper\\dfs mypassword -U Administrator -E -W CISWINNET -D home -d0 -Tqca /tmp/junk.tar This command starts tarring up the contents of \\snapper\dfs\home until a very predictable point, when it fails with the error SMB Signature verification failed on incoming packet! I start the command, and it happily runs for about 3 minutes and then... [2004/01/13 17:39:21, 0] libsmb/clientgen.c:cli_receive_smb(121) SMB Signature verification failed on incoming packet! [2004/01/13 17:39:21, 0] client/clitar.c:do_atar(698) Error reading file \home\faculty\bryant\bryantback-brblt\Images\backups\backup20011126.zip : Server packet had invalid SMB signature! [2004/01/13 17:39:21, 0] client/clitar.c:do_atar(733) Didn't get entire file. size=50316714, nread=46322640 [2004/01/13 17:39:21, 0] client/clitar.c:do_atar(654) Server packet had invalid SMB signature! opening remote file \home\faculty\bryant\bryantback-brblt\Images\backups\b (\home\faculty\bryant\bryantback-brblt\Images\backups\) [2004/01/13 17:39:21, 0] client/clitar.c:do_atar(654) Server packet had invalid SMB signature! opening remote file \home\faculty\bryant\bryantback-brblt\Images\backups\b (\home\faculty\bryant\bryantback-brblt\Images\backups\) Server packet had invalid SMB signature! listing \home\faculty\bryant\bryantback-brblt\Images\c\* Server packet had invalid SMB signature! listing \home\faculty\bryant\bryantback-brblt\Images\f\* ...and so on for the rest of the \\snapper\dfs\home directory It always happens with the file \home\faculty\bryant\bryantback-brblt\Images\backups\backup20011126.zip and then continues to fail out for the rest of the files in the directory. I'm don't think Kerberos is coming into play here since I'm providing my authentication on the command line, but that's just a guess. Any pointers as to what's going wrong here? The end goal is to backup our dfs share via the Amanda backup software, and this command that I am running is exactly the one that Amanda is trying to run, and seeing the errors that I've outlined here. Thanks, Fran -- Fran Fabrizio Senior Systems Analyst Department of Computer and Information Sciences University of Alabama - Birmingham [EMAIL PROTECTED] (205) 934-0653 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] smbclient from linux to Win2k3 server AD share
We are trying to mount a dfs share on a Redhat 9 machine that's served from our W2K3 AD server. We've been banging our heads against this for quite a while, so I thought it time to run up the white flag and ask here. We've been trying variations of this: # mount -t smbfs -o username=OURDOMAIN\administrator,password=adminpasswd //servername/dfs /mnt/dfs and we've been getting 16162: session setup failed: ERRDOS - ERRnoaccess (Access denied.) SMB connection failed We're sure we are using the right password, and we have tried username=administrator and username=OURDOMAIN\administrator, and we know that the share name is right (can be browsed to fine from any Windows client. So it's likely that we're not sending the right stuff for authentication. We can't browse with smbclient -U administrator -L servername, we get: tree connect failed: NT_STATUS_ACCESS_DENIED This is likely something basic, but the two of us here are getting nowhere with it. Any pointers of other things I should be trying? Thanks, Fran -- Fran Fabrizio Senior Systems Analyst Department of Computer and Information Sciences University of Alabama - Birmingham [EMAIL PROTECTED] (205) 934-0653 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SOLVED Samba 3.0.0, CUPS support - Unable to open printcap file cups for read!
I'm still having print problems. I'm beginning to wonder if it's my version of CUPS rather than Samba. When I print from my Windows Samba clients, the job shows up in the /var/spool/cups directory, and CUPS web admin says the job completed, but it never prints anything. Same thing from linux samba clients works fine (i.e. if I do 'smbclient //ds119b/myprinter' and then 'print /etc/printcap', it works fine). CUPS works fine for me here. No dummy printcap needed. Something else is funny with that configuration. What version of CUPS? I have the following RPMs: cups-devel-1.1.17-13.3.0.3 cups-1.1.17-13.3.0.3 cups-libs-1.1.17-13.3.0.3 Samba 3.0.0 built from source, all standard config settings, on Redhat 9. My entire smb.conf (mostly based off of the samples in the O'Reilly book): [global] netbios name = ds119b workgroup = CISSAMBADOMAIN wins support = yes encrypt passwords = yes domain master = yes local master = yes preferred master = yes os level = 65 security = user domain logons = yes ; roaming profile support logon path = \\%L\profiles\%u\%m logon script = logon.bat logon drive = H: logon home = \\%L\%u\.win_profile\%m time server = yes ; script for adding users add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u add machine script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u # print support printing = cups printcap name = /etc/printcap load printers = yes [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writable = no printable = yes printer admin = root, @ntadmins [netlogon] path = /usr/local/samba/lib/netlogon writable = no browsable = no write list = root fran [profiles] path = /home/samba-ntprof browsable = no writable = yes create mask = 0600 directory mask = 0700 [homes] read only = no browsable = no guest ok = no map archive = yes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.0, CUPS support - Unable to open printcap file cups for read!
I've restarted the daemons many times since altering my smb.conf. My smb.conf definitely has load printers = yes (see the smb.conf excerpt I sent in my initial post for the rest of the relevant configuration entries). You mention that it complains that it can't find the share - I think it makes perfect sense that Samba complains that it doesn't know about a share called 'ps4' right after it complained that it couldn't open the CUPS configuration. :-) It stands to reason that it doesn't know it exists because it can't read the config. I'm more asking about the root problem of why it is complaining that it was Unable to open printcap file cups for read!. Thanks for the reply - it looks like I've covered all of the gotchas that you mentioned. Something else seems to be at work here... -Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.0, CUPS support - Unable to open printcap file cups for read!
Use testparm -v smb-conf-as-seen-by-samba.txt (hit ENTER twice) and then investigate smb-conf-as-seen-by-samba.txt. 'testparm -v' shows that samba is seeing (trimmed to the relevant entries): [global] load printers = yes printers = cups printcap name = cups [printers] comment = All Printers path = /var/spool/samba printer admin = root, @ntadmins guest ok = Yes printable = Yes browseable = No This means that *your* Samba tries to look for a printcap file with the *name* cups to read. Yes, I thought that was odd - but I wasn't sure if that was just samba's generic way of saying that it couldn't initialize the CUPS printers. There is no printcap file named 'cups'. As you say, it shouldn't be looking for one at all given that I've set printers = cups. I guess the most accurate description of the problem is to say samba isn't seeing printers = cups as the magic that it signifies, it just sees it as the name of a plain old printcap file. So my logic said to check that cups support was compiled in, and 'ldd /usr/local/samba/sbin/smbd' confirms that it is. That's when I decided to post - I was fresh out of ideas. :-) Maybe you are not running the smbd you think you are? Maybe you compiled yourself, and are still starting the previous smbd in a different path (not having libcups support compiled in?) I removed the RedHat samba RPMs before compiling my own version. `which smbd` doesn't find any smbd. I start it with the full path to /usr/local/samba/sbin/smbd in my init.d file for smb. I'll keep tinkering with it. -Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SOLVED Samba 3.0.0, CUPS support - Unable to open printcap file cups for read!
I have set Printcap /dev/null in cupsd.conf and re-started cupsd first then smbd. Guess what? smbclient -L localhost still lists all my printers! And I can still print from my Windows apps. (I can't print anymore from OpenOffice, since that one *does* look for a printcap) In desperation I tried printcap = /etc/printcap even though the HOWTO recommended printcap = cups and Kurt's advice above is that you could even redirect to /dev/null. Guess what, it worked. At least on my install, it seems to require that you do have a real, live printcap even for CUPS printing support. I then added another printer via the redhat printer config tool, which added it to CUPS. I restarted smb and the new printer showed up on my Windows clients. So, the residual question is why does it require a real printcap file even under CUPS support? The docs don't seem to feel that it should. Now I need to solve the You do not have sufficient access to your computer to connect to this printer problem from the Windows clients. :-) Thanks for the help, Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba 3.0.0, CUPS support - Unable to open printcap file cups for read!
Hello, I've compiled Samba 3.0.0 with CUPS support. I verified this: # ldd /usr/local/samba/sbin/smbd *snip* libcups.so.2 = /usr/lib/libcups.so.2 (0x400dc000) *snip* My smb.conf was copied from the HOWTO and the relevant sections look like: [global] *snip* # print support load printers = yes printing = cups printcap name = cups *snip* [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writable = no printable = yes printer admin = root, @ntadmins I log into the domain on an XP Pro client using the root account, and if I try to browse to the printer via My Computer -- My Network Places -- Entire Network -- MyDomain -- ds119b (this is my samba server) -- Printers and Faxes, it comes up blank. If I try to directly access the printer via \\ds119b\MyPrinterName, it gets stuck in a loop. In both cases, I am getting errors like this: Dec 9 13:38:17 ds119b smbd[21244]: [2003/12/09 13:38:17, 0] printing/pcap.c:pcap_printername_ok(282) Dec 9 13:38:17 ds119b smbd[21244]: Unable to open printcap file cups for read! Any ideas? Thanks! -Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.0, CUPS support - Unable to open printcap file cups for read!
A couple more data points: # smbclient //ds119b/ps4 Password: tree connect failed: NT_STATUS_BAD_NETWORK_NAME # The syslog shows this as a result: Dec 9 13:46:47 ds119b smbd[21284]: [2003/12/09 13:46:47, 0] printing/pcap.c:pcap_printername_ok(282) Dec 9 13:46:47 ds119b smbd[21284]: Unable to open printcap file cups for read! Dec 9 13:46:47 ds119b smbd[21284]: [2003/12/09 13:46:47, 0] smbd/service.c:make_connection(850) Dec 9 13:46:47 ds119b smbd[21284]: ds119b (192.168.2.232) couldn't find service ps4 I can successfully print to this printer from the samba linux host via the standard lpr -Pps4 approach. I checked my cupsd.conf to make sure it had a Printcap = /etc/printcap and PrintcapFormat = BSD entries and it does. The generated /etc/printcap has only one non-comment line, ps4:. -Fran On Tue, 2003-12-09 at 13:40, Fran Fabrizio wrote: Hello, I've compiled Samba 3.0.0 with CUPS support. I verified this: # ldd /usr/local/samba/sbin/smbd *snip* libcups.so.2 = /usr/lib/libcups.so.2 (0x400dc000) *snip* My smb.conf was copied from the HOWTO and the relevant sections look like: [global] *snip* # print support load printers = yes printing = cups printcap name = cups *snip* [printers] comment = All Printers path = /var/spool/samba browseable = no public = yes guest ok = yes writable = no printable = yes printer admin = root, @ntadmins I log into the domain on an XP Pro client using the root account, and if I try to browse to the printer via My Computer -- My Network Places -- Entire Network -- MyDomain -- ds119b (this is my samba server) -- Printers and Faxes, it comes up blank. If I try to directly access the printer via \\ds119b\MyPrinterName, it gets stuck in a loop. In both cases, I am getting errors like this: Dec 9 13:38:17 ds119b smbd[21244]: [2003/12/09 13:38:17, 0] printing/pcap.c:pcap_printername_ok(282) Dec 9 13:38:17 ds119b smbd[21244]: Unable to open printcap file cups for read! Any ideas? Thanks! -Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba 3.0.0, CUPS support - Unable to open printcap file cups for read!
Hopefully a dumb question... but is cups running? Also, what does an lpstat -a show? Dumb questions are usually the right kind to be asking, it's bound to be something basic that I missed. :-) However, everything looks ok: # ps -eaf | grep cupsd root 21413 1 0 14:04 ?00:00:00 cupsd # lpstat -a ps4 accepting requests since Jan 01 00:00 I do find the Jan 01 date a bit odd, but printing is functioning normally from outside of samba on this host. Thanks, Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Can't join my domain
Day 2 of my adventure into Samba. Having had such success with workgroup-based Samba, it was time to try Samba as a PDC. Unfortunately, it got cut short very quickly because I am not able to log into the domain from the XP client. I took the following steps (I'm using Samba 3.0): - modified my smb.conf as per instructions in O'Reilly Using Samba, 2nd Ed. (I think this may be part of the problem - see below) - ran 'smbpasswd -a root' giving the account a password different than the real root password - restarted the daemons - hacked my XP registry to turn off the signorseal bit - rebooted XP - logged into XP with my administrator account - control panel, system, computer name, change, enter name of my domain to join,click ok, user/pass dialog pops up - tried 'root' with the samba password i created above, not the real root password, and get the following WinXP error message dialog: The following error occurred attempting to join the domain CISSAMBA The user name could not be found checking the log files on the linux server, I see nothing unusual. I investigated and learned from testparm that Samba 3.0 no longer understands domain admin group as an smb.conf parameter (so much for Using Samba's claim that it covers Samba 2.2 and 3.0 :-( So I poked around the web and the samba site and tried the sample smb.conf from the official HOWTO, which seemed to replace the old domain admin group with a write list in the [netlogon] section. I tried write list = root in there, but it's still giving me the same error. What's the proper way to set this up on Samba 3.0? Here is my smb.conf... [global] netbios name = ds119b workgroup = cissamba wins support = yes encrypt passwords = yes domain master = yes local master = yes preferred master = yes os level = 65 security = user domain logons = yes logon path = \\%L\profiles\%u\%m logon script = logon.bat logon drive = H: logon home = \\%L\%u\.win_profile\%m time server = yes ;domain admin group = root; book says to do this but is invalid for Samba 3.0 add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u [netlogon] path = /usr/local/samba/lib/netlogon writable = no browsable = no write list = root [profiles] path=/home/samba-ntprof browsable = no writable = yes create mask = 0600 directory mask = 0700 [homes] read only = no browsable = no guest ok = no map archive = yes Any ideas? Thanks, Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: AW: [Samba] Can't join my domain
I have had the same Problem with Samba 2.2.8 but I solved it. I created an user root on my W2k Client with Administrator Privileges and the same password as on my Samba Server. In Samba 2.2.8 you only can join the Samba PDC as root. Perhaps this could also work on Samba3. Not a bad idea, but it didn't work in my case. :-( My XP box has two administrator accounts now, 'root' and 'fran'. My linux Samba server also has those two accounts, root of course, and fran as my regular user account. I've added root to smbpasswd with a password specifically for samba. I've also added fran to smbpasswd. The odd thing is that if I try to join the domain as root, I get user not found, if I try to join the domain as fran, I get Access Denied. You'd think it would be the same since they're both in smbpasswd. I was watching log.nmbd, log.smbd, and /var/log/messages while attempting to join the domain, and I see a bunch of process_logon_packet messages from the XP client's IP, but no error messages. Just some hex values like 0x12 and 0x07 associated with the process_logon messages, do they mean anything? -Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: AW: AW: [Samba] Can't join my domain
On Sun, 2003-11-23 at 11:40, Hendrik wrote: Please send your smb.conf for examine. Pretty much all the same settings as the version I posted in the original message but here it is again [global] netbios name = ds119b workgroup = CISSAMBADOMAIN wins support = yes encrypt passwords = yes domain master = yes local master = yes preferred master = ye os level = 65 security = user domain logons = yes ; roaming profile support logon path = \\%L\profiles\%u\%m logon script = logon.bat logon drive = H: logon home = \\%L\%u\.win_profile\%m time server = yes ; list of admins on the XP box? ;domain admin group = root fran ;from book but Samba3 doesn't like it ; script for adding users add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u [netlogon] path = /usr/local/samba/lib/netlogon writable = no browsable = no write list = root fran [profiles] path = /home/samba-ntprof browsable = no writable = yes create mask = 0600 directory mask = 0700 [homes] read only = no browsable = no guest ok = no map archive = yes [test] comment = For testing only, please path = /usr/local/samba/tmp read only = no guest ok = yes -Ursprngliche Nachricht- Von: Fran Fabrizio [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 23. November 2003 15:51 An: Hendrik; [EMAIL PROTECTED] Betreff: Re: AW: [Samba] Can't join my domain I have had the same Problem with Samba 2.2.8 but I solved it. I created an user root on my W2k Client with Administrator Privileges and the same password as on my Samba Server. In Samba 2.2.8 you only can join the Samba PDC as root. Perhaps this could also work on Samba3. Not a bad idea, but it didn't work in my case. :-( My XP box has two administrator accounts now, 'root' and 'fran'. My linux Samba server also has those two accounts, root of course, and fran as my regular user account. I've added root to smbpasswd with a password specifically for samba. I've also added fran to smbpasswd. The odd thing is that if I try to join the domain as root, I get user not found, if I try to join the domain as fran, I get Access Denied. You'd think it would be the same since they're both in smbpasswd. I was watching log.nmbd, log.smbd, and /var/log/messages while attempting to join the domain, and I see a bunch of process_logon_packet messages from the XP client's IP, but no error messages. Just some hex values like 0x12 and 0x07 associated with the process_logon messages, do they mean anything? -Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: AW: AW: [Samba] Can't join my domain
Thanks John that did it! I'm a little frustrated with the O'Reilly Using Samba 2nd Ed book - it advertises that it covers 3.0 but has omissions such as this. Now that I reread the book I think some of the times they refer to add user script they meant add machine script. Lucky for me this list is so helpful! :-) -Fran On Sun, 2003-11-23 at 13:40, John H Terpstra wrote: Fran, You will need an add machine script. - John T. On Sun, 23 Nov 2003, Fran Fabrizio wrote: On Sun, 2003-11-23 at 11:40, Hendrik wrote: Please send your smb.conf for examine. Pretty much all the same settings as the version I posted in the original message but here it is again [global] netbios name = ds119b workgroup = CISSAMBADOMAIN wins support = yes encrypt passwords = yes domain master = yes local master = yes preferred master = ye os level = 65 security = user domain logons = yes ; roaming profile support logon path = \\%L\profiles\%u\%m logon script = logon.bat logon drive = H: logon home = \\%L\%u\.win_profile\%m time server = yes ; list of admins on the XP box? ;domain admin group = root fran ;from book but Samba3 doesn't like it ; script for adding users add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u [netlogon] path = /usr/local/samba/lib/netlogon writable = no browsable = no write list = root fran [profiles] path = /home/samba-ntprof browsable = no writable = yes create mask = 0600 directory mask = 0700 [homes] read only = no browsable = no guest ok = no map archive = yes [test] comment = For testing only, please path = /usr/local/samba/tmp read only = no guest ok = yes -Ursprngliche Nachricht- Von: Fran Fabrizio [mailto:[EMAIL PROTECTED] Gesendet: Sonntag, 23. November 2003 15:51 An: Hendrik; [EMAIL PROTECTED] Betreff: Re: AW: [Samba] Can't join my domain I have had the same Problem with Samba 2.2.8 but I solved it. I created an user root on my W2k Client with Administrator Privileges and the same password as on my Samba Server. In Samba 2.2.8 you only can join the Samba PDC as root. Perhaps this could also work on Samba3. Not a bad idea, but it didn't work in my case. :-( My XP box has two administrator accounts now, 'root' and 'fran'. My linux Samba server also has those two accounts, root of course, and fran as my regular user account. I've added root to smbpasswd with a password specifically for samba. I've also added fran to smbpasswd. The odd thing is that if I try to join the domain as root, I get user not found, if I try to join the domain as fran, I get Access Denied. You'd think it would be the same since they're both in smbpasswd. I was watching log.nmbd, log.smbd, and /var/log/messages while attempting to join the domain, and I see a bunch of process_logon_packet messages from the XP client's IP, but no error messages. Just some hex values like 0x12 and 0x07 associated with the process_logon messages, do they mean anything? -Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Starting with Samba - first impressions
Yep, figured as much. :-) /etc/xinetd.d/swat didn't exist on my RH9 stock install, so I created it with the content recommended in the Using Samba book. The book recommended only from = localhost. Once I commented that out, it works fine. Wonder why it doesn't think I am coming from localhost? Thanks! -Fran On Fri, 2003-11-21 at 14:18, Woodward, Chris wrote: oops, I really meant, change disable = yes to no... sorry Fran, -chris -Original Message- From: Woodward, Chris [mailto:[EMAIL PROTECTED] Sent: Friday, November 21, 2003 3:02 PM To: [EMAIL PROTECTED] Subject: RE: [Samba] Starting with Samba - first impressions Did you change the /etc/xinet.d/swat file? comment out the only from line and change disable = no to yes restart xinetd -chris -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Having Samba integrate/replace existing mixed Unix/Windows network
Sorry if I came off as wanting Samba to be a clone of AD - not at all the case. :-) In fact, I speak as someone who has -never- admin'ed a Windows network, has no idea what AD is capable of, etc I've spent all of 5 minutes in front of an AD server, and that's about it. I suddenly find this network dropped in my lap and need to solve these problems quickly. My interest in minimizing the role of AD is as much about self-preservation as anything else. :-) All I'm trying to assure is that the types of things that we -do- rely on AD for right now can be sufficently replaced by some alternative functionality that Samba provides. It certainly sounds like this is the case. I just think that either the language of that excerpt was a little vague, or (more likely) it's my fault for jumping right to that section and thus not realizing that the context was XP operating natively as a member of an AD domain, and that there were other options available. I think the angle that I want to see is this - I think there are a lot of people like me who are traditionally on the Unix/Linux side of the fence, and are suddenly faced with people wanting Windows clients (or inheriting such a network). Instead of embracing that, they fear it, they wall it off, they make Windows it's own world and their network suffers for it. So the angle I want is Samba: Making Windows Play In Unix's Ballpark (as opposed to how Samba is more often billed at making Unix play more nicely on a Windows network or appear more like a Windows networkit's a blurry distinction but one which does make things less transparent for me). You'd be surprised (well maybe not -you- seeing as how you've already seen the need for more documentation on this topic) at how most literature on Samba sort of touches on these topics, but ultimately dances around them, or fails to answer them concisely all in one place. I have enough info to start playing with things - I am currently setting up a testbed consisting of a Linux laptop with a VMWare'd Windows XP on it. I will be sure to document the project and share that documentation with this list. Thanks for the kick-start and the assurance that what I will end up with will be highly functional. :-) -Fran At 07:19 AM 11/20/2003 +, you wrote: On Thu, 20 Nov 2003, Fran Fabrizio wrote: Hrmm. It seems that this (from the HOWTO) puts a MAJOR damper on things A damper is a state of mind and an attitude that is routed in what you can not do. Let's focus on what we CAN do - that's more productive. :) - Samba can act as a NT4-style DC in a Windows 2000/XP environment. However, there are certain compromises: · No machine policy files. · No Group Policy Objects. · No synchronously executed AD logon scripts. · Can't use Active Directory management tools to manage users and machines. · Registry changes tattoo the main registry, while with AD they do not leave permanent changes in effect. · Without AD you cannot perform the function of exporting specific applications to specific users or groups. -- Considering my goal #6 6. Preserve as much of the functionality that Active Directory is currently providing. This includes login scripts, roaming profiles, all the permissions management and authentication, serving a dfs, etcI understand that Samba cannot be an Active Directory server, but I also understand that it can do a lot of the same things AD does. So...no login scripts and some of these other things (policy files, temp You can have a logon script. You can use NTConfig.POL files. When we figure out how to implement Group Policy Objects, we will document how to do that. Right now you can have Group settings in NTConfig.POL, and then apply that Policy File to a group. changes to the registry that get wiped at logout, etc...) are common on our network. Almost all of our Windows clients are XP. Do you truly lose the What I have described as being possible works perfectly with Windows XP Professional clients. ability to do all of those things, or can you do older, NT-style versions of some of them by having the XP clients fallback into NT domain compatibility? You can do with Samba-3 most of what you can do with Windows NT4. There are still millions of networks that have only Windows NT4 servers that are running fine with Windows XP Professional clients. Samba-3 is perfect alternative, which when fully deployed significantly reduces the need for Active Directory. You can get a highly scalable Samba-3 based network (using an LDAP backend). You can store UNIX POSIX account information in LDAP. You can get a very functional Windows network with Samba-3. Samba-3 is not a cake that has no icing on it. The issue is that Samba-3 gives you most of what Windows NT4 Server gives you. Samba-3 offers a more scalable solution that NT4 (through use of LDAP). Samba-3
[Samba] Having Samba integrate/replace existing mixed Unix/Windows network
I've recently inherited a two-headed monster of a network and would like to see what Samba can do for me to help clean up the situation. Due to bias/preference of the past administrator, who favored Unix, when it came time to introduce Windows machines to our department, he basically built a parallel network (physically and logically), and let a graduate student manage the Windows network. As a result, we now have a network consisting of two subnets, Windows and Unix. Each subnet provides it's own file server, print server, DNS, DHCP, directory (NIS vs. Active Directory) and user accounts. Unfortunately for us, this is a rather arbitrary division, as we often have users that dual-boot between the two sides and students that need to do work on both and I would prefer that the two networks be more integrated. I will be redesigning this network (both physically and logically) and I believe Samba can help me. Some of the ways are clear, whereas some are much less clear. Let me start with my design goals... 1. Repartition the network based on functional needs, not OS choice. Our context is a department at a university. Instead of a Unix subnet and a Windows subnet, I would like a subnet for the undergraduate open labs, a subnet for research groups, a subnet for faculty workstations, etcwhatever services I provide need to play well in this multi-subnet environment. 2. Consolidate file serving duties. I would like for a user to see the same home directory whether booting into Linux, Solaris or Windows. This will reduce the number of instances of users needing to move files between the two systems, as well as provide a single point as a target for backups. 3. Consolidate user accounts. I want one account for each user, period. If I absolutely can't have this, I want to synchronize between the two so that it appears as one. We eventually going to try to authenticate against the campus-wide LDAP service, and the fewer points of authentication I have within my department, the easier that will be. 4. Consolidate DNS and DHCP. Because we have two DHCPs, and because our firewall is set to pass all traffic between the two subnets, I actually have two network cables running to my laptop - I have to switch them when I switch OSes! I am not 100% sure of the reason, the past admin simply said that's how it is, but I believe it's so I hit the right DHCP server first. Obviously, that needs to go away. Same with DNS - right now, adding a host means adding it to Active Directory, adding it to NIS, and adding it to 3 /etc/hosts files. This needs to be much cleaner. 5. Consolidate print servers. 6. Preserve as much of the functionality that Active Directory is currently providing. This includes login scripts, roaming profiles, all the permissions management and authentication, serving a dfs, etcI understand that Samba cannot be an Active Directory server, but I also understand that it can do a lot of the same things AD does. So, those are the highlights of my goals. I see that it's very straightforward for Samba to do the file and print serving, but is this rock solid? This will be the sole source of home dirs, I don't want the Windows clients flaking out on me. I'm less sure about the authentication. Right now, we use Active Directory on the Win side and NIS on the Unix side. I believe one option is to keep the Active Directory for linux clients, and to use winbind to authenticate against that. However, I would like to get rid of AD altogether if possible. Is there a better model? On the Unix side, NIS has to go. Something like Kerberos or LDAP would be better but I want to make a choice that plays well with Samba and with the Windows clients as well. I know that Kerberos is a good option for cross-platform single-point-of-authentication. Perhaps LDAP. Perhaps they work together? What's the model I'm after and how does Samba fit in? I'm not sure if Samba can help with the current DNS/DHCP woes or if that's simply a matter of setting up one on Linux and pointing everyone at it (not sure how good it is to have DHCP serving multiple subnets like I want, though...) Thoughts? For the big picture is it possible for me to get rid of Active Directory for this network I have of Sun, Linux, NT, 2000, and XP machines and still have hopes of a reliable network? If I need to keep an AD around for one of more of these services, how best to set it up to play with Samba? Those are the kinds of questions I'm after. I have read through the beginning of the O'Reilly Samba book and it appears that Samba is definitely the right track, but I'm hoping for a bit more of the specifics of the model I'm seeking. Thanks for your time and thoughts, Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Having Samba integrate/replace existing mixed Unix/Windows network
Hrmm. It seems that this (from the HOWTO) puts a MAJOR damper on things - Samba can act as a NT4-style DC in a Windows 2000/XP environment. However, there are certain compromises: · No machine policy files. · No Group Policy Objects. · No synchronously executed AD logon scripts. · Can't use Active Directory management tools to manage users and machines. · Registry changes tattoo the main registry, while with AD they do not leave permanent changes in effect. · Without AD you cannot perform the function of exporting specific applications to specific users or groups. -- Considering my goal #6 6. Preserve as much of the functionality that Active Directory is currently providing. This includes login scripts, roaming profiles, all the permissions management and authentication, serving a dfs, etcI understand that Samba cannot be an Active Directory server, but I also understand that it can do a lot of the same things AD does. So...no login scripts and some of these other things (policy files, temp changes to the registry that get wiped at logout, etc...) are common on our network. Almost all of our Windows clients are XP. Do you truly lose the ability to do all of those things, or can you do older, NT-style versions of some of them by having the XP clients fallback into NT domain compatibility? -Fran -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
