similar to: help in server signing

Hello, I am trying to connect a 2nd Linux machine to my Samba PDC using smbmount. Both machines run Samba 3.0.14a. However, when trying to mount using machine2# /usr/local/samba/bin/smbmount //pdc/wpkg /raid/samba/mount -o username=abc,password=123 it takes some seconds and then only brings up an I/O error. The log on the primary machine brings up [2005/07/19 10:28:36, 1, effective(1008,

Greetings, I've set up a Samba 3.0.23a PDC on Fedora Core 5 and joined a couple XP clients to the domain successfully. However, when I start using the Samba PDC's "homes" share from the XP client, I eventually get errors such as the following: [2006/08/05 03:28:07, 0] libsmb/smb_signing.c:srv_check_incoming_message(657) srv_check_incoming_message: BAD SIG: seq 798 wanted

LAN - mixed architecture - 2 x win98, 1 x winME, 1 x win2k, 3 x Mandrake Linux 10.0. Most samba activity is between the Mdk boxes, file-moving, etc. Versions - Mandrake 10.0, with all updates applied, Samba 3.0.6-4.1 I had a properly working lan, with occasional problems between box1 and box2 (Mdk boxes). Now I have no connection between them, for file-sharing purposes, at all. Box3,

Hello I seem to be having signing problems with 3.2.0 I have 2 PDCs on 2 different sites (say A and B) both running 3.2.0, with the line server signing = auto in smb.conf. There is a one way trust (B trusting A) setup. While everything works correctly on both sites for local machines access to local shares (a site A user logged on a site A machine can perfectly access shares of site A PDC). The

Hello, after an update from Samba 2.2.12 to 3.0.22 and running the daemons 2-3 days my Samba Server freeze the whole Server. First the clients get connection problems, timing out to access the shares and then some minutes later the whole Server freeze, i can't even logon on the console. Only a cold reset is possible. I convert all files from latin-1 to a UTF-8 and then from UTF-8 to ISO-8859-1

I am running Samba 3.0.9/KRB5 1.4 on Centos 3.4 on x86 with security = ADS in a Win2k3 domain. I have successfully used kinit to authenticate, joined the domain, and wbinfo -g/-u/-t return the expected results. However, when I try and access the samba shares from a Win2k3 box, it fails telling me I don't have permissions to access the share. Needless to say I am thoroughly perplexed. I have

Since upgrading to Samba 3.0.23a, mounting a Samba share using mount.cifs generates the following errors in the Samba server's logs: Aug 7 17:45:08 pccentos4 smbd[5345]: [2006/08/07 17:45:08, 0] libsmb/smb_signing.c:srv_check_incoming_message(720) Aug 7 17:45:08 pccentos4 smbd[5345]: srv_check_incoming_message: BAD SIG: seq 2 wanted SMB signature of Aug 7 17:45:08 pccentos4 smbd[5345]:

I'm having problems connecting from my laptop, and the logs show lib/util_sock.c:send_smb(769) Error writing 116 bytes to client. -1. (Broken pipe) : 1 Time(s) lib/util_sock.c:write_data(562) write_data: write failure in writing to client 192.168.0.91. Error Broken pipe : 1 Time(s) libsmb/smb_signing.c:srv_check_incoming_message(737) srv_check_incoming_message: BAD SIG: seq 2 wanted

Hello all, I have 3 Linux boxes all authenticating against 2 Windows 2003 domain controllers. Each Linux box is running a different Linux and samba version: Box1: CentOS 3.4 3.0.25-7 Box2: CentOS 4.4 3.0.10-1 Box3: CentOS 5 3.0.23c-2 Their smb.conf and krb5.conf files are all identical (below). A few days ago authentication stopped working and my /var/log/messages fills up with

Hi there I'm having trouble getting winbindd working properly (I think). My understanding is that winbindd uses a kerberos 5 session (with 2003 server) to authenticate the machine to ADS, before any users have logged in. Then it uses that session ticket to authenticate all users of the smb server. Is that correct ? I can run kinit ok, and klist shows me a krb5 ticket (using a Domain

I've been checking the authentication with "wbinfo -a <username>%<password>", which is failing with the following error: plaintext password authentication failed error code was NT_STATUS_NO_SUCH_USER (0xc0000064) error messsage was: No such user Could not authenticate user <username>%<password> with plaintext password challenge/response password

Hi I'm trying to get my samba file server to authenticate against my windows 2008 active directory server , so that there is a unified log in and if anyone logs onto the box the they are authenticated against the a server and there account is created. I'm battling to get my samba server server to join the domain .. I can get any further than this [root@technical-vmlab ~]# kinit

(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

Hi all hope you can help, I have a mixed XP / 2K client deployment, and the samba server is running as a PDC. On most machines I have no problems, but on 2 2K machines and 1 XP machine I'm getting the same behaviour every time I either try to write the file or execute a file, no matter whether I log on to the domain or which userid I log on as. I'm also running debian woody 2.4.19, and

As promised, I'm posting the smb.conf files for the two servers in question. One minor correction I should offer is that the new SAMBA server will be version 4.1, not 4.0. Following is SMB.CONF for the current PDC, which is Samba 3.3.4 on Slackware 13. I've omitted all share definitions to allow focus more on the configuration side. Actual server/domain names have been omitted.

I have a samba PDC (using samba 3.0.24). When I try to establish trust with a win2003 domain, I got signing error, see the log below. Trust with NT domain and win2000 domain works. Any help are appreciated. Thanks, Lin [2007/04/04 17:00:13, 5] lib/debug.c:debug_dump_status(391) INFO: Current debug levels: all: True/10 tdb: False/0 printdrivers: False/0 lanman: False/0 smb: False/0

On 12/02/15 02:43, soonerdave wrote: > As promised, I'm posting the smb.conf files for the two servers in question. > > One minor correction I should offer is that the new SAMBA server will be > version 4.1, not 4.0. > > Following is SMB.CONF for the current PDC, which is Samba 3.3.4 on Slackware > 13. > I've omitted all share definitions to allow focus more on the

Help, wbinfo -t fails with the error in subject, and getting sids of groups that aren't BUILTIN fail. Everything else seems to work. Note: I am not converting my kerberos tickets to krb4, is this necessary? (It used to work without it..but now it seems not to work.) I get no errors from kinit. all other wbinfo requests succeed with the exception of looking up the SIDS of groups that

Hi, I've a problem with "logon script" parameter: client doesn't run this script and i've no error in samba logs. I'm using samba 3.0.24 (etch) with windows XP SP2 client side. workstation was joined in domain and user login (using roaming profiles) is executed without errors. I used unix2dos tool to transform the script in dos way and if I run the script in widows with

Hi! I''m studying load balancing and fault tolerance using multiple WAN interfaces. I follow the howto in http://www.ssi.bg/~ja/nano.txt but the problem is that faults detected are limited only in link between lan gateway and modem/router adsl, and none about adsl signal. Someone can tell me another howto about fault tolerance using a different method? (that solve my problem) I know