Displaying 20 results from an estimated 1100 matches similar to: "No subject"
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
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
<<<<<<<<<<<<<
I connect my homedir from the testserver and start Lotus Notes.
Lotus Notes is infamous for it's sensitivity for 'non-optimal' network
connections. Notes tries to lock certain files and complains immediately if
that fails.
> 3. does the log message always fail at the same offset/count:
> (fcntl_lock: lock failed at offset
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
network. I did read somewhere on the web (several years ago) of a guy
who managed to boot windows from the net.
With the start of Win 98/ME/ etc.etc it's not posible anymore.
I currently use PXE to install machine from the net using bpbatch that
works great only bpbatch is not really under developnt and the script
language is a bit buggy.
I see only one option to boot windows from the net and
2003 Dec 01
0
No subject
TEST 3
If you get a "connection refused" response then the smbd server may
not be running. If you installed it in inetd.conf then you probably
edited
that file incorrectly. If you installed it as a daemon then check
that
it is running, and check that the netbios-ssn port is in a LISTEN
state using "netstat -a".
Note: You have xinetd not inetd on the redhat box. To avoid all
2003 Dec 01
0
No subject
workgroup but also a domain logon server. The NT box happily accepted
mounts from users originally only known only to Samba.
Everything fine again, but the next day they came in and told me about
people finding complete new mounts on their workstations. To describe
this:
A user normally has
C: local
H: \\SAMBASRV\HOMES
Z: \\SAMBASRV\HISGROUP
These are mounted by a local script and
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
And route print?
Do you have any servers on the WAN? (or is everyone connecting to the
servers THROUGH the WAN?)
Can you see the samba machines at all in network neghborhood?
What happens when you type in the UNC of a samba server manually? (i.e.
\\SAMBASERVERNAME)
I hope I can help you, and I'm trying, but I'm not a samba guru.
-Dan
PS. Please change your email type to PLAIN TEXT from
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
copy d:\bugs.ps \\ouessant\lexmark
after having deleted all the samba log files and restarted the SMBd daemon from the SWAT Web interface.
This leads to the INTERNAL ERROR, see samba.oulx
Now, to locate the problem, I tried the same kind of command on the same file, bugs.ps, but using the SMBCLIENT application from the Linux server itself, without changing anything, nor restarting the SMBd
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
... (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
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
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
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
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
the files when you attempt to rename it. This is caused by Window's Media
Player loading the file when you click on it.
To work around this I had to go into Windows Explorer and change the folder
options from "Enable Web Contents in Folders" to "Use Windows Classic
Folders". This way, Windows Media player won't load the file when you click
on it.
Just trying to save
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."