Displaying 6 results from an estimated 6 matches for "idzerda".
1997 Oct 23
1
NT domain logon questions
Hi. Myself and a anti-Micro$oft companion tried to get
NT domain logons working yesterday and seem pretty close, but
not quite.
Samba is 1.9.18alpha3, server is an Ultra-2 running SunOS 5.5.1.
Encrypted passwords seem to be working, a la smbclient and mostly
from NT, "mostly" because it *seemed* to be working but we did
have some problems with home directories in smbpasswd changing
1997 Dec 20
1
Intermittent logon failures
Samba 1.9.17p2 running on SPARC 4 Solaris 2.5.
Windows 95 clients.
For some time now I have been hearing reports of users not
being able to logon to the domain--but I've never seen it
happen myself, and I never do anything to fix it. It's
just this annoying problem that doesn't happen often enough
for me to ever see or track down.
Today, FINALLY, I tried logging into a machine and
1999 Jan 20
2
Multiple servers from single /usr/local
Dear Samba Users,
In the past, with Samba 1.9.18p10, I have handled running several Sun
SPARC/Solaris server boxes that share the same /usr/local/samba filesystem.
I did this by putting different configuration files in /usr/local/samba/lib.
For example: smb.conf.host1, smb.conf.host2, etc.
But, now with Samba-2.0.0, it didn't seem to work. My initial questions are:
1) There are now files
1998 May 11
1
(wtmp) Suggestion to samba
Joao Carlos Mendes Luis <jonny@coe.ufrj.br> wrote:
> I think it would be useful if samba had a utmp log interface.
> I know that it's possible to see who is logged with smbstatus, but
> sometimes a simple who(1) or w(1) is more efficient and ubiquitous.
If you were to search for 'wtmp' in the 1997 archives
(via the Samba web pages), you would find one interesting
1997 Oct 20
1
Disappearing clients in WINS list
On Mon, 20 Oct 1997, Dieter Rothacker wrote:
> Luke Kenneth Casson Leighton wrote:
>
> > > Here is the smb.conf of the disappeared samba box:
>
> ^^^^^^^^^^^
> I do not think THIS computer should become local master !?
> (see below)
>
> > > wins support = no
> > > workgroup = WORKGROUP
> > >
1998 Jan 30
0
find_response_record/find_subnet_for_nmb_packet
I'm getting a *lot* of error messages like this, enough that I'm tempted
to remove syslog support because I catch syslogd using small but
measurable percentages of CPU time:
find_response_record: response packet id 27930 received with no matching record.
find_subnet_for_nmb_packet: response record not found for response id 27930
find_response_record: response packet id 35 received with no