Displaying 20 results from an estimated 200 matches similar to: "schannel issue on samba 3.0.3"
2004 Mar 30
1
Problems with charsets and i18n
Hello list,
probably a known issue (but I haven't found a link yet):
I'm using 3.0.2a with 'unix charset = ISO8859-15' and get the following then a file with ticks is created:
- desired: "???????`'??"
- displayed: "???????`'??"
^^^
The euro sign is created correctly in a file name. The filename will be displayed in the filesystem
2005 Feb 11
2
pb with package mix
hello,
We've got a problem with the mix package in order to impute the missing data.
After importing the data, the prelim function does not work (only the stlouis
data works).
We have done :
>library(mix)
>Manq <- read.table("C:/.../file.txt")
>attach(Manq)
>save(Manq,file="C:/../R/rw2001/library/mix/data/Manq.rda")
>data(Manq)
>Manq
V1 V2 V3 V4
1
2004 Feb 18
1
Help! messed up user rights with word and samba 3.0.x
Hello everybody!
I need help with a curious problem referring to Word and Samba.
I've installed a network with a Samba 3.0.2 PDC and fileserver and about 8
Windows Clients ranging from w2k prof (members of the domain) to XP home. The
XP Home users have an account within the domain and so can "mount" the Samba
share as a local drive on their computers. All of the users are members
2004 Mar 01
5
Samba3.0.2a, MS Office (Excel), Save problem.
Hi all,
I've done a brief search of the list archieves and cannot find any
solutions to this problem, so I'll post my story and hopefuly someone will
have a better answer.
Brief Description:
This problem has now occured with a number of users, running different
versions of Office (see below).
When saving documents, Office seems to set the read-only bit. The problem
is best shown with
2005 Feb 16
1
problem with da.mix
Hello,
We use the mix package and we have a problem with the DA function. We aren't
sure, but it's maybbe a memory problem.
We have done:
> Ent<--read.table("C:/.../File.txt")
> attach(Ent)
> Ent
V1 V2 V3 V4 ... V16 V17
1 1 1 2 6 18 18
2 1 1 1 NA 14 17
3 1 1 2 1 16 14
....
199 2 1 NA 7 19 18
200
2004 Jul 28
1
failed to decode PDU - failed to do schannel processing
I am running Slackware 10
samba-3.0.5-i486-2
I get the following errors in my syslog, over and over and over...
Jul 27 17:05:51 Olympus smbd[11471]: [2004/07/27 17:05:51, 0]
rpc_server/srv_pipe.c:api_pipe_netsec_process(1397)
Jul 27 17:05:51 Olympus smbd[11471]: failed to decode PDU
Jul 27 17:05:51 Olympus smbd[11471]: [2004/07/27 17:05:51, 0]
2008 Jan 18
0
testjoin on samba pdc fails to get schannel session key
Debian 2.6.18
smb.conf:
[global]
workgroup = DOMAIN
server string = %h server
interfaces = eth0
passdb backend = tdbsam
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n
*Retype\snew\sUNIX\spassword:* %n\n *password\supdated\ssuccessfully* .
syslog = 0
log file = /var/log/samba/log.%m
max
2006 Mar 15
0
winbind and schannel errors
Hello All,
I am having two problems. I am running Samba on Solaris 10 as a member
server to a NT 4.0 domain with a PC NetLink 2.0 PDC.
The first problem: Running Samba 3.0.10 I am able to get the server to
join the domain just fine with authentication and acls working correctly
but if the shares aren't accessed for a little while winbind seems to
halt and I have to start and stop
2019 Nov 14
1
Windows server parameter equivalent to “server schannel = no”
Hi,
We have successfully upgraded from samba 4.4.3 to samba 4.9.13 as AD controller with your very helpfully advice.
When we finished the upgrade process, and with all servers fully working, including printer and shares servers, we did have to add the ?server schannel = no? parameter to smb.conf because of a EMC Unity NAS that was giving secure channel error on user validation. After that change
2010 Jan 14
1
0 length domain name & SCHANNEL can't be used to fetch trust account password?
I have a few errors I'm trying to chase down in an effort to get a
Win7 client in my domain. WinXP works -- tested unjoining and
rejoining today, and it can still join.
I have the registry adds for DNSNameResolutionRequired=0 under
LanmanServer&Client/Params (put it in both places in attempt to get
things working), as well as a DomainCompatibilityMode=1
I've tried moving to winbind
2005 Sep 10
2
"Attempt to bind using schannel without successful serverauth2" in 3.0.20 logs
Samba logs show many of these:
[2005/09/10 10:15:56, 0] rpc_server/srv_pipe.c:api_pipe_bind_req(981)
Attempt to bind using schannel without successful serverauth2
[2005/09/10 10:26:04, 0] rpc_server/srv_pipe.c:api_pipe_bind_req(981)
Attempt to bind using schannel without successful serverauth2
[2005/09/10 11:26:01, 0] rpc_server/srv_pipe.c:api_pipe_bind_req(981)
Attempt to bind using
2003 Aug 26
1
Invalid auth info 68 or level 5 on schannel only prior to
logins
Reply-To:
I've sourced the groups, but haven't had any success with solving this
problem. Here are the details:
I have a debian/testing system running samba 3.0.0beta2-1. It was
working fine with the 2.x series, until I upgraded to 3.0. The debian
server (al) is a PDC for a small NT domain (isabela) with three
workstations, all running win2k pro. All but one work fine
2006 May 19
1
Safe to ignore this message ? -Attempt to bind using schannel without successful serverauth2
OS: SLES 9
Samba Version: 3.0.20b-3.4-SUSE
Server is running in test mode, as a PDC
I find this message in my log files quite frequently, the majority coming
from one particluar machine (XP SP2):
[2006/05/19 10:35:06, 0] rpc_server/srv_pipe.c:api_pipe_bind_req(981)
Attempt to bind using schannel without successful serverauth2
[2006/05/19 10:40:16, 0]
2004 Feb 24
3
PDU & schannel errors
I extracted the following weird error from the sys-log regarding pdu and
schannel (have the same PID):
Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0, pid=31833,
effective(65534, 65533), real(65534, 0)]
rpc_server/srv_pipe.c:api_pipe_netsec_process(1371)
Feb 24 10:40:37 s-svr01 smbd[31833]: failed to decode PDU
Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0,
2004 May 17
2
RE: Bug 1315 -- wrong schannel auth len 24 -- am I having same problem on my Mac?
Can someone verify that I am having the same problem with Mac OS X
Panther (10.3.3) using Samba 3.0.2 based on my log below? I get this
trying to connect from my WinXP machine to my Mac which is configured
with ADS.
If so, can you point me to a set of instructions on upgrading from 3.0.2
to 3.0.4 with this patch?
I don't have control over the server I authenticate with...it is about
300
2010 Sep 03
2
seeking current supported crypto co-processors
Howdy,
<this messages is cross posted in freebsd-security and freebsd-net>
I'm seeking current cryptographic coprocessors supported in FreeBSD 8.x. By perusing through the crypto-dev (and subsequently referenced) man page(s) I found this list:
Hifn 7751/7951/7811/7955/7956 crypto accelerator
SafeNet 1141/1741
Bluesteel 5501/5601
Broadcom
2011 Apr 20
2
Folder Encryption and Samba
It's been passed to me from on high that one of our file servers needs
to be encrypted. I'm considering either whole-disk encryption or
folder encryption. I like the latter since, well, it's less work.
Is there any particular folder encryption systems out there that the
folks around here can recommend?
--
Aaron Clausen
mightymartianca at gmail.com
2008 Mar 28
3
IMAP security
I have port 143 open so that I can get my mail when away from home.
Occasionally, though, my router reports things like
Thu, 2008-03-27 02:00:11 - TCP Packet - Source:200.122.134.9,3821
Destination:88.97.17.41,143 - [IMAP rule match]
Thu, 2008-03-27 05:39:49 - TCP Packet - Source:140.127.181.141,3461
Destination:88.97.17.41,143 - [IMAP rule match]
Thu, 2008-03-27 16:10:03 - TCP Packet -
2003 Feb 06
1
Samba-2.2.8pre1 available on samba.org mirrors
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We've just posted a preview release of Samba 2.2.8 on samba.org.
This is a non-production release provided for testing only.
The final 2.2.8 will only include bug fixes for the 2.2.7a release.
The source code can be downloaded from :
http://download.samba.org/samba/ftp/pre/
The unpcompressed tarball and patch file have been signed
using
2005 Jul 22
1
winbind lookup errors
Hello Samba folks,
I have recently begun seeing some disturbing behavior from winbind.
Winbind will fail to look up users and groups. Examples:
The machine is configured to use winbind as a nss module.
"getent passwd <username>" will yield no results.
"wbinfo -n <username>" will yield "Could not lookup name <username>"
"wbinfo -g"