Displaying 20 results from an estimated 60000 matches similar to: "No subject"
2003 Dec 01
0
No subject
and that access to the client should be denied.
> James
>
> ----- Original Message -----
> From: "Alexander Lobodzinski" <lobo@mental.com>
> To: <samba@lists.samba.org>
> Sent: Monday, August 20, 2001 10:17 AM
> Subject: Can I have only certain users log in to a Samba DC client?
>
>
> > A machine should be member of a domain controlled by
2003 Dec 01
0
No subject
have a hosts allow or hosts deny line in your smb.conf. If you don't
want samba to do reverse lookups, then comment out any allow/deny hosts
lines in your smb.conf file.
Don
-----Original Message-----
From: future@yxtc.edu.cn [mailto:future@yxtc.edu.cn]
Sent: Sunday, August 05, 2001 3:00 AM
To: samba@lists.samba.org
Subject: dns and samba
Hi,
I find that my samba server always does
2003 Dec 01
0
No subject
are being offered by the server. You can check also what shares are being
offered by the windows boxes the same way.
I wonder why the other windows machines are not showing up in network
neighborhood? Try sharing some things between windows machines. Maybe you
have something misconfigured on the windows side.
There is a script, findsmb, which comes with samba. First turn off nmbd
(killall nmbd) ,
2003 Dec 01
0
No subject
Are you using wins?
Try lmhosts for the start?
Are all machines on the same subnet?
Just a few hints to start with ...
Christian
>
>
> I have absolutely no clue what I could do to fix it. The only solution I
> can think of, is to downgrade to redhat 6.2.
>
> Your help would be greatly appreciated.
>
> Stefan Kaes
>
> portax.com GmbH
> Zielstattstrasse 40, Geb.
2003 Dec 01
0
No subject
it were a Microsoft box... (Windoze is so stupid it'll never know the
difference!)
-----Original Message-----
From: samba-admin@lists.samba.org [mailto:samba-admin@lists.samba.org] On
Behalf Of Fred Jackson
Sent: Monday, July 30, 2001 10:39 PM
To: samba@lists.samba.org
Subject: a question?
Hi
does the command line
smbpasswd -j <domain> -r <PDC>
apply to clients joining a
2003 Dec 01
0
No subject
for this process is "root", that is correct. The PID 7247 is one of the
users, but the UID shouldn't be "root" and should be the username that was
authenticated during logon.
Anyone have same or similar problem? and how do I prevent this problem
from happening again? I would appreciate any help.
Thanks.
Will Sun
wsun@jpl.nasa.gov
(818) 354-2311
Return-Path:
2003 Dec 01
0
No subject
When I try the command
nmblookup -M TESTGROUP
querying TESTGROUP on 192.168.255.255
name_query failed to find name TESTGROUP #1d
My /etc/hosts file is
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost localhost.localdomain
192.168.100.101 testpc
192.168.100.100 linuxserver
/etc/samba/lmhosts is
127.0.0.1 localhost
2003 Dec 01
0
No subject
share in the samba box, from the PDC server itself. The log.winbindd and
log.nmbd are empty.
[2001/08/08 13:11:28, 3] smbd/reply.c:reply_sesssetup_and_X(865)
Domain=[EERDBR001] NativeOS=[Windows NT 1381] NativeLanMan=[] [2001/08/08
13:11:28, 3] smbd/reply.c:reply_sesssetup_and_X(876)
sesssetupX:name=[administrator]
[2001/08/08 13:11:28, 3] libsmb/namequery.c:resolve_lmhosts(733)
2003 Dec 01
0
No subject
However....
When I try the command
nmblookup -M LINUXSERVER
querying TESTGROUP on 192.168.255.255
name_query failed to find name TESTGROUP #1d
My /etc/hosts file is
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost localhost.localdomain
192.168.100.101 testpc
192.168.100.100 linuxserver
/etc/samba/lmhosts is
127.0.0.1
2003 Dec 01
0
No subject
read list (S)
This is a list of users that are given read-only
access to a service. If the connecting user is in
this list then they will not be given write access,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
no matter what the writeable option is set to. The
2003 Dec 01
0
No subject
cheers, jerry
---------------------------------------------------------------------
www.valinux.com VA Linux Systems gcarter_at_valinux.com
www.samba.org SAMBA Team jerry_at_samba.org
www.plainjoe.org jerry_at_plainjoe.org
--"I never saved anything for the swim back." Ethan Hawk in Gattaca--
Return-Path:
2003 Dec 01
0
No subject
share in the samba box, from the PDC server itself. The log.winbindd and
log.nmbd are empty.
[2001/08/08 13:11:28, 3] smbd/reply.c:reply_sesssetup_and_X(865)
Domain=[EERDBR001] NativeOS=[Windows NT 1381] NativeLanMan=[] [2001/08/08
13:11:28, 3] smbd/reply.c:reply_sesssetup_and_X(876)
sesssetupX:name=[administrator]
[2001/08/08 13:11:28, 3] libsmb/namequery.c:resolve_lmhosts(733)
2003 Dec 01
0
No subject
I will get a smbd process started. (If this is incorrect please let me know
;)
But this morning I did a quick ps -ax on my machine and found *two* smbd -D
in the process list. But as far as I know there is no connection to the
samba server right now.
I did connect to and disconnect from the server yesterday but I would think
that that connection would have been released by now.
Can anyone
2003 Dec 01
0
No subject
net use * \\samba\mgerdts
Debug level 10 says:
[2001/06/22 10:28:49, 1, pid=29656] smbd/password.c:pass_check_smb(554)
Couldn't find user 'mgerdts' in smb_passwd file.
[2001/06/22 10:28:49, 2, pid=29656] smbd/reply.c:reply_sesssetup_and_X(951)
NT Password did not match for user 'mgerdts'!
[2001/06/22 10:28:49, 2, pid=29656] smbd/reply.c:reply_sesssetup_and_X(961)
2003 Dec 01
0
No subject
... (port 138, setting options)...
[2001/07/10 20:11:23, 3] nmbd/nmbd.c:(541)
open_sockets: Broadcast sockets opened.
[2001/07/10 20:11:23, 2] lib/interface.c:(85)
added interface ip=141.43.132.161 bcast=141.43.132.191 nmask=255.255.255.192
[2001/07/10 20:11:23, 3] lib/util_sock.c:(832)
bind succeeded on port 137
... (port 138, setting options)...
[2001/07/10 20:11:23, 2]
2003 Dec 01
0
No subject
<----------------------------------------------------------------------->
Changes to user passwords are captured by a special DLL, which traps and
then stores the password changes in encrypted form in a private area.
On each synchronization schedule, the synchronization service first examines
the SAM file for changes, and then checks this private area for passwords
to be synchronized. Once
2003 Dec 01
0
No subject
remove unix password sync = yes
Reply on a question....
http://www.mail-archive.com/redhat-devel-list@redhat.com/msg04223.html
Good Luck,
Ries
Return-Path: <ries@franksintl.nl>
Delivered-To: samba@lists.samba.org
Received: from tiny.int.franksintl.nl (goblin.franksintl.nl
[195.193.231.154]) by lists.samba.org (Postfix) with ESMTP id
6771C4AC8 for <samba@lists.samba.org>; Thu, 17
2003 Dec 01
0
No subject
Please note that Windows 9x clients are not true members
of a domain for reasons outlined in this article. Therefore
the protocol for support Windows 9x style domain logons is
completely different from NT4 domain logons and has been
officially supported for some time.
Did you read this document? Let me know what needs to
be updated and i will take care of it.
Cheers, jerry
2003 Dec 01
0
No subject
more specific on what your problem is?
cheers, jerry
---------------------------------------------------------------------
http://www.valinux.com/ VA Linux Systems gcarter@valinux.com
http://www.samba.org/ SAMBA Team jerry@samba.org
http://www.plainjoe.org/ jerry@plainjoe.org
--"I never saved anything for the swim back."
2003 Dec 01
0
No subject
Are you using wins?
Try lmhosts for the start?
Are all machines on the same subnet?
Just a few hints to start with ...
Christian
>
>
> I have absolutely no clue what I could do to fix it. The only solution I
> can think of, is to downgrade to redhat 6.2.
>
> Your help would be greatly appreciated.
>
> Stefan Kaes
>
> portax.com GmbH
> Zielstattstrasse 40,