I have two identical AIX v4.2 machines. One of them was vendor installed, and I installed the OS on the other one. I am successfully running Samba-1.9.18p4 on the vendor installed OS, but I cannot seem to get any Win95 clients to browse on my other machine (Explorer hangs on the Win95 client). I have performed all of the tests in DIAGNOSIS.txt. All of the tests work except for number 7. I can connect to shares (unix to unix) by supplying the correct password, but the smbclient hangs when I try to get a file or dir listing. I cannot connect to shares from Win to Unix at all (no password prompt, nothing!). I reduced the smb.conf file to the simplest share/security that I could and 'testparm' didn't report any errors. Finally, I added a debug level of 5, but It didn't show me any problems (that I could immediately see). Do you have any good starting points? Mark Southward Venchurs Packaging Adrian, MI, USA
Ok, here is the update. I copied the binaries from the machine that works properly to the 2nd machine. This appears to have solved the problem. Something is wrong with our AIX C compiler or I have incorrect compile options set. I followed the correct options from the Makefile but that didn't work. Has anyone had any trouble compiling the source for AIX 4.2 ? --Mark ----------> From: MIS Dept <mis.venchurs@tc3net.com> > To: samba@samba.anu.edu.au > Subject: connection problem > Date: Friday, July 17, 1998 5:05 PM > > I have two identical AIX v4.2 machines. One of them was vendorinstalled,> and I installed the OS on the other one. > > I am successfully running Samba-1.9.18p4 on the vendor installed OS, butI> cannot seem to get any Win95 clients to browse on my other machine > (Explorer hangs on the Win95 client). > > I have performed all of the tests in DIAGNOSIS.txt. All of the testswork> except for number 7. I can connect to shares (unix to unix) by supplying > the correct password, but the smbclient hangs when I try to get a file or > dir listing. I cannot connect to shares from Win to Unix at all (no > password prompt, nothing!). > > I reduced the smb.conf file to the simplest share/security that I couldand> 'testparm' didn't report any errors. > > Finally, I added a debug level of 5, but It didn't show me any problems > (that I could immediately see). > > Do you have any good starting points? > > Mark Southward > Venchurs Packaging > Adrian, MI, USA
I am having a problem connecting from a Windows 98 machine to my Samba UNIX
server. I think it has to do with the way Win 98 connects to the network.
Foe example in windows networking, if I am at a computer that logs on to a
Windows network that uses the name bill, and I try to connect to the below
share as Mike it fails. How can I connect to the share below anywhere I
happen to be?????
Thanks
[tmp]
comment = Mikes Test
valid users = mike
path = /data/mike
Dear Samba support, I have been using samba (in Solaris 2.6) for 1.5 years and always update with latest version. I had problem 3 weeks ago, when some users tried to connect to the disks in samba server (solaris 2.6) I still used samba ver. 2.0.6 in that time. The users used Windows 95 when they had problems, while there was no problem on NT users. The messages appeared in Windows 95 were: "cannot connect to vicosrv1. Network is busy. " And the log message in samba log were: [2000/06/20 07:02:53, 0] lib/util_sock.c:write_socket_data(537) write_socket_data: write failure. Error = Broken pipe [2000/06/20 07:02:53, 0] lib/util_sock.c:write_socket(563) write_socket: Error writing 4 bytes to socket 8: ERRNO = Broken pipe [2000/06/20 07:02:53, 0] lib/util_sock.c:send_smb(751) Error writing 4 bytes to client. -1. Exiting [2000/06/20 07:02:53, 0] lib/util_sock.c:client_addr(1035) getpeername failed. Error was Transport endpoint is not connected [2000/06/20 07:02:53, 0] lib/util_sock.c:write_socket_data(537) write_socket_data: write failure. Error = Broken pipe [2000/06/20 07:02:53, 0] lib/util_sock.c:write_socket(563) write_socket: Error writing 4 bytes to socket 8: ERRNO = Broken pipe [2000/06/20 07:02:53, 0] lib/util_sock.c:send_smb(751) Error writing 4 bytes to client. -1. Exiting [2000/06/20 09:29:12, 0] lib/util_sock.c:client_addr(1035) getpeername failed. Error was Transport endpoint is not connected [2000/06/20 09:29:12, 0] lib/util_sock.c:write_socket_data(537) write_socket_data: write failure. Error = Broken pipe [2000/06/20 09:29:12, 0] lib/util_sock.c:write_socket(563) write_socket: Error writing 4 bytes to socket 8: ERRNO = Broken pipe [2000/06/20 09:29:12, 0] lib/util_sock.c:send_smb(751) and repeated.... After two-three days with this problems (without any solutions), now the connection is back. Windows 95 users can connect without any problems. Why it can happen....and how to solve this problem when it comes again... PS: I have samba 2.0.7 now and I will install soon. regards, Puntadi VICO Indonesia puntadi@vico.co.id
I have been running Samba for at least 6 months now without a problem. Recently I have been getting this error message; [2001/03/16 13:18:29, 0] lib/util_sock.c:read_socket_data(477) read_socket_data: recv failure for 4. Error = Connection reset by peer This error message is appearing more and more everyday and my users are getting more and more annoyed. How can I fix this? Martin Stacey Information Support Manager Safcol Australia Pty Ltd -------------- next part -------------- HTML attachment scrubbed and removed
Hi Martin, the message specifically means that samba went to retrieve data from a socket (a connection to a particular workstation) and found that at the tcpip layer, the client had sent a packet with the tpc reset flag set - ie, the CLIENT deliberately terminated the tcpip connection. Question is WHY - if you have NT clients that are experiencing this, you can check their event logs for errors; in some cases NT will do a reset to a server connection if it receives a badly formatted smb packet on that connection, or if it timed out waiting an smbreply on that connection - this might help you understand what is going on. If it's just win9x clients, you're out of luck, other than to see if you can isolate the problem to one of your clients that has it frequently, and turn on debugging leve 10 for that one client, and maybe run netmon in the background on that same client, and try to CATCH the reset, to see what the client/server were doing at the proximate time of the reset. make sure you have debug timestamp and debug pid turned on as well, so you can check the timing of smb request/replys. Since you mention that it's been running fine for 6 months, and has only recently developed this symptom, you need to also ask yourself what has changed recently? Number of clients increased? new application clients are using accessing samba files, that they werent using before? Increased load on the Unix box that samba is running on? Increased overall network traffic or increase in errors or retries on the network from the Unix nic? Just some ideas, Good luck, Don -----Original Message----- From: Martin Stacey [mailto:martin@safcol.com.au] Sent: Thursday, March 15, 2001 10:32 PM To: Samba Subject: Connection problem I have been running Samba for at least 6 months now without a problem. Recently I have been getting this error message; [2001/03/16 13:18:29, 0] lib/util_sock.c:read_socket_data(477) read_socket_data: recv failure for 4. Error = Connection reset by peer This error message is appearing more and more everyday and my users are getting more and more annoyed. How can I fix this? Martin Stacey Information Support Manager Safcol Australia Pty Ltd
I am running HPUX 11.0 with SAMBA connected to an NT network. The system is configured to validate against the network and this appears to be working great, but we are having a problem with the number of connections. We are trying to migrate 200 users over to the system, but during certain times we get the following error message when trying to connect to the mapped network drive: Microsoft Windows Network: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. This connection has not been restored. Can anyone tell me why we are getting this message and if there is a parameter that I can change in order to make this error messages stop appearing? When the messages appears no one can map to our UNIX server and we must restart the SAMBA processes in order to get connected. Please help!! _________________________________ Brad M. Garrott Computer Programmer/Analyst Global Information Services The Timken Corporation _________________________________ E-Mail: garrottb@timken.com Ph/Fax: (330) 471-4750/4034
On Mon, Nov 05, 2001 at 02:55:07PM -0500, Garrott, Brad M. wrote:> I am running HPUX 11.0 with SAMBA connected to an NT network. The system is > configured to validate against the network and this appears to be working > great, but we are having a problem with the number of connections. We are > trying to migrate 200 users over to the system, but during certain times we > get the following error message when trying to connect to the mapped network > drive: > > Microsoft Windows Network: No more connections can be made to this remote > computer at this time because there are already as many connections as the > computer can accept. This connection has not been restored. > > Can anyone tell me why we are getting this message and if there is a > parameter that I can change in order to make this error messages stop > appearing? When the messages appears no one can map to our UNIX server and > we must restart the SAMBA processes in order to get connected.What version of Samba are you running ? What messages are you getting in the Samba logs when you get these messages ? You need to give more details in order for us to help you. Thanks, Jeremy.
Hello Brad, I have seen this on many of the 2.2.x versions out there when run on HP-UX. There were some .tdb corruption issues (partly because of mmap implementation on HP-UX, partly because of some issues with the tdb code itself). AFAIK, these issues have been addressed with the latest release version of Samba, which is 2.2.2. Please see if you can reproduce with this version. Good Luck, Don -----Original Message----- From: Garrott, Brad M. [mailto:garrottb@timken.com] Sent: Monday, November 05, 2001 2:55 PM To: 'samba@lists.samba.org' Subject: connection problem I am running HPUX 11.0 with SAMBA connected to an NT network. The system is configured to validate against the network and this appears to be working great, but we are having a problem with the number of connections. We are trying to migrate 200 users over to the system, but during certain times we get the following error message when trying to connect to the mapped network drive: Microsoft Windows Network: No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. This connection has not been restored. Can anyone tell me why we are getting this message and if there is a parameter that I can change in order to make this error messages stop appearing? When the messages appears no one can map to our UNIX server and we must restart the SAMBA processes in order to get connected. Please help!! _________________________________ Brad M. Garrott Computer Programmer/Analyst Global Information Services The Timken Corporation _________________________________ E-Mail: garrottb@timken.com Ph/Fax: (330) 471-4750/4034 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
hi list, I?ve a strange problem: I?m using samba 2.2.1 kernel 2.4.10 and win2000 clients. Login and profiles are working but when I want to go to a directory on the server I must try it about three or more times to get access to the directories. Then I can do everything with the files in this directory. Should I use the keepalive parameter (=120???) or is my hardware too slow (P III 350, 128 MB, 10 MBit-LAN). Can the WIN 2000 SP2 help me? Peter
Samba 2.2.2 is running on my hp 11.11 server. have about 20 connections.
nobody else can connect!
trying to debug using various tools:
houux6: >smbclient -L localhost -I 10.41.248.90 -n houux6 -W KM -d10
added interface ip=10.41.248.90 bcast=10.41.251.255 nmask=255.255.252.0
Client started (version 2.2.2).
Connecting to 10.41.248.90 at port 139
socket option SO_KEEPALIVE = 0
socket option SO_REUSEADDR = 0
socket option SO_BROADCAST = 0
socket option TCP_NODELAY = 1
socket option IPTOS_LOWDELAY = 0
socket option IPTOS_THROUGHPUT = 0
socket option SO_REUSEPORT = 0
socket option SO_SNDBUF = 32768
socket option SO_RCVBUF = 32768
socket option SO_SNDLOWAT = 8192
socket option SO_RCVLOWAT = 8192
socket option SO_SNDTIMEO = 0
socket option SO_RCVTIMEO = 0
write_socket(3,76)
write_socket(3,76) wrote 76
Sent session request
read_socket_with_timeout: timeout read. EOF from client.
receive_smb: length < 0!
client_receive_smb failed
size=0
smb_com=0x0
smb_rcls=0
smb_reh=0
smb_err=0
smb_flg=0
smb_flg2=0
smb_tid=0
smb_pid=0
smb_uid=0
smb_mid=0
smt_wct=0
smb_bcc=0
session request to LOCALHOST failed (code 0)
Connecting to 10.41.248.90 at port 139
socket option SO_KEEPALIVE = 0
socket option SO_REUSEADDR = 0
socket option SO_BROADCAST = 0
socket option TCP_NODELAY = 1
socket option IPTOS_LOWDELAY = 0
socket option IPTOS_THROUGHPUT = 0
socket option SO_REUSEPORT = 0
socket option SO_SNDBUF = 32768
socket option SO_RCVBUF = 32768
socket option SO_SNDLOWAT = 8192
socket option SO_RCVLOWAT = 8192
socket option SO_SNDTIMEO = 0
socket option SO_RCVTIMEO = 0
write_socket(3,76)
write_socket(3,76) wrote 76
Sent session request
read_socket_with_timeout: timeout read. EOF from client.
receive_smb: length < 0!
client_receive_smb failed
size=0
smb_com=0x0
smb_rcls=0
smb_reh=0
smb_err=0
smb_flg=0
smb_flg2=0
smb_tid=0
smb_pid=0
smb_uid=0
smb_mid=0
smt_wct=0
smb_bcc=0
session request to *SMBSERVER failed (code 0)
houux6: >nmblookup -B houux6 __SAMBA__
querying __SAMBA__ on 10.41.248.90
10.41.248.90 __SAMBA__<00>
houux6: >echo hello | telnet localhost 139
Trying...
Connected to localhost.kindermorgan.com.
Escape character is '^]'.
Connection closed by foreign host.
houux6: >nmblookup -S houux6
querying houux6 on 10.41.251.255
10.41.248.90 houux6<00>
Looking up status of 10.41.248.90
HOUUX6 <00> - M <ACTIVE>
HOUUX6 <03> - M <ACTIVE>
HOUUX6 <20> - M <ACTIVE>
KM <00> - <GROUP> M <ACTIVE>
KM <1e> - <GROUP> M <ACTIVE>
Hello all, i'm having a hard time getting samba running. I am running red hat 8.0, and samba 2.25. i am part of a domain on my campus and have my box joined to the domain. i can even see it in the workgroup, but whenever i try and connect to it from a windows machine i get this error "No service is operating at the destination network endpoint on the remote system." Here's my smb.conf [global] netbios name = jasonsdt guest ok = yes log file = /var/log/samba/%m.log load printers = yes smb passwd file = /etc/samba/smbpasswd passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully* obey pam restrictions = yes socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192 wins server = Enterprise encrypt passwords = yes passwd program = /usr/bin/passwd %u dns proxy = no server string = Samba Server printing = lprng password server = Enterprise unix password sync = Yes workgroup = Trinitynet printcap name = /etc/printcap security = domain pam password change = yes [downloads] writeable = yes public = yes path = /home/jason/downloads [music] writeable = yes public = yes path = /home/jason/music any help you could give me would be greatly appreciated. Thanks, jason _________________________________________________________________ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus
I have a Sun Solaris 2.6 system, with Samba 2.0.5. One of the PC's which has the outlook.pst file stored on a samba share keeps getting an error saying the outlook.pst file could not be saved and outlook crashes. This PC also takes a long tome to open files on the samba share with Excel, and sometimes fails to open them, although they will open when re-tried. The PC is called 19-2103157 and the user is jweller. I can see various error messages in the attached log file, and have looked on the web site, but I am none the wiser about how to resolve the problem. Any suggestions will be gratefully received. Helen Mason I.T.Services Manager M & W Mack Wholesale Division Tel: 01905 798316 Fax: 01905 798763 This email contains proprietary information some of which may be legally privileged. It is for the intended recipient only. If an error has misdirected this email, please notify the sender by reply email. If you are not the intended recipient, you must not use, disclose, distribute, copy, print or rely on this email. ________________________________________________________________________ This e-mail has been scanned for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ________________________________________________________________________
Hi!!! Samba Greate Members I am new to Samba and I am trying to network windows 2000 and linux machin as Samba server. I instaled samba version 2.2.5 on redhat.8 I can see the work groupe icon on windows machin . when I click on to see the Linux machin, it comes with a message "Work group is not accessible" I did following # smbclient -L server1 ( Wher serve1 is linux box host name) Response is Can't find include file /etc/samba/smb.conf. addedd int = 192.168.0.2 broadcast = 192.168.0.255 netmask = 255.255.255.0 session request to server1 failed( Not llistening for calling name). Session request to *SAMBASERVER faild (Not listening for calling name ) pinging beteen the linux box and windows machin is ok with ip's and with host names. pinging to local host 127.0.0.1 and with host name is ok. Telenet between windows2000 and linx on port 139 is ok. Could some greate person help me to sccessfull net working. Regards Rao Mylangam