similar to: How can I solve this problem that cause"getpeername failed. Error was Transport endpoint is not connected"

Hi !!! I've Samba 3.3.12 running on AIX, I have a few windows 7 using a shared resource on that server. This is the shared resource definition: [shared_disk] comment = shared_disk path = /home2/nfs-chiappe/shared_disk valid users = user1,user2 write list = @staff read only = No create mask = 0764 This particular Windows 7 Computer is driving

On Wed, 4 Jan 2017 15:58:39 -0300 Andres Tarallo via samba <samba at lists.samba.org> wrote: > Hi !!! > > I've Samba 3.3.12 running on AIX, I have a few windows 7 using a > shared resource on that server. > > This is the shared resource definition: > > [shared_disk] > comment = shared_disk > path = /home2/nfs-chiappe/shared_disk >

This samba is scheduled for upgrade. We've been testing samba 4.3.8 packages (from BULLFreeware) on other AIX. It was not easy the install, even with RPM packages. I hope to do the upgrade soon, but I need to have this particular user working now. What puzzles me is that I have other windows 7 PCs happily working on the same resource. 2017-01-04 16:21 GMT-03:00 Rowland Penny via samba

I am trying to access a samba share from windows 7. The samba version is 3.3.3 on FreeBSD 7.2, The samba daemons are running and I can see the server in my Network Places on the Windows client. When I try to login using the username "spacebizall" and password (the same as the account on the server) I receive an "unknown username or password" error. I installed the registry

I have a curious message I get repeatedly every so often on a samba domain member that serves up our network's home and group shares. [2009/07/07 12:24:56, 0] lib/util_sock.c:read_socket_with_timeout(939) [2009/07/07 12:24:56, 0] lib/util_sock.c:get_peer_addr_internal(1607) getpeername failed. Error was Transport endpoint is not connected read_socket_with_timeout: client 0.0.0.0 read

I'm using samba 3.5.6 + PDC and connected to LDAP directory In log level 1 there is many entries like this : Feb 18 18:13:42 samba smbd[21646]: getpeername failed. Error was Transport endpoint is not connected Feb 18 18:13:42 samba smbd[21646]: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer Is it a problem ? or just an informative event ? Feb 18

I have a problem with samba (3.2.3) not working properly with windows clients. I run a FC11 samba storage server, that has windows and mac client machines connecting to it. So far mac clients work. However windows client, whenever I try to install some application that is stored on the samba server, or even copy a very large file (few gbs) I get this in /var/log/messages and the file

Greetings list, I am about setting up a domain controller in a little company, so I choose samba (debian lenny) and I did it against openldap. Everything seems to be ok in the server but when I try to log in (windows client) I have a bizarre output: it said that my profile will not be saved. And after that when I try to connect to virtual machine running in the same computer, it doesn't work:

Every so often I will see this in my log file: smbd[1034]: [2009/02/02 08:47:21, 0] lib/util_sock.c:get_peer_addr_internal(1607) smbd[1034]: getpeername failed. Error was Transport endpoint is not connected smbd[1034]: read_socket_with_timeout: client 0.0.0.0 read error = Connection reset by peer. smbd[1036]: [2009/02/02 08:47:22, 0] lib/util_sock.c:read_socket_with_timeout(939) smbd[1036]:

Samba 3.2.5 I'm running into an issue when using Vista to access Samba shares. I'm able to connect intermitently and it stays connected for a brief period of time (under 60 seconds) before I get the following error on the Vista box: "Network path was not found" In syslog it shows: [begin] [2008/12/09 11:09:03, 2] auth/auth.c:check_ntlm_password(308) check_ntlm_password:

Hi All, I installed OpenSUSE 11.0, updated samba server to 3.2.4 version. Added two users in linux and samba with user names "test1" and "Test2". (Please note the capital letter in Test2). Created two shares in /srv/samba/shares "test1" and "Test2". The permissions of the shares are as below. drwx------ 2 test1 users 4096 2009-12-11 12:42 test1 drwx------

This is the first time I've noticed this with Samba 3.2.8 on Irix: [2009/02/19 16:40:15, 1] smbd/service.c:make_connection_snum(1194) eowyn (161.253.154.245) signed connect to service warburg initially as user warburg (uid=123, gid=20) (pid 13408) [2009/02/19 17:20:06, 0] lib/util_sock.c:read_socket_with_timeout(936) [2009/02/19 17:20:06, 0]

Every so often I will see this in my log file: Feb 2 08:47:21 int-torino smbd[1034]: [2009/02/02 08:47:21, 0] lib/util_sock.c:get_peer_addr_internal(1607) Feb 2 08:47:21 int-torino smbd[1034]: getpeername failed. Error was Transport endpoint is not connected Feb 2 08:47:21 int-torino smbd[1034]: read_socket_with_timeout: client 0.0.0.0 read error = Connection reset by peer. Feb 2

I'm wondering if anybody's got this work with windows server 2008 R2 RC (build 7100). I'm able to join my samba domain after making all of the posted registry modifications, but I too am getting the "The trust relationship between this workstation and the primary domain failed" message when I try to login. I upgraded to Samba 3.3.6 (from 3.0.33) and joined the machine

Hello list, I have been using "smb ports = 445" to get rid of the dreaded "Transport endpoint is not connected" error, and it seemed to be working fine for Windows XP, on SerNet's samba3-3.3.9-40.el5 build. We recently introduced Windows 7 to our network - and the "Transport endpoint" errors are back: Nov 25 17:21:41 experimental smbd[13018]: [2009/11/25

This is a really weird one. To the ( XP Pro ) client, I can join the domain, but can never log in. I've looked all over for a troubleshooting guide, but none have found the problem. Help!!! System: samba 3.3.4 on 64 bit debian lenny patched to current. Gigabit lan environment. When Joining the domain ( over an openvpn connection ), the client log shows: [2009/05/07 09:52:08, 0]

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

Hi, I got no replies to my last post "win 7 client can't map drive: getpeername failed" Anyway I've dug a little deeper on the server side by setting log level 10 and found the error: "Transport endpoint is not connected" Basically I compared the logs (several thousand lines!) from two windows 7 clients, one of which always works (the good client) and one which

Good Afternoon, I have Samba 2.2.1a running on a SPARC Solaris 2.7. All of a sudden I'm having a problem with one PC mapping Samba drives. In the log file for this PC I get the following error messages: [2001/12/11 12:47:22, 0] lib/util_sock.c:write_socket(565) write_socket: Error writing 4 bytes to socket 8: ERRNO = Broken pipe [2001/12/11 12:47:22, 0] lib/util_sock.c:send_smb(729)

Hi all, I'm using Samba 3.0.7, OpenLDAP 2.2.17, smbldap-tools-0.8.5 It has been configured pdc with tls. tls work fine: ldapsearch -x -ZZ -h ldap.domain.com.br -D cn=suport,dc=domain,dc=com,dc=br -L -W ... ... # numResponses: 20 # numEntries: 19 my user has been found and accept password in the ldap root@terra:~# id fernando.ribeiro uid=1000(fernando.ribeiro)