Hello, We are using machines with Solaris and Windows XP. The XP machines are joined in a domain(windows 2003) and the Solaris machines are not joined to any domain. With Samba 2.2.8a running on Solaris 9 there are no problems to access them form Windows XP. We are authenticated by DC. On other machines we have Solaris 10 with Samba 3.0.21b and here we are NOT authenticated anymore by DC. So we have to use user authentication so every time the password is changed on XP we have to change it also on Solaris. This is done for 100 users so it is not nice... Can you, please, help me? Wy can't I have the same authentication on Samba 3.x like in Samba 2.x? Thank you very much! mirciulicai
> We are using machines with Solaris and Windows XP. The XP machines are > joined in a domain(windows 2003) and the Solaris machines are not joined to > any domain. > With Samba 2.2.8a running on Solaris 9 there are no problems to access them > form Windows XP. We are authenticated by DC. > On other machines we have Solaris 10 with Samba 3.0.21b and here we are NOT > authenticated anymore by DC. So we have to use user authentication so every > time the password is changed on XP we have to change it also on Solaris. > This is done for 100 users so it is not nice... > Can you, please, help me? Wy can't I have the same authentication on Samba > 3.x like in Samba 2.x?It is your choice to do it this way - "Solaris machines are not joined to any domain" Just join the Solaris machines to the domain. http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/
Heyho Are you using the samba binaries that came with Solaris? If so then Sun, for reasons I do not understand, have neglected to compile it with Kerberos support (at least that's the case when I looked into it with Solaris Express 6 months ago). Since AD uses Kerberos this will be a problem for you. I believe the solution is to download, compile and install the mit or heimdial kerberos libraries (they'll happily live alongside the Sun ones on a Solaris machine), and then to download and compile Samba against the aforementioned kerberos librarires. It seemed like a bit of a pain, so I never bothered to do it myself (well, I have kept putting it off ... even to this day). A google search for "samba solaris 10 kerberos" or something similar should net you some guides on what, precisely, to do. On 19/12/2006, at 1:24 AM, Mircea Ionescu wrote:> Hello, > > We are using machines with Solaris and Windows XP. The XP machines are > joined in a domain(windows 2003) and the Solaris machines are not > joined to > any domain. > > With Samba 2.2.8a running on Solaris 9 there are no problems to > access them > form Windows XP. We are authenticated by DC. > > On other machines we have Solaris 10 with Samba 3.0.21b and here we > are NOT > authenticated anymore by DC. So we have to use user authentication > so every > time the password is changed on XP we have to change it also on > Solaris. > This is done for 100 users so it is not nice... > > Can you, please, help me? Wy can't I have the same authentication > on Samba > 3.x like in Samba 2.x? > > Thank you very much! > > mirciulicai > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba-- Matt Skerritt matt.skerritt@agrav.net
Hello again, Since I had no ideea why Samba 2.2.8a is working in our environment and samba 3.0.21b not I got the ideea to compile samba 2.2.8a under Solaris 10. Make the first test(with no options) with samba-2.2.8a/source> configure samba-2.2.8a/source> make and I got the following error Compiling tdb/tdbutil.c tdb/tdbutil.c: In function `tdb_chainlock_with_timeout': tdb/tdbutil.c:46: warning: passing arg 1 of `tdb_set_lock_alarm' discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_lock_bystring': tdb/tdbutil.c:73: warning: assignment discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_unlock_bystring': tdb/tdbutil.c:87: warning: assignment discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_fetch_int32_byblob': tdb/tdbutil.c:103: warning: assignment discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_store_int32_byblob': tdb/tdbutil.c:134: warning: assignment discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_fetch_uint32_byblob': tdb/tdbutil.c:162: warning: assignment discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_store_uint32_byblob': tdb/tdbutil.c:194: warning: assignment discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_store_by_string': tdb/tdbutil.c:224: warning: assignment discards qualifiers from pointer target type tdb/tdbutil.c: In function `tdb_fetch_by_string': tdb/tdbutil.c:242: warning: assignment discards qualifiers from pointer target type Compiling printing/printing.c Compiling printing/nt_printing.c Compiling smbd/noquotas.c Compiling smbd/oplock.c Compiling smbd/oplock_irix.c Compiling smbd/oplock_linux.c Compiling smbd/notify.c Compiling smbd/notify_hash.c Compiling smbd/notify_kernel.c Linking bin/smbd Undefined first referenced symbol in file VA_COPY lib/snprintf.o ld: fatal: Symbol referencing errors. No output written to bin/smbd collect2: ld returned 1 exit status *** Error code 1 The following command caused the error: gcc -O -Iinclude -I./include -I./ubiqx -I./smbwrapper -DLOGFILEBASE=\"/usr/local/samba/var\" -DCONFIGFILE=\"/usr/local/samba/lib/smb.conf\" -DLMHOSTSFILE=\"/usr/local/samba/lib/lmhosts\" -DSWATDIR=\"/usr/local/samba/swat\" -DSBINDIR=\"/usr/local/samba/bin\" -DLOCKDIR=\"/usr/local/samba/var/locks\" -DCODEPAGEDIR=\"/usr/local/samba/lib/codepages\" -DDRIVERFILE=\"/usr/local/samba/lib/printers.def\" -DBINDIR=\"/usr/local/samba/bin\" -DPIDDIR=\"/usr/local/samba/var/locks\" -DLIBDIR=\"/usr/local/samba/lib\" -DHAVE_INCLUDES_H -DPASSWD_PROGRAM=\"/bin/passwd\" -DSMB_PASSWD_FILE=\"/usr/local/samba/private/smbpasswd\" -DTDB_PASSWD_FILE=\"/usr/local/samba/private/smbpasswd.tdb\" -o bin/smbd smbd/server.o smbd/files.o smbd/chgpasswd.o smbd/connection.o smbd/utmp.o smbd/session.o smbd/dfree.o smbd/dir.o smbd/password.o smbd/conn.o smbd/fileio.o smbd/ipc.o smbd/lanman.o smbd/mangle.o smbd/mangle_hash2.o smbd/mangle_hash.o smbd/mangle_map.o smbd/negprot.o smbd/message.o smbd/nttrans.o smbd/pipes.o smbd/reply.o smbd/trans2.o smbd/uid.o smbd/dosmode.o smbd/filename.o smbd/open.o smbd/close.o smbd/blocking.o smbd/sec_ctx.o smbd/vfs.o smbd/vfs-wrap.o smbd/statcache.o smbd/posix_acls.o lib/sysacls.o smbd/process.o smbd/service.o smbd/error.o printing/printfsp.o lib/util_seaccess.o libsmb/cli_pipe_util.o msdfs/msdfs.o param/loadparm.o param/params.o libsmb/clientgen.o libsmb/cliconnect.o libsmb/clifile.o libsmb/clirap.o libsmb/clierror.o libsmb/climessage.o libsmb/clireadwrite.o libsmb/clilist.o libsmb/cliprint.o libsmb/clitrans.o libsmb/clisecdesc.o libsmb/clidgram.o libsmb/namequery.o libsmb/nmblib.o libsmb/clistr.o libsmb/nterr.o libsmb/smbdes.o libsmb/smbencrypt.o libsmb/smberr.o libsmb/credentials.o libsmb/pwd_cache.o libsmb/clioplock.o libsmb/errormap.o libsmb/doserr.o libsmb/passchange.o libsmb/unexpected.o rpc_parse/parse_prs.o rpc_parse/parse_sec.o rpc_parse/parse_misc.o libsmb/namecache.o ubiqx/ubi_BinTree.o ubiqx/ubi_Cache.o ubiqx/ubi_SplayTree.o ubiqx/ubi_dLinkList.o ubiqx/ubi_sLinkList.o ubiqx/debugparse.o rpc_server/srv_lsa.o rpc_server/srv_lsa_nt.o rpc_server/srv_lsa_hnd.o rpc_server/srv_netlog.o rpc_server/srv_netlog_nt.o rpc_server/srv_pipe_hnd.o rpc_server/srv_reg.o rpc_server/srv_reg_nt.o rpc_server/srv_samr.o rpc_server/srv_samr_nt.o rpc_server/srv_srvsvc.o rpc_server/srv_srvsvc_nt.o rpc_server/srv_util.o rpc_server/srv_wkssvc.o rpc_server/srv_wkssvc_nt.o rpc_server/srv_pipe.o rpc_server/srv_dfs.o rpc_server/srv_dfs_nt.o rpc_server/srv_spoolss.o rpc_server/srv_spoolss_nt.o rpc_client/cli_spoolss_notify.o rpc_parse/parse_lsa.o rpc_parse/parse_net.o rpc_parse/parse_reg.o rpc_parse/parse_rpc.o rpc_parse/parse_samr.o rpc_parse/parse_srv.o rpc_parse/parse_wks.o rpc_parse/parse_spoolss.o rpc_parse/parse_dfs.o rpc_client/cli_netlogon.o rpc_client/cli_pipe.o rpc_client/cli_login.o rpc_client/cli_trust.o locking/locking.o locking/brlock.o locking/posix.o passdb/passdb.o passdb/secrets.o passdb/pass_check.o passdb/smbpassfile.o passdb/machine_sid.o passdb/pdb_smbpasswd.o passdb/pampass.o passdb/pdb_tdb.o passdb/pdb_ldap.o passdb/pdb_nisplus.o printing/pcap.o printing/print_svid.o printing/print_cups.o printing/print_generic.o printing/lpq_parse.o printing/load.o profile/profile.o lib/charcnv.o lib/charset.o lib/debug.o lib/fault.o lib/getsmbpass.o lib/interface.o lib/kanji.o lib/md4.o lib/interfaces.o lib/pidfile.o lib/replace.o lib/signal.o lib/system.o lib/sendfile.o lib/time.o lib/ufc.o lib/genrand.o lib/username.o lib/util_getent.o lib/access.o lib/smbrun.o lib/bitmap.o lib/crc32.o lib/snprintf.o lib/wins_srv.o lib/util_str.o lib/util_sid.o lib/util_unistr.o lib/util_file.o lib/util.o lib/util_sock.o lib/util_sec.o smbd/ssl.o lib/talloc.o lib/hash.o lib/substitute.o lib/fsusage.o lib/ms_fnmatch.o lib/select.o lib/error.o lib/messages.o lib/pam_errors.o nsswitch/wb_client.o nsswitch/wb_common.o tdb/tdb.o tdb/spinlock.o tdb/tdbutil.o printing/printing.o printing/nt_printing.o smbd/noquotas.o smbd/oplock.o smbd/oplock_irix.o smbd/oplock_linux.o smbd/notify.o smbd/notify_hash.o smbd/notify_kernel.o -lsec -lgen -lsocket -lnsl -lpopt make: Fatal error: Command failed for target `bin/smbd' Any ideea why and how can I fix it? Thank you very much! Best regards, Mircea On 12/18/06, Mircea Ionescu <mirciulicai@gmail.com> wrote:> > Hello, > > We are using machines with Solaris and Windows XP. The XP machines are > joined in a domain(windows 2003) and the Solaris machines are not joined to > any domain. > > With Samba 2.2.8a running on Solaris 9 there are no problems to access > them form Windows XP. We are authenticated by DC. > > On other machines we have Solaris 10 with Samba 3.0.21b and here we are > NOT authenticated anymore by DC. So we have to use user authentication so > every time the password is changed on XP we have to change it also on > Solaris. This is done for 100 users so it is not nice... > > Can you, please, help me? Wy can't I have the same authentication on Samba > 3.x like in Samba 2.x? > > Thank you very much! > > mirciulicai >
In message <7ucb3-1r0-13@gated-at.bofh.it>, "Gerald (Jerry) Carter" <jerry@samba.org> writes>Mirceac, > >> In our case the company police rules don't allow us to >> join non Windows machines to our domain. > >No offense to you personally, but that is an irresponsible >IT policy and just plan stupid. You can quote me on that one.I wouldn't call it irresponsible or stupid. If samba.org are willing to provide free on-site software support then I'm sure that the OP could persuade his employer to change the policy. If I was responsible for a company network, and didn't have any Linux support resources, I would block anyone from connecting any Linux boxes to my network whether using Samba or not. There are situations where there might be a legal requirement to do just that. Personally I'm happy to use Samba servers on my home network, happy to use them on my company networks if I can support them properly. If I only have Windows support engineers available then blocking Linux access is prudent. Things will change when any network admin can assume that his people have enough Linux experience to properly support it. We haven't got to that point yet. -- Bernard Peek bap@shrdlu.com