similar to: Semaphore Timeout Period has Expired on Win2K

Displaying 20 results from an estimated 60000 matches similar to: "Semaphore Timeout Period has Expired on Win2K"

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
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
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
2005 Feb 09
0
Error:The semaphore timeout period has expired
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 &
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
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
2002 May 23
0
Semaphore Timeout on from Win2K to Samba
I have been using Samba w/out any problems what so ever for the longest time, but today, I cannot connect to the linux box (shows up in network neighborhood as 'LINUXSERVER'), but when I try to connect from a win2K machine (which normally connects w/NO problems). Here is the output from /var/log/messages (appears the problem is in smbd) May 23 11:34:14 fileserver nmbd[1423]: [2002/05/23
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
2024 Jan 03
1
{Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
hi, After a "samba-tool drs showrepl" I saw that there had been an error in the replication of ForestDnsZones. I ran a "samba-tool drs replicate dc2 dc3 DC=ForestDnsZones,DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br -d10" and the error below occurred. ERROR(<class 'samba.drs_utils.drsException'>): DsReplicaSync failed - drsException: DsReplicaSync failed
2024 Jan 17
1
{Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
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
2024 Jan 17
1
{Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
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
2024 Jan 17
1
{Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
On Wed, 17 Jan 2024 16:14:48 -0300 Elias Pereira <empbilly at gmail.com> wrote: > With --async-op does it run in the background? Is the output saved in > a log? Just add it to however you ran 'samba-tool drs replicate', I think it will stop the error messages in your logs. Rowland
2024 Jan 17
1
{Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
Okay. How do I know if the command really ran correctly? :D On Wed, Jan 17, 2024 at 4:26?PM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Wed, 17 Jan 2024 16:14:48 -0300 > Elias Pereira <empbilly at gmail.com> wrote: > > > With --async-op does it run in the background? Is the output saved in > > a log? > > Just add it to however you ran
2024 Jan 17
1
{Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
On Wed, 17 Jan 2024 16:43:26 -0300 Elias Pereira <empbilly at gmail.com> wrote: > Okay. How do I know if the command really ran correctly? :D You ran: samba-tool drs replicate dc2 dc3 DC=ForestDnsZones,DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br -d10 and got an error message. If you run: samba-tool drs replicate dc2 dc3 DC=ForestDnsZones,DC=campus,DC=sertao,DC=ifrs,DC=edu,DC=br
2002 Oct 01
1
Semaphore timeout
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
2024 Jan 17
1
{Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
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 "Checking 16529 objects (Checked 16529 objects (0 errors))". So it wouldn't be my case. Running "samba-tool drs
2024 Jan 04
1
{Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
Hi Rowland, Could you tell me what the correct permissions are for the bind9 files? On Wed, Jan 3, 2024 at 5:46?PM Elias Pereira <empbilly at gmail.com> wrote: > The only 'problem' I can see is that the group is set to 'bind' instead >> of 'root', why is this ? > > If I'm not mistaken, I did it on the wiki, but maybe I needed an older >