Displaying 20 results from an estimated 300 matches similar to: "help for samba and ldap"
2011 Nov 30
1
Wine 1.3.28 Office2003 setup error on Kubuntu 10.04 !
I'm not able to setup office 2003 with wine on my Kubuntu 10.04. Look at this:
ottavio at nc6320:/media/dati/Dati_ext4/home/ottavio/DaMasterizzare/Programmi$ sudo mount "Office 2003.iso" /media/isomnt -t iso9660 -o unhide
[sudo] password for ottavio:
mount: warning: /media/isomnt seems to be mounted read-only.
ottavio at
2000 Mar 13
2
Win2k Domain logons
Hi everyone. I just got a copy of Win2k in and have been messing with it.
Have a question, and have searched the archives for the answer, but didn't
find it. Can Win2k domain logon to a pre-3.0.0 samba server? Or di I
need to get TNG running? I can get NT4.0 boxes to authenticate and login
fine (Samba pre-3.0.0), but Win2k keeps complaining:
"The following error occurred validating
2004 Oct 05
2
Can join domain; can't logon
I had a problem similar to my current one a week or so ago, and I was
encouraged to upgrade from Samba 2.2.9 to 3.0.7, which I did. Now
that I've completed that nightmare, the problem I initially set out to
fix is still there, just different. Namely:
I am trying to set up Samba 3.0.7 on a SuSE 9.1 box as an LDAP PDC
whose only job will be authentication. Our LDAP server is on a
separate
2003 Feb 16
2
Access Denied when trying to login to samba PDC
While trying to set up samba as a PDC, I followed O'Reillys Using Samba. This resulted in the
following smb.conf:
[global]
workgroup = GRAHAM
encrypt passwords = true
log level = 1
max log size = 1000
hosts allow = 192.168.0/24 192.168.1/24
hosts deny = 1.1.1.1/0.0.0.0
domain logons = yes
security = user
os level = 34
local master = yes
preferred master = yes
domain master = yes
[temp]
2004 Jan 12
1
Another problem with Win2k logins...
Hi all,
After recovering the former SID that I hadn't had in mind while changing the Linux distro (thanks to Thomas for his help), now I still have some problems. I can't still get any user to login but the ones that must be in cache in the clients (thanks again Thomas).
So, I'll give you the logs to see if anybody detects something strange...
The users can perform a 'smbclient -L
2004 Jan 28
1
XP logins
Hi all,
today happened very strange thing to me. I'm running Samba 3.0.1 on Debian.
Today users called me that machines with XP has problems to work on the
network. I haven't changed configuration for 1 month...
Users on XPs can logon into domain, but when they try, after logon, to open
ANY share on Samba server, it locks up (explorer has no response] for about
5
minutes and after that
2002 Oct 28
1
intermitent domain logon failures
I have an issue where at odd times, maybe after 3 days, maybe after a
week, people suddenly cant do domain logons. Unfortunately the machine
is 50km away so i'm sure theres more details I can glean once I can
interogate the users a bit more.
Things I have noticed:
Anyone currently logged in can still work fine.
A restart of samba fixes the issue (till it hapens next).
ps ax shows smbd and
2001 Apr 17
4
Samba 2.2.0 - glossy press release :-).
In the interests of full disclosure, here's the glossy press
release (with html as well ! :-).
Jeremy.
---------------------------------------------------------------------
Samba 2.2.0 - Powering the next generation of Network Attached
--------------------------------------------------------------
Storage.
--------
17
2003 Feb 04
1
spurious domian login problems
We have a few win9x workstations, that have spurious login
problems. They get the message:
No domain server was available to validate your password you
may not be able to gain access to some network resources.
The passwords are definetly correct and the problem will
sometimes disappear after 5 - 10 retries, but almost always after
a full restart of the win9x PC, very occasionally it takes as
2003 May 13
3
PDC problem
Hello all,
I'm running slackware linux 8.0 and tries to configure samba 2.2.8a
as PDC. I succeded configuring network shares i.e. netlogon,
profiles, etc. Everything is OK, but when i tries to make a domain
logon using windows 98 apears an error "Wrong parameter". When i
tries to join my samba domain under Windows 2000 it says "domain does
not exists ....". what am i
2000 Mar 18
3
Samba 2.0.7pre2 snapshot released.
Hi all,
I just released Samba 2.0.7pre2, available from :
ftp://samba.org/pub/samba/alpha/samba-2.0.7pre2.tar.gz
This is the second snapshot of the code that should become
the official Samba 2.0.7 and is feature complete (ie. I'm
only going to accept bug fixes, not more features).
This is *not* production code, but should work well as a
file and print server, and contains fixes for all
2003 May 22
1
Continued: Join domain OK, but domain not found after reboot
Hi, all:
To recap:
I can successfully get my WinXP box to join the domain (WHITEROCK), but
after rebooting, when I try to log on:
"The system cannot log you on now because the domain WHITEROCK is not
available."
I get this even when using the user 'root' - and this user was the one
to successfully join the domain WHITEROCK!!
To rule out any stale junk, my WinXP is a
2003 Jul 15
2
Windows 98 logon server problem
Hi,
I have Samba version 2.2.7 up and running as a PDC for several
Windows 2000/XP clients, as well as file sharing working. However, when
I try to use it as a Win9X logon server, I can not seem to make it work.
Whenever I try to logon from the Win98 computer, I get the error
message "Incorrect Parameter" (in windows) and get the following message
in the nmbd.log file:
=-=-=
2004 Sep 21
2
login from XP
Hello,
I'm having a problem logging in to the Samba domain from an XP machine. The machine is added to the domain but after reboot I can't login. I've done the signorseal registry hack but I'm still not able to login. The error I get when logging in is this:
"Windows cannot connect to the domain, either because the domain controller is down or otherwise unavailable, or
2004 Jan 12
3
Win XP Pro / Linux PDC
Hi all,
I'm trying to configure Samba as a PDC. I'm running Debian Woody, hence
Samba version 3.0.0final-1. We have no Windows servers anywhere on the
network (yay!).
I have done an smbpasswd for root, and add machine script is setup (see
attached smb.conf). From the XP Pro workstation, when I fill in the domain
name, log in as root, and click ok, I eventually get: "The following
1999 Oct 28
1
Win 95 login fails
Hi !
I've set up a samba server (2.0.3-8) on a machine running RH 6.1.
Everything works fine.
Printing, smbclient and so on..
But when i try to login from a win95 client, it says "there's no domain server
to confirm the password"..
And when i look in the logs. ( .log ), it says:
[1999/10/28 10:00:59, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69)
process_login_packet:
2002 Feb 25
1
Solution: Samba-2.2.3a and Win95?
Hi out there,
i got a very good hint to the solution
of the problem with the error-message:
2002/02/25 15:38:52, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69)
process_logon_packet: Logon from 10.170.20.8: code = 0x0
The hint was from Demerson Zounar:
> I faced this problem some time ago, and the solution was an absence of the
> parameter netbios name in smb.conf.
1998 Dec 31
2
NT Logon Authentication
I'm trying to set up SAMBA to handle NT logons, and have it to the
point where my Sun sees the logon request come in, and I get the
following in the log file:
process_logon_packet: Logon from : code = 7
Does anyone know either what this code (and others) relates to, or
where to find the code meanings?
Anyone else gotten this to work and have some tips/tricks/gotchas?
I'm trying to
2002 Feb 25
1
Samba-2.2.3a and Win95?
Hi out there again,
i just installed Samba-2.2.3a as a PDC
on a Solaris-Box (2.6) and encounter Problems with Windows95
Logons. log.nmbd says:
[2002/02/25 15:38:52, 1] nmbd/nmbd_processlogon.c:process_logon_packet(69)
process_logon_packet: Logon from 10.170.20.8: code = 0x0
And Windows95b states:
Invalid parameter.
The mklogon-Script get's not invoked for
2007 Jan 30
4
Domain logons and client IP broadcasts
Ok, I'm stumped.
Last week domain logons worked.
Now when I try to logon, I get a message, "You could not logon
because the SJSA domain is not available.
I've had this happen before when the trust account between the
client and server was out of sync (restored a disk image that had
a different trust account password)
To fix this, it has been sufficient to quit the domain, reset