similar to: Errors in smbd log file

Hello, I was using version 3.0.14 and upgraded to 3.0.20a. I did not change my config, however, I am seeing some serious problems now, and I am not sure what to do about it. I noticed there were a large number of changes between these two versions. I looked at the changes briefly, but there are just so many. This samba server is a domain memmber, on an ADS domain with a win 2003 enterprise

Hello, I run a samba (v3.0.10) PDC and openLdap server on the same machine. They work fine, except sometimes the smb server cannot contact the ldap server. From a windows client, it looks like the server gets stuck, and it takes a few minutes before the shares are available again. In the /var/log/messages file, i get these error messages :

Hi list, Since I've upgraded from Version 5.0 to 5.1 i have strange problems with samba. Since 5.1 the connection from a XP client to the samba server disconnect often, especially then i write a file to the share after some idle time. Some informations of my config. The Box is a Samba PDC for a little Windows Domain with a ldap backed. I used this config on Centos 4.x and 5.0 without

I have four samba servers connecting into a samba PDC (using ldapsam as password backend) and all of the servers get the "transport end point not connected" error. I've looked in the groups but cannot find anything that helps. I've tried to set my oplocks=no and other similar settings but nothing seems to help. The only thing that seems to limit excessive sleeping smbd

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:

Greetings Experts! Sorry for my poor english, but I?m inside of a terrible nightmare!!! I?m using Samba+LDAP has about 2 months ago without problems, but in the last 4 hours, the system is absolutelly unstable. I couldn?t upgrade or patched anything. The problem simply has appeared. Principally system characteristics: - Sun Fire V880 running Solaris 9 - openldap-2.2.23 - nss_ldap-232 -

Hi all, here's hoping you can help with a problem I have got. I am currently running samba 3.0.7-1 on a Suse 9.0 system and I am having the following problem. I am trying to get my samba server to join a windows NT4 domain called BVFL-DOM and then use winbind to get user names from that domain to be use samba. The samba box joins the NT domain without a problem and I can use NT server

Mates, I'm trying to solve some log errors I getting. I have samba 3.0.7 installed on Suse 9.0. It has been happening intermittently for several months. I don't know if this is XP client related or what. Any thoughts: The errors are: Feb 9 20:00:33 skyline smbd[14408]: [2005/02/09 20:00:33, 0] lib/util_sock.c:get_peer_addr(1000) Feb 9 20:00:33 skyline smbd[14408]: getpeername

Hello, I'm having trouble configuring an Ubuntu Hoary Samba server to use LDAP for authentication (the server is named "dixie"). I'm basing my configuration on another server here at work that connects just fine. When I try to just list samba shares on dixie with $ smbclient -L dixie -U faker It takes quite some time for the request to go through before failing. Looking at the

Hi, I am discovering several error messages from one of our samba servers. Logcheck says: Security Events =-=-=-=-=-=-=-= getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected getpeername failed. Error was Transport endpoint is not connected

============== The problem: ============== I am in the testing stages of implementing a Samba domain. My user is logging on to a standard win xp SP2 desktop, with the samba pdc, supplying the credentials. The logon screen disappears and an "SAS window: winlogon.exe - Application Error" box pops up on the Win XP screen. If I click OK the machine reboots. My user can log onto the Debian

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 have a laptop that I need to be able to connect to my samba shares with its wired connection and its wireless connection. It works fine when connecting from the wired ethernet connection but it stops working once I disable the wired connection and connect to the wireless network (both networks are on the same subnet). The IP address for the wired connection is 192.168.1.112

Hello, I tried to google this, but haven't found anything really helpful so far. I get stuff like this at one Samba-3.0.9-Domain-Member-Server: > [2005/03/06 13:30:47, 1] smbd/service.c:make_connection_snum(647) > fre2003 (192.168.86.11) connect to service users initially as user fre (uid=1006, gid=1000) (pid 31447) > [2005/03/06 13:31:57, 1] smbd/service.c:close_cnum(835) >

Hi, there I created a new samba 3.4.5 server on RHEL 5.2(it's a VirtualBox!) and only copied over the old smb.conf from samba 2.0.22(it's a real box) with little changes. I shutdown the old samba and startup the new one with the same IP and domain name. Everything works fine on XP client side without any changes. LDAP backend stays the same on a separate machine. I use the same package

Hi there, Since upgrading our debian sarge boxes to 3.0.23c, we have found that we are unable to connect to shares using the official hostname of the servers (short or fully qualified) but can still use its netbios aliases (again, short or fully qualified). As nothing else has changed in our configuration, I think that the change of behaviour is down to the newer release and can find nothing in

I have a similar error, I can us XP workstation ad domain members, and they even use the shares, but two or threes times per day the connection resets, and I have to kill the smbd and start it again (only restart does not work). Take look at my LOG. Any idea? [2005/10/04 11:02:10, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2005/10/04

Well, I WAS puzzled by this persistent error. Then I stumbled onto something and I might have fixed it. It looks like with an XP client, XP might be trying to renegotiate which port to talk (445 or 139) over at the start of every transaction. Whichever one answers first is used for the rest of the transfer. I added this to smb.conf and restarted samba: smb ports = 139 I can't tell if

Dear all, I have a SuSE9.1 box running as a file server with mp3's on it. The /var/log/messages log file is recording the following errors which I don't understand and perhaps you could assist me: Nov 17 11:25:05 mp3-nrg smbd[7903]: [2004/11/17 11:25:05, 0] lib/util_sock.c:get_peer_addr(975) Nov 17 11:25:05 mp3-nrg smbd[7903]: getpeername failed. Error was Transport endpoint is not