similar to: after 3.0.9 upgrade windows wants to sync home drive

Jan. 21, 2004 Dear All, I have enjoyed some success with Samba version 2.2.2. I am using it to serve Micro$ Access to end users. It works very well on a prior version of Unix, with older Win2k clients. Now, with my current version, and Win XP Pro, I have problems. Periodically, they get abruptly kicked out. I get syslog errors which look like: kforce-adm-# tail syslog Jan 7 16:29:09

Hello all, I'm having troubles with a samba 2.2.2 server (on debian). Some clients are having problems connecting, and are filling the logs with messages like those below. This isn't the first time I've had this problem, nor is it the first site. This is a win98 box I'm having troubles with now - it fails trying to log onto the domain... although I'm fairly sure it affects

Dear all, I have a linux server that uses redhat AS4.I want to make a samba file server.Because we have a windows 2003 domain,I must use "security = ADS".The samba version is samba-3.0.10-1.4E.9. The samba server joined windows 2003 domain successful.I can find samba server in the "network neighborhood".Client PC access samba server must confirms with PDC.The domain member

I recently upgraded my Linux install (Debian potato to woody) and now Samba is no longer playing nice with Windows 2000. I can use smbclient on the samba machine to connect to itself, so at least that's working. The error from Windows is: "The semaphore timeout period has expired.". I deleted the smb.log file at one point in an effort to reset it. I figured it'd be created

Hi. Iv'e set up samba as PDC with LDAP and trying to connect a Windows XP Pro machine to the domain. When i'm trying to join the domain XP popups a logon-windows, but no one of the accounts i have added will work to login, XP say something like "Cannot find the selected domain or cannot connect". I've also detected an error in /var/log/samba/log.nmbd which i dont

Iv'e set up samba as PDC with LDAP and trying to connect a Windows XP Pro machine to the domain. When i'm trying to join the domain XP popups a logon-windows, but no one of the accounts i have add will work to login, XP say something like "Cannot find the selected domain or cannot connect". I've also detected an error in /var/log/samba/log.nmbd which i dont understand:

The account is not authorized to log in from this station. This is even though I have in smb.conf: hosts allow = 192.168.1. Which should allow the whole subnet. Thanks! Jen ----- Original Message ----- From: "Ahmad Yahya" <getlucky@telkom.net> To: <samba@lists.samba.org> Sent: Sunday, December 02, 2001 10:23 PM Subject: Re: Can't connect from Windows 2000 >

The account is not authorized to log in from this station. This is even though I have in smb.conf: hosts allow = 192.168.1. Which should allow the whole subnet. Thanks! Jen ----- Original Message ----- From: "Ahmad Yahya" <getlucky@telkom.net> To: <samba@lists.samba.org> Sent: Sunday, December 02, 2001 10:23 PM Subject: Re: Can't connect from Windows 2000 >

I?m using SAMBA 3.0.4-6.3E as a PDC. I have Win98, WinNT4 and Win2000 clients successfully joined to the domain. But I can?t get an XP box to join. The XP machine can ?see? shares on the SAMBA PDC but strangely does not show up in network neighbourhood. You can find it if you search for it. The PDC is just using smbpasswd, no LDAP The machine add line in my smb.conf is as follows..... add

On a server that has been running smoothly since it was setup, and with no changes to configurations or network or anything, users cannot save a shared QuickBooks file. they have been regularly using, updating and saving to this file for a few months. All users are able to create and update other files in the same share. I have not confirmed if they are able to create and update new QuickBooks

Hi, About 10 days ago, I started looking at the "getpeername failed. Error was Transport endpoint is not connected" message appearing on our logs. This message was being produced very frequently during the day and somewhat less frequently at night. Anyone can help me to fix it ?? Here're message info ! Our configuration is samba 3.0.10a Our network has about 60 XP Pro PC's

I have samba setup as a fileserver with winbind on an NT 4 domain. I keep getting the errors shown below constantly, and have no clue what could be causing it. If you have any clues please let me know. Jun 3 18:08:27 baker smbd[7436]: [2005/06/03 18:08:27, 0] lib/util_sock.c:read_socket_data(384) Jun 3 18:08:27 baker smbd[7436]: read_socket_data: recv failure for 4. Error = Connection

Hello List, I am running Samba 3.0.10-1.4E on RHEL 4.0. I was able to join this server to the domain using the 'net ads join' command and it created a machine account in AD with the name of the server. My issue is that I can authenticate using domain credentials when I access the server from a Windows computer using //SMBSERVERNAME/SHARE, however when I access the server using

I'm getting some strange error messages on my Samba server. Does anybody know what these mean, or where I can look them up? I also don't -think- I'm getting the performance I should be. Any help is much appreciated, Craig Pentium II-300Mhz 128MB RAM Solaris 2.6 Samba 2.0.6 Intel 10/100 NIC Running at 100Mb/Full Duplex Clients are mainly WinNT 4.0-SP4 running ArcView. Feb 27

I am using the defaults that came with the samba RPM package on Mandrake 10.1. For socket options, it has: socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 Is that something that may fix the problem if I change it? Pablo mschwartz@dcscorp.net wrote: >Pablo, you might have incorrectly set some settings in smb.conf. Check >your settings for socket options. I don't mess

I have Samba 2.07 on Mandrake 7.2 distro. I am proxying a DSL connection successfully over Squid. I do not have ipchains running but with all the BS Mandrake like to pack on it's hard to tell what it's scripts all do. All the tests with the smbclient on the samba machine work fine. Also all the test with nmblookup. I have a clean Ping from both ends. When I use smbclient to view my Win98

I am having some problems getting a samba server to work with Windows 2000 Active Directory. I am at the point where I can successfully list all users and groups, using the wbinfo command, and was able to join the domain with the net join ads ... command. I can also see the computer in my network neighborhood ... however, when I click on it .. it prompts for a username / password .. and

Packet send failed to 62.101.92.90(137) ERRNO=Network is unreachable [2004/05/03 10:27:45, 0] nmbd/nmbd_packets.c:reply_netbios_packet(975) Hi list, once again looking for some good advice. I apologize for the long email and for the mistakes I could have done. I'm running Samba 3.0.2-6.3E on White box linux 3.0 kernel 2.4.21-4.EL (clone of Red Hat EL 3.0), the environment is a Win 2k ADS

Hello, I have two error messages on user.log as follow : 1. [2001/11/26 14:41:07, 0] smbd/oplock.c:oplock_break(813) oplock_break: no break received from client within 30 seconds. oplock_break failed for file aa1/EMI/SIGVM00 (dev = 302, inode = 194716). [2001/11/26 14:41:07, 0] smbd/oplock.c:oplock_break(859) oplock_break: client failure in oplock break in file aa1/EMI/SIGVM00 2.

Samba gives read_socket_data: recv failure for 4 when trying to write or read with NT4 WS, why? Samba 2.0.7, NT WS 4.0 sp6, Slackware 7.0 (glibc 2.1.2), linux kernel 2.2.15 with crypto patch patch-int-2.2.14.1. Samba configured/compiled with the following switches: --with-smbmount --with-syslog Most of the time writing to, or copying from samba shares, hangs, then fails. Trying to copy