similar to: Samba 2.0.3 problem

Hi, I'm having a problem accessing my samba server from Windows. The problem occurs every time I try to browse to it on either XP or 2003 Server. The error message I get is: "\\Zeus is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The account is not authorized to log in

The smbd log shows: [1999/06/24 06:40:24, 0] lib/util_sock.c:client_addr(851) getpeername failed. Error was Transport endpoint is not connected [1999/06/24 06:40:24, 0] lib/util_sock.c:write_data(407) write_data: write failure. Error = Broken pipe [1999/06/24 06:40:24, 0] lib/util_sock.c:write_socket(191) write_socket: Error writing 4 bytes to socket 7: ERRNO = Broken pipe [1999/06/24

I get the following errors in log.smb: [1999/02/24 17:02:44, 1] lib/util_sock.c:client_name(810) Gethostbyaddr failed for <CLIENTs IP> [1999/02/24 17:02:44, 0] lib/util_sock.c:write_data(407) write_data: write failure. Error = Broken pipe [1999/02/24 17:02:44, 0] lib/util_sock.c:write_socket(191) write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe [1999/02/24

I'm running Samba 2.0.4b on a E450 running Solaris 7 which acts as a diskspace server for students, normally everything runs quite smoothly with numbers of connections in the region of about 800/900. Then every now and again students will start seeing their connections being lost and others will not get a connection when they log in, looking at the system shows no obvious problems, except

Hi, our window file server running 3.0.25b-33 (X64) (Sernet rpm) on SLES 9 SP3 has been stoped working. The log file shows nothing new. No error ... Only the clients can not connect to the server. After a restart of smbd it seems to work for a while. Any idea ? Any help is welcome !! ---------The last logline before was 10:39; at10:42 no connection was possible----- Jan 7 10:42:30 modena

Hi, Our samba server is running Red Hat Enterprise Linux ES release 4 (Nahant Update 4) with samba version: samba-3.0.33-0.17.el4. We like to authenticate all the users with our Primary Domain Controller wnidows 2008. Some users keep getting asked to enter username and password. Even with the correct password, still can't access the drive. The strange thing is that some users are

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:

I have been using Samba w/out any problems what so ever for the longest time, but today, I cannot connect to the linux box (shows up in network neighborhood as 'LINUXSERVER'), but when I try to connect from a win2K machine (which normally connects w/NO problems). Here is the output from /var/log/messages (appears the problem is in smbd) May 23 11:34:14 fileserver nmbd[1423]: [2002/05/23

Hi, I'm running samba 2.2.7 on redhat advanced server with approximately 40 win2k clients and having a serious problem with the clients. Intermittently the clients will lose their connection to the server for approximately 30 seconds. It's like the socket connection is being reset or something. Here's a sample output from a client log file: [2003/04/12 15:13:08, 0]

It seems that my smbd process got fuxed somehow. It appears to have take up all the file handles, and there were over 130 smbd processes running on the system. I'm not entirely sure what happened. My first thought is that something bad happened between the server and the Windows client that's running Kaza (with a couple hundred mid-download files) and it just spiraled out of control,

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)

Hello, We use samba to backup some (rather large) sql databases. Lately we ocasionally are getting fail reports, as in the file could not be written, and windows generating an error 64: "The specified network name is no longer available" While going trough the logs, i can see the following error (sorry for the long output): ----- [2008/05/19 01:14:46, 0]

I'm doing some testing with Win7 RC1 and I'm having an identical problem with two CentOS servers (5.2 and 5.3) both running Samba 3.0.33 where I cannot authenticate. Both servers are authenticating with Winbind to an AD DC. I have a third CentOS 5.2 server with Samba 3.0.33 shares that does not use Winbind which has no problems. This pops up in smbd.log: (.200 is wireless and .184 is my

This is probably a hot topic, and if this has been beaten to the ground, forgive me. I'm not a regular part of the Samba community. Although I have been using Samba for years, I now have to use it in a corporate environment utilizing some of it's more modern features. Let me just say, that it's been several hours of testing/troubleshooting to get where I am now. (And I don't

(Server :Mandrake 7, Samba 2.0.6) (Client : PC Win95 and Win 98) Samba's work fine since one year but yesterday We had a big problem in my college Lots of PC's client can't connect (invalid password). In the samba's log we read : > [2000/05/19 12:15:21, 1] smbd/service.c:close_cnum(568) > renoir (192.168.84.189) closed connection to service valancee > [2000/05/19

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

A few times in the last couple months we have had our production Samba 3.0.14a-1server crash. We did not have detailed logging turned on at the time so the attached output of our log is the best process tracking I can give at the time of the crash. What will happen is our shares will no longer be accessible, and all the smbd processes will be hung. We can ssh to the server and do a restart

Over the last few weeks I've had problems using Samba on a FreeBSD. Windows XP clients (that's all I have) would experience intermittent long delays (lockups, freezing) when accessing the samba shares using Windows Explorer or any other applications. This occurred both directly when browsing the network neighborhood, and when accessing the share through a letter drive mapping.

Greetings, I have a File Server, Running Samba on RedHat 7.0 Everything Works fines, It have 64 megs of ram, and around 15 peoples using it. But sometimes, in the morning when people try to access it's Share it gives the error msgs: NETWORK IS BUSY. All my user get logon using a Windows NT PDC. To enable my user to connect to Samba, I "play" with the computer for a While..