similar to: 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

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

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

hi, I hv recently installed and configured samba-3.0.10-1 with Ldap and smb tools. Everything looks good, i mean Samba, LDAP and smbldaptools everything. But now when i am trying to access the shares as well as trying to join w2k prof desktop to the domain its giving the error "The semaphore timeout period has expired" Can any one let me know what could be the problem? Thanks &

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.

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

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

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

Here is my first major problem with dovecot. I am running rc15 on FreeBSD 6.1. I run dovecot supervised by DJB's daemontools. I run only the pop3 service. A colleague informed me that pop3 service was simply not responding. They could not rcv mail. When I checked the server, tail-ing dovecot.log, here is what was scrolling: [wash at nbi ~]$ tail -f /var/log/dovecot.log dovecot: Nov 23

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

I upgraded from a perfectly working 1.6.2 asterisk installation (including fax via app_fax_digium) to 1.8.0 this evening. All my custom modules (including swift <thanks darren!>) are working fine except for fax. When a caller connects, asterisk switches to the fax context and hangs up the call. i've captured with: core set verbose 10 core set debug 10 fax set debug on sip

After upgrading to Asterisk 1.8.0, I am finding that my outbound SIP calls are being destroyed after 1 minute and 20 seconds (80 seconds). Asterisk is sending a BYE message - I have no idea why. http://jeremy.kister.net/tmp/20101115/sip.txt for a sip debug. can anyone suggest how i can further deal with this? -- Jeremy Kister http://jeremy.kister.net./

just thought this was cute enough to pass along, https://www.youtube.com/watch?feature=player_detailpage&v=GLwct15X_3g#t=135 -- Jeremy Kister http://jeremy.kister.net./

Howdy. Trying to set up a persistent SSH connection from a remote host, to my own machine with a LocalForward. I am running the ssh process in the foreground so it can be maintained by djb's daemontools to ensure that the connection stays open at all times. But, I am having a problem with the following command (even when run manually from a shell): ssh -N tarkin where in ~/.ssh/config I

Running Asterisk 1.6.2.11 on debian 5.0.6 with mpg123 1.4.3 when i start asterisk, i immediately see two mpg123 processes spawned which sit there forever. I can't imagine it's normal behavior, but if it is, please explain :) # /etc/init.d/asterisk stop stopping asterisk. #[...] # /etc/init.d/asterisk start starting asterisk. # psg aster root 14573 1 0 16:29 pts/2 00:00:00

I recently configured a SIP peer which i must specify my fromuser as my ten digit "DID". I send calls to this peer, but whenever Asterisk sends an options message, the fromuser is "asterisk". Is this a bug? Or is there some other config I must make ? register = 2155551941:123456 at 10.0.138.226/2155551941~600 [peer](!) type=peer context=inbound qualify=yes

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

Hello, I'm trying to run smbd with djb daemontools' supervise. Here's the way I followed: # 2/6/2002 # problem running samba-2.2.4 and supervise problem: run smbd with supervise subproblem 1: smbd & nnmbd with -D option deteach from tty, so supervise cannot control them; solution 1: we can patch smb/server.c (foreground patch) to prevent deteach, but a second

I have asterisk 1.6.2.11 talking to a cisco 1760 running ipvoicek9-mz.124-25b. whenever a call goes through the 1760's FXO or FXS (in or out) there is a 915 second maximum call time due to asterisk hanging up the call because of a "critical packet" being missed. I read doc/sip-retransmit.txt and I don't see anything there that is helpful to my situation - the asterisk box is

With app_swift 1.6.2 + asterisk 1.6.1.12, I've found that if you enter DTMF during cepstral playback, the first digit of ${SWIFT_DTMF} is [un]set in an odd way. for example consider: 999,1,Swift(some long message that you dont want to wait for|5000|5) 999,n,NoOp(DTMF: ${SWIFT_DTMF}) if while I am listening to the playback, i interrupt and dial: - "12345", SWIFT_DTMF is set to