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

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

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 &

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

[.. 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

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

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

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 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

My dd (sk98lin v7.09) supports 3c940 (Marvel/Syskonnect) which the stock v6.x drivers doesn't . Successfull tested on a Asus A-7N8X Deluxe with Marvell Gigabit Lan the dd is available at http://slackpkg.ath.cx/centos/disk/sk98lin/

I'm new to the lists so sorry about any faux pas I may have made. Also I apologize for the length, but I wanted to be sure I covered most of the details. I'm trying to do a PXE install on an Intel 1435VP2 server machine. The PXE install has worked on all the older machines in the cluster, so I know PXE is working. However, these new Intel server machines only support PXE booting from

Hello, I have an issue with my XEN system. I suspect that it might be a bug, but I''m no linux expert, so I don''t know. Here is my problem: I have an ASUS P7P55D-E Premium motherboard, and a Western Digital Caviar Black SATA-III 1TB hdd. I am trying to use AHCI. The dom0 is an Arch Linux. The dom0 boots fine until Intel VT-d is enabled in the BIOS. When I enable it Arch

Hi I'm getting a "semaphore timeout period has expired" error trying to connect a WinXP desktop to out linuxbox. (Redhat 7.1 / samba-2.0.7-36) I can't seem to find help about this in the documentation. Has anyone had any experience with this? Thanks Stuart -------------- next part -------------- HTML attachment scrubbed and removed

Is anyone using sk98lin Gigabit Ethernet adapters under CentOS 4.x? The version of the driver that ships with CentOS 4.x kernels was too old to support the onboard NICs on some Intel server boards that we recently got, so we installed a newer driver using DKMS. However, we're having problems finding a stable driver to use: the first version that we tried (7.09) gave a kernel panic when I ran

Hi team, I use Samba 4.3.12 as a printserver with ~900 printers, and it takes about 20 seconds for rpcclient enumprinters command to finish. However, sometimes it gets stuck and returns WERR_SEM_TIMEOUT for no apparent reason, and this timeout always takes exactly 12 seconds. I was thinking maybe there is a hardcoded timeout somewhere that is shorter than expected 20 sec time for returning my

On Tue, Dec 13, 2016 at 10:48:38AM -0500, Alex Korobkin via samba wrote: > Hi team, > > I use Samba 4.3.12 as a printserver with ~900 printers, and it takes about > 20 seconds for rpcclient enumprinters command to finish. However, sometimes > it gets stuck and returns WERR_SEM_TIMEOUT for no apparent reason, and this > timeout always takes exactly 12 seconds. > > I was

[+cc Intel folks] On Fri, Aug 31, 2018 at 03:30:57PM +0800, Daniel Drake wrote: > On over 40 Intel-based Asus products, the nvidia GPU becomes unusable > after S3 suspend/resume. The affected products include multiple > generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs > many errors such as: > > fifo: fault 00 [READ] at 0000005555555000 engine 00 [GR]

On Wed, 17 Jan 2024 11:23:12 -0300 Elias Pereira <empbilly at gmail.com> wrote: > hi, > > Still dealing with the error. > > In some posts on the internet, a user reported that he has more than > 40k objects in samba and that's why the error occurs. > > When running the command "samba-tool dbcheck --cross-ncs --fix --yes" > reports that it has

With --async-op does it run in the background? Is the output saved in a log? On Wed, Jan 17, 2024 at 12:12?PM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Wed, 17 Jan 2024 11:23:12 -0300 > Elias Pereira <empbilly at gmail.com> wrote: > > > hi, > > > > Still dealing with the error. > > > > In some posts on the internet, a user