similar to: High count of smb processes

Any and all attempts to connect to our samba server, packaged in the redhat RPM found on samba.org, have failed. The allow statement is set to localhost, x.y.z. where x.y.z is our class C(ended with a period, as per the online help in SWAT.) Local connections via smbclient work beautifully, but connections from any other machine fails. I've followed the troubleshooting procedure to the

Hello samba@lists.samba.org ----- Original message ----- When i am first run samba from script ("-D" param) log looks like this: [2001/11/12 13:46:42, 3] lib/util_sock.c:open_socket_in(878) bind succeeded on port 139 [2001/11/12 13:46:42, 2] smbd/server.c:open_sockets(181) waiting for a

All, I've just upgraded from 2.0.4 to 2.0.5a on my Sparc 20 (Solaris 2.5.1). I've kept the same configurations but I can no longer map drives from my Windows machines (NT, Win95). smbd exits on error: [1999/07/26 15:48:16, 2] smbd/server.c:main(716) Changed root to / [1999/07/26 15:48:16, 3] smbd/oplock.c:open_oplock_ipc(85) open_oplock_ipc: opening loopback UDP socket. [1999/07/26

Iam running Samba 2.0.10 on a FreeBSD 4.2 platform within a Windows 98/2k peer to peer network. Most of the time this system appears to be working very well with the file system nicely browsable by the client machines. Unfortunately, from time to time the following error appears within the log.smb: [2002/02/14 10:54:28, 3] lib/util.c:interpret_addr(1833) Get_Hostbyname: Unknown host. ed0

Hello, I've a problem with Samba version 2.0.6, where smbd does not start from inetd. nmbd starts from inetd and "smbd -D" works fine as well. And I didn't have that problem with 2.0.4b. The following is an extraction of the smb.log, which shows an "read_socket_data: recv failure for 4. Error = Invalid argument" error. Regarding this problem, what is the difference

Here's my setup: Caldera Open Linux Lite (kernel 2.0.29) Samba 2.0.4a Windows Domain (Two Windows NT 4.0 Servers -- one PDC, one BDC -- and numerous Windows NT 4.0 Workstations) I can see my Linux box in Network Neighborhood on my Windows NT boxes. I can open the Linux box and see the top level shares available. When I try to open a share I see one or two anonymous folders. Anyone

Hi! I've got the fillowing trouble. Im' trying to get the local shares list. I started the smbd using "/etc/init.d/smb restart" script. It seem to work fine. The smb.conf and log.smb are listed below. The smbd says that he "Can't change directory to /root/tmp" when I'm trying to "smbclient -L localhost -U%". The permissions for /tmp/SHARE are

Connecting from WinNT to Samba 1.9.18p10 I have another question: When I have a drive map to my Unix homedir, which should be automatically reconnected during login, I get an error that my password is not correct. If I control the log file of Samba I see: 1998/10/08 17:37:43 changed root to / open_oplock_ipc: opening loopback UDP socket. bind succeeded on port 0 open_oplock ipc: pid = 33822,

Here is some log output that occurs on the production during the process of issuing a net use command from the win95 box to the samba server. The connection reset by peer message appears immediately after the error 54 network is busy message appears on the windows 95 machine. (This is debug level = 10) [1999/05/18 18:21:00, 2] smbd/server.c:main(709) Changed root to / [1999/05/18 18:21:00,

OS: HP-UX B.11.00 U 9000/800 Samba: 2.0.7 smb.conf: -------------------- [global] workgroup = <wg-name> security = SERVER encrypt passwords = Yes password server = <server-list> username map = /opt/samba/lib/domainusers.map debug level = 3 log file = /var/opt/samba/log.%m max log size = 50 dns proxy = No

Hi, I?m running SuSE 6.1 with a 2.2.5 Kernel on a PentiumPro machine. If I use the standard SuSE Kernel, Samba functions without any problems. If I make a new one I get following error: [1999/05/14 11:57:01, 0] smbd/oplock.c:open_oplock_ipc(80) open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested address Wich part off the kernel swichted I off

Hi! When I enter smbpaswd as a normal user iget the following error: Connecting to 127.0.0.1 at port 139 machine 127.0.0.1 rejected the password change: Error was : The specified password is invalid. Failed to change password for mgoeben and in the logs I got: ==> /var/log/samba/log.smb <== [2000/08/16 18:39:57, 3] locking/shmem_sysv.c:sysv_shm_open(707) Initialised IPC area of size

I get the following errors in the smb.log file. If anyone has any ideas about this please let me know. [2001/05/01 09:51:46, 0] lib/util_sock.c:set_socket_options(154) Failed to set socket option TCP_NODELAY (Error Connection reset by peer) [2001/05/01 09:51:46, 0] lib/util_sock.c:open_socket_in(827) Get_Hostbyname: Unknown host [2001/05/01 09:51:46, 0] smbd/oplock.c:open_oplock_ipc(93)

Hi all Samba Gurus, I have problems getting my Win98 box to talk to my Samba Server. I got Samba 2.05a, and ran configure and installed it. Please see the attached smb.conf file for details. Here are my problems: 1. It seems samba does not like hosts deny = ALL hosts allow = <list of hosts> I need to do hosts deny = ALL EXCEPT <list of hosts> hosts allow = <list of

Hello all, I'm in very big big trouble here. In an attempt to enable domain logon for NT workstations as well, I fetched the CVS code on Oct 5, 98. I successful built it with no error. I copied the smb.conf from a workable Sambav1.9.18p8 to the Samba2.0alpha. Then I started the smbd and nmbd of Samba2.0alpha. I rebooted one of the Windows 98 (which used to be working happily with

Hi, I am unable to log into samba anymore since I upgraded to 2.0.3. I've attached my smb.conf below and I've even gone to trying the CVS releases to see if one of them will help. First of all, I get soemthing like {33}: smbclient -L vilnius -U mharrell Added interface ip=207.97.105.146 bcast=207.97.105.255 nmask=255.255.255.128 Password: session setup failed: ERRSRV

> I have a network that sporadically give 'network busy' errors. One morning > the workstations will all connect up fine and stay up throughout the days > work, yet the next day there is not one machine that can log on to the > network. It may run fine for two weeks, then bam, three days of no logins. > Yet the internet works fine. Could I copy my smb.conf file and rpm -e

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

We have a local network with Samba 2.0.3 on SuSE-Linux and some Windows 95 and Windows 98 clients. All works fine. Now we have got a new Windows XP computer, and we found no way to connect to the Samba server from that computer. 1. The network card works. I can ping the server, and it replies. 2. The Samba server as well as the Windows XP computer are shown in the network neighbourhood. 3.

Hello all I need some help understanding what is failing with my Samba installation. I compiled Samba 2.0.6 on a Sparc Ultra-II Solaris 2.6, using GCC version 2.8.1. I have read in some of the docs that there may be some support for shadow passwords but could not find a definition regarding shadow in any of the compile scripts. The SMB and NMB processes are running as deamons. I am unable