Hi,
I'm having trouble joining a Samba 2.2.7a server running on RH9 into a
domain that is being served by a Windows 2003 server running AD in mixed
mode. The server successfully joins the domain when using smbpasswd,
however, when running smbclient -L localhost I get the following error:
Hi,
We've been having lots of issues with our Linux based Samba servers since
the Windows domains have migrated to AD. We were hoping and expecting
that, at least in the short term, we could run in mixed mode and not
have to make any changes to our Samba servers. However, things just aren't
Hi,
We've been experiencing this same problem, however, with Samba
3.0.7-1.3E.1 running on RedHat ES 3.0. We've also experienced this on
2.2.7x on RedHat 9. The problem has been intermittently happening over the
last several weeks, (I've posted list about it).
This message, along with the
Hi,
We continuously see these errors in our logs. I've done some searches on
this but nothing seems to point to anything specific.
Any ideas?
-John
Dec 23 20:14:41 valhalla smbd[3574]: [2004/12/23 20:14:41, 0]
lib/util_sock.c:get_peer_addr(1000)
Dec 23 20:14:41 valhalla smbd[3574]:
Hi Tom,
This particular server is running samba 3.0.7-1.3E.1 on RH 3.0. The domain
is running AD in mixed mode, (I'll include the smb.conf below), and I
believe the Windows server is Windows 2003.
Our clients are a mix of Win2k and WinXp. The server is running Clearcase
and the clients access
did not
respond after 2 milliseconds.
John DeBella
12/20/2004 09:28 AM
To: [EMAIL PROTECTED]
cc:
Subject:Domain password server not available
We are running samba 3.0.7-1.3E.1in an AD domain which is running a PDC
emulator. The samba servers
We are running samba 3.0.7-1.3E.1in an AD domain which is running a PDC
emulator. The samba servers are configured with security = domain and on
some servers the password server is specified while on others we are using
*.
We very frequently see the following messages in the log files of the
Hi,
Is it enough to run service smb reload when changing the password server
setting in smb.conf or is a complete restart required?
-John
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Would anyone know what these errors mean?
Dec 14 01:22:36 valhalla smbd[28506]: tdb_chainlock_with_timeout_internal:
alarm (10) timed out for key SENECA in tdb /etc/samba/secrets.tdb
Dec 14 01:33:33 valhalla smbd[7266]: cli_nt_session_open: cli_nt_create
failed on pipe \NETLOGON to machine
We're still experiencing this issue. I've observed a couple of things
during the latest event.
I mentioned before that netstat -a shows many smb processes in CLOSE_WAIT
state when this problem occurs. I happened to strace on a process that was
stuck in recvfrom(1315,. When I killed this
We have upgraded to the 3.0.7-1.3E.1 RH Samba update and this problem
still occurs. Has anyone else experienced this or does anyone have any
ideas on what's causing this?
-John
[EMAIL PROTECTED] wrote:
We've seen Samba crash and burn twice in the last 48 hours - it just
started happening,
Hi Jerry,
Thanks for the reply. I'll check this if it reoccurs again.
We've turned off strict locking to see if this helps. This was on a hunch
that it was a lock issue.
To answer your question, the access to the main share on this server is
via the automounter to a local directory. For
Looks like it's a link to /var/cache/samba/gencache.tdb.
-John
Gerald (Jerry) Carter [EMAIL PROTECTED]
12/08/2004 11:53 AM
To: [EMAIL PROTECTED]
cc: [EMAIL PROTECTED]
Subject:Re: [Samba] smbd hung processes - Samba 3.0.7
-BEGIN PGP SIGNED
13 matches
Mail list logo