Displaying 20 results from an estimated 100 matches similar to: "authentication problems samba -> PDC"
1999 Jul 02
2
problems with connecting to a share
Hi,
I've the following problem.
samba 2.0.3 runs on a sun.
The security is server. The PDC is a NT-machine.
Sometimes when users try to connect to a share they get
the answer the password is incorrect. After a restart of
smbd all works fine.
Has anybody an idea????
regards
Eckhard
---------------------------------------------
Fraunhofer Institute
Factory Operation and Automation (IFF)
2009 Dec 17
1
Opening "Printers and Faxes" crashes explorer.exe on Vista x64
Hello everyone,
First time on this list, because I can't seem to find anything about my
problem. I hope someone here will be able to help me.
I have a file and print server running an old Ubuntu 7.04 x86 and Samba
3.0.2.4 that came with it. (I tried upgrading samba once, but it kept
crashing, so I went back to this default version, because it works very
well.)
The problem is, as the title
2002 Nov 15
3
Problem with print$
Ok...I'm stuck.
Environment:
Suse 8.0, with Samba 2.2.3a, no domain controller (workgroup only).
Client machine is NT4 Workstation, SP5.
Access to disk shares is fine, no problems, using encrypted PWs.
I'm trying to set up a [print$] share, as described in chapter 6 of the
Samba-HOWTO-Collection.
The symptom that I get is that when I attempt to load the driver to the
print$ share, I
1997 Oct 15
8
OPLOCKS
Robert Dal Santo wrote:
> Is there any work underway to get Samba to support OPLOCKS? I know
> they are difficult to implement but I'm faced with a decisions now to buy an
> NT box (Ugh!) or do a lot of messing around to get this application
> to perform decently. The application in questions takes around 5
> hours to do a taks without OPLOCKS and around an hour to do the
2005 Jun 06
0
NTLMSSP(NTLMv2) problems after PDC reboot
Hi all,
In my win2k ADS server(mixed mode), I have set the LAN Manager
authentication level to Send NTLMv2 response only\refuse LM & NTLM. In
the registry, i also set
HKLM\System\CurrentControlSet\Control\Lsa|lmcompatibilitylevel -->
level 5 (accepts only NTLMv2). Similarly, i also set
HKLM\System\CurrentControlSet\Control\Lsa\MSV1_0\NtlmMinClientSec -->
0x00080000(NTLMv2 Session
2007 Sep 25
2
Stumbling blocks moving to NTLMv2
Hi folks,
I have been asked to force NTLMv2 logins to avoid use of LM hashes.
To meet the requirement I added some lines to the smb.conf in [Global] (we
only have that section anyway - this is purely for domain authentication
with an ldap backend):
client lanman auth = no
client NTLMv2 auth = yes
lanman auth = no
min protocol = LANMAN2
ntlm auth = no
This seemed to work - users
2003 Nov 25
1
NTLMv2 and Win95 clients
Hello.
I've just compiled Samba-3.0.0 on Tru-64 5.1b (AKA Digital Unix, AKA
OSF) with base security (no shadow passwords) using the native compiler
and GNU make. In smb.conf I'm forcing NTLMv2 only:
security = user
encrypt passwords = yes
lanman auth = No
ntlm auth = No
client NTLMv2 auth = Yes
client lanman auth = No
2011 Sep 15
1
Samba/LDAP/Win7 Domain Admins could not log in
Hi,
I'm running Samba 3.5.6 with OpenLDAP 2.4.23 (from Debian Squeeze) as
PDC. Everything is working fine (Joining Domains, Log on Users) but I'm
not able to Log in as Domain Admin. If I try to, the message "Unable to
log on ?The User Profile Service service failed the logon. User profile
cannot be loaded." (in german: "Fehler bei der Anmeldung mit dem
2002 Jun 07
2
Mappoing from Samba client to \\server\share\dir ?
Hi!
How do I create a mountpoint with smbmount, that attaches to
\\server\share\dir (on a Windows 2000 server) ?? If I mount to
\\server\share I'm not able to see anything - but the mapping to the same
server (from a Win2000 client) is okay, and I can see the contents of the
directory... Trying to map to //server/share/dir gives me an error:
24402: tree connect failed: ERRDOS -
2003 Feb 17
1
Testparm Solaris 8
Apologies if this has been covered already, I can't find any helpful hints
after 2 hours searching....
Testparm refuses to work on my e250 box - says it can't find the file?
Any pointers to useful docs will be greatly appreciated (other than SAMS
books and O'Rielly - been there, done that!), especially any relating to
Solaris 8 and SAMBA!
TIA
Jo
2002 Feb 12
0
password server authentication
I have installed Samba 2.2.3a on a Solaris 2.6 box,
and it has been configured with a small smb.conf that
sets security = domain, workgroup = GFMNET, password server = GFMNET01,
I have succesfully joined domain GFMNET (controlled by
GFMNET01).
I can attach to resources anywhere in the domain from
this new box(E250), but any attempt to connect to its
resources results in failed authentication.
I
2019 Apr 18
0
Announce: OpenSSH 8.0 released
OpenSSH 8.0 has just been released. It will be available from the
mirrors listed at http://www.openssh.com/ shortly.
OpenSSH is a 100% complete SSH protocol 2.0 implementation and
includes sftp client and server support.
Once again, we would like to thank the OpenSSH community for their
continued support of the project, especially those who contributed
code or patches, reported bugs, tested
1998 Jul 30
0
If WAN is broken I have a problem with local connect
We have two subnets with two samba servers (div0 - 150.10.10.1 and div8 - 150.18.18.1 ).
If I break the connection between subnets, clients belong to div8 cannot connect locally.
All clients have set up wins server to 150.10.10.1 ( div0 ) .
If subnets are connect, all is ok ( connecting, browsing).
We are using samba 1.9.18p7.
smb.conf in div0 is
[global]
workgroup = LANGROUP
domain logons =
2000 Jul 20
10
SUNWski
Has anyone had success with getting /dev/random to work
after installing SUNWski? After I install the pkg and start /etc/
init.d/cryptorand, the /dev/random file remains 0 bytes.
I am running Solaris 2.8
- David
2002 Feb 25
2
(no subject)
did U use :
smbpasswd -a user
th passwd must be the same
rick.
>From: "Gary Ferrer" <gary@ferrer.yi.org>
>To: "Samba-users" <samba@lists.samba.org>
>Subject: [Samba] (no subject)
>Date: Fri, 22 Feb 2002 00:07:04 -0800
>
>Hi people, sorry for the previous HTML stuff, I hope this time it's plain
>text. Here's my problem:
2002 Feb 14
4
Authentication problems Still
Hi All,
I've tried everything I can think of, and spent many many
hours trying to get this Sun Solaris 8 machine to authenticate
with a Linux 7.1 machine acting as the PDC.
In summary:
Both machines are running 2.2.3a compiled from source
without additional arguments (just ran configure on each platform)
No problems with Win95, Win98, WinNT authenticating with the Linux
PDC.
The Sun machine
1997 Sep 29
1
UMASK Problems
I have quite a problem with the new SAMBA version(s) ( both 1.9.17
and 1.9.17 p2).
When creating a directory in a samba-mounted
unix file system the create mask entry will be ignored. I tried
a lot (changing umasks on the unix boxes (SunOS/Solaris), changing
the create mask entry to a many different values) but nothing
happens at all. Every directory will be created with the permissions
of 755.
2011 Apr 12
0
samba active directory question
We are migrating to 2008 Active Directory and in making changed to
smb.conf and krb5.conf and restarting smb services I get below error in
the winbindd.log:
Winbind won't start
[2011/04/07 15:03:09, 1] nsswitch/winbindd.c:main(979)
winbindd version 3.0.22-13.16-SUSE-SLES10 started.
Copyright The Samba Team 2000-2004
[2011/04/07 15:03:09, 0]
1999 May 13
0
copy problem in samba 2.02
Dear Gurus,
I'm playing with samba 2.02 in my FreeBSD 3.1-stable box. I can browze
the the server and its shares from my PC. The problem is when I tried to
copy files from my PC to the samba shares, I got the following errors
from my PC:
"Can't create or replace filename: the specified network response or
device is no longer available."
I got this prompt almost everytime I
2001 Jan 23
0
Authentication Problem on Sun Solaris 8 and SSHd2
I am running SSH on a number of servers but none use SSH for anything
but admin login. I am thinking of switching all users to it (for obvious
security reasons) but I have had a rash of problems lately. The first
was the 'Bad Packet' error which no one seems to care about or know the
answer to why it suddenly appears on 2 servers while other servers
running the same OS and SSH version