Displaying 20 results from an estimated 2000 matches similar to: "Error:The semaphore timeout period has expired"
2005 Feb 07
1
RPM Build error for Samba-3.0.10-1.src.rpm
Hi,
I am trying to install samba 3 on RH Enterprise Linux AS with LDAP and
SMBLDapTools. I hv downloaded the Samba-3.0.10-1.src.rpm from Samba site.
I want my samba to support ACLs, Profiles, LDAPSAM etc. To make it work i
edited the SPECS file and added the following entries
- - with-acl-support
- - with-profile
- - disable-static
- - with-msdfs
- -with-ldapsam
After adding the
2005 Mar 21
2
SAMBA3 + LDAP = PDC => ROUND 3!
Okay, I've upgrade samba, now I use samba3.schema who is with my suse 9.2
So I delete all in /var/lib/ldap and in /var/lib/samba
Redo smb-populate blablabla (from the howto
http://samba.idealx.org/smbldap-howto.en.html)
So now when i would like to join my Samba domain :
[2005/03/21 15:45:51, 2] auth/auth.c:check_ntlm_password(312)
check_ntlm_password: Authentication for user
2005 Jan 03
3
New to Samba world
Hi Team,
I am new to Samba.
As company has decided to install Linux based file and print server, we are
planning to use Samba and LDAP
But prior to proceed further, I wanted to know how samba works, what all
things needs to be considered at the time of installation.
So can any one let me know the same?
Thanks & Regards
Mandar Kulkarni
2005 Aug 16
0
FW: Error:The semaphore timeout period has expired
UPDATE:
We found out that there was still an entry in /etc/rc.local to start up
the old SAMBA after upgrading and setting up to run from inetd.conf.
Once the /etc/rc.local entry was removed, we no longer receive the
"semaphore timeout period has expired" messages and we are able to
connect to the shares.
Ben Burruel
Sr. Systems Manager
Metrics & Mainframe Capacity Planning
San
2002 Feb 26
1
semaphore timeoit period expired (root is full)
I have had samba running on my freebsd box for about 2 years now, and my / partition is 50MB (it is just a fileserver with ssh and
nothing more). However, recently (about a month or two ago) it disconnects itself from my LAN with warnings like: semaphore timeout
has expired. I go to the console on the box and it says that the disk is full (its not, but the root directory is at 101%) I cannot
2004 May 19
0
The semaphore timeout period has expired
Hello everyone
I have samba 3.0.3pre2-SuSE running on SuSE 9.0 i386, this is from SuSE
rpms not source. The box is joined to a 2k3 domain, wbinfo works fine,
acls work and users are authenticated properly.
I had a problem yesterday and cannot seem to find a solution:
I have been copying data across from the old SBS server, this seems to
work fine for about 5 minutes, then completely crashes
2004 Jun 25
1
The semaphore timeout period has expired
Hello Hamish.
I found your message just googling for Suse and sk98lin.
Did you solve your problem?
I had the same case and only way to restore was to change NIS driver speed
settings from AUTO to 10Mb. And it was not related to OS as the same problem
is in WXP ( I have dual boot, ASUS P4P800, integrated GB NIS ).
Oleg.
2006 Mar 18
0
error:semaphore timeout period has expired
Hi all
I have a samba pdc (3.0.21c) with openldap (2.3.19) on a Redhat Enterprise
Linux 4 (2.6.9-5EL-SMP) kernel
i have Domain Member servers (samba server), i redirect my users to share
declared to in my domain member servers.
using logon script which gets executed when users logon . my clients use
windows 2k professional and windows xp.
my logon script is
@ echo off
net time \\mypdc /set /yes
2003 Dec 11
0
Semaphore Timeout Period has Expired
Hi. We are running Solaris 2.6, Samba 2.0.0.
NT workstations can connect to all samba shares, but W2K workstations can't. Some users get "Semaphore Timeout Period has expired", some get "Network name not found". The NT and W2K users login to the same NT domain. There is a WINS entry matching the Unix server hostname. Any ideas? Thank you. -Anoosh
Here is smb.conf
2005 Feb 24
0
The semaphore timeout period has expired
[.. most data for the archives ..]
I've got several windows 2000 machines and a samba 2.2.12 on solaris 7.
for years only one of the windows machines has ever needed to connect to
the samba server. just a couple of days ago, it was necessary for a
second machine to connect to the samba server. Whenever the second
machine tried to load the network share, windows came back with its "The
2004 Mar 18
0
Semaphore Timeout Period has Expired on Win2K
Tom,
Did you resolve your problem:
Question: is this a Samba configuration error or a Win2K configuration error. The 98 and ME connect just fine to SAMBA.
If so, what was the answer?
Thank you, Jim Majczek
2004 Jan 28
1
new error when upgrading :P "The semaphore timeout period has exp
We have newly installed ADSL/speedTouch 510 modem. After the installation,
we are getting problems with out Win2K machines. On out NT workstation
everything is OK, but on the Win2K we are getting following error,
"The semaphore timeout period has expired" whne trying to connect to the
domain (GARAGET),
My Network Places
Entire network
MS Windows Network
Garaget (our
2004 Jun 30
1
Semaphore Time Expired
I am running Debian 'woody' with Samba 3.0.2 and am having a sparatic
problem on my network.
Some users will suddenly lose their connections to the samba shares and
when trying to log in
to the system again will get an error that windows cannot locate their
roaming profile - "Semaphore time period has expired".
It seems that if they wait for about 15 minutes they can then
2023 Apr 09
1
can't install nser...
It says that nser requires the most recent version of magrittr that you do
not have installed. You must update magrittr before attempting to install
nser:
update.packages(oldPkgs = "magrittr")
or at the prompt you were presented before, choose to update magrittr
before installing nser.
On Sun, Apr 9, 2023, 17:55 akshay kulkarni <akshay_e4 at hotmail.com> wrote:
> Dear
2005 Dec 24
1
master.password instead of LDAP database.
Good day.
Help me please to solve my problem to login a user to samba domain.
Samba accepts user authorisation only if a user account exists both in
master.password and LDAP database.
Note that uid and gid are taken from master.password instead of LDAP
database.
Why?
my smb.cf
[global]
dos charset = CP866
unix charset = KOI8-R
workgroup = FISH
server string = Samba Server
passdb backend
2005 Dec 21
0
Can not login to the domain. User serg in passdb, but getpwnam() fails!
Hi everyone.
I am installing an Samba 3 PDC with an OpenLDAP backend.
I am currently having a problem when I try to login to the domain with
my username and password. But no such problem when i am trying to join
to domain or connect to a share.
So, i get the following error :
[2005/12/21 18:08:02, 1] auth/auth_util.c:make_server_info_sam(840)
User serg in passdb, but getpwnam() fails!
2008 Jan 02
0
winbind initialization: GetDC got invalid response type 21
Hi all,
I'm running Samba 3.0.28 on CentOS 5.1 as a PDC. I'm having problems
with winbind taking a long to initialize or reconnect to the domain.
For example, starting winbind and then checking the trust secret takes
~30 seconds:
# time /usr/local/samba/bin/wbinfo -t
checking the trust secret via RPC calls succeeded
real 0m34.055s
user 0m0.008s
sys 0m0.019s
In the logs
2004 Jul 19
2
Affordable SIP Phone - Stiil a Myth?
Folks!
This is to let all of you know that I am making D'Link make an all out effort to make D'Link Phone DPH80 and DPH100 work with Asterisk. I have provided the Asterisk Platform to D'Link's R&D Division located in Goa, India, where their IP phone's SIP Bios is undergoing modifications based on my recommendations/suggestions. I have also provided the test bed &
2007 Jan 27
0
debugging smbldap-useradd failures
Hi, I just thought I'd post here some notes after a loong bugsearch.
Keywords:
failed to perform search; Unexpected EOF
using Domain Admins to add machines
The problem was that I got this in the sambalog:
_samr_create_user: Running the command `/usr/sbin/smbldap-useradd -w
"machine$"' gave 127
Part of the problem was that this isn't a lot to go on, and the command
1998 Apr 01
0
[Fwd: Semaphore problem on HP-UX ?]
Hi Jeremy,
Thanks for your prompt response. I implemented your suggestion
and added those lines to includes.h, recompiled and reinstalled the
samba on the test machine. Unfortunately it made no
difference. :-(.
I added some debugging code and looked what happened :
--------------------------------------------------------------------
DEBUG(4,("Trying sysv shmem open of size