similar to: can not access samba drive on Redhat ES 4

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

Hi !! I have already sent this message to the list, but, as I have not received any replies, I am trying again !! I have Samba 3.0.22 running as PDC on solaris10. Each time a windows client (XP SP2 or W2003) opens an explorer to access a share, I see in the log.smbd : [2006/06/15 01:28:08, 0] lib/util_sock.c:get_peer_addr(1225) getpeername failed. Error was Invalid argument [2006/06/15

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

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]

MY OS is: Red Hat Enterprise Linux ES release 4 (Nahant Update 8) Samba version: samba-3.0.25b-0.4E.6 I'm map a share drive and I get asked for user name and password. Right now I'm just trouble shooting the samba part. "smb" service is running and "winbind" server is running too. The /var/log/samba/xxxx log file has the following in it:

When i try to swap files between disks on my server using samba i get errors: then windows reports "The specified network name is no longer available". Sometimes the copies are fine other times files just wont copy. Hardware checks out fine. Ive even replaced the network cable between server and switch thinking that might be causing the problem. Ive included a ethereal cap of the

Hello mailing-list, this is my first post and i hope that you enjoy my very bad but sometimes funny english. My Problem is the following: First of all, my server-config: Samba Version 3.0.20b-3.4-SUSE on a SUSE Linux Enterprise Server 9 with Kernel 2.6.5-7.252-smp Now the problem is, that samba generally works fine, but it doesn't work to work with a special application directly on a

I'm having problems connecting from my laptop, and the logs show lib/util_sock.c:send_smb(769) Error writing 116 bytes to client. -1. (Broken pipe) : 1 Time(s) lib/util_sock.c:write_data(562) write_data: write failure in writing to client 192.168.0.91. Error Broken pipe : 1 Time(s) libsmb/smb_signing.c:srv_check_incoming_message(737) srv_check_incoming_message: BAD SIG: seq 2 wanted

I'm trying to use zfs acls in solaris 10. I've looked at past posts regarding this and some online help, but am stuck. I'm currently using samba 3.3.9; I've had the same problem with 3.3.7. samba is compiled and running as an Active Directory member server (compiled with ldap and kerberos). The zfs disk is local. I'm not using winbind. I compiled with zfsacl module.

Hello, I'm running samba-3.0.33 (samba-3.0.33-3.15.el5_4) On Centos 5.4 and some files have issues being copied from the Samba server to the Vista (Service Pack 1) clients local disk via Windows Explorer, copying too the Samba server also has no issues and copying via the CMD prompt has no problem, I'm getting the following errors 1. Invalid MS-DOS Function

Last week we installed Samba 3.0.20b on one of our servers, worked fine and does it's job well. But today the load was rising due two smbd processes taking up all cputime. While looking for hints on what was going on the logfiles show two types of errors (I don't know at this time if it has anything to do with the load spike): lib/util_sock.c:write_data(554) write_data: write failure in

I can't access the share through a station with Windows XP, in the messages log show this error: Jul 21 15:34:55 files smbd[5097]: [2009/07/21 15:34:55, 0] lib/util_sock.c:write_data(562) Jul 21 15:34:55 files smbd[5097]: write_data: write failure in writing to client 192.168.1.74. Error Broken pipe Jul 21 15:34:55 files smbd[5097]: [2009/07/21 15:34:55, 0] lib/util_sock.c:send_smb(761) Jul

Hello, I 've just upgrade my samba server from 2.2.12 version to 3.0.24 (to accept windows vista machines) The machines already recorded on domain are connected without difficulty, on the other hand I have problem to add a machine to the field. It is necessary that I put twice. Here the example of file of log of a machine added to the field obtained after the first attempt cat

A few computers -- two or three -- are very spotty about letting people log on. It seems -- and this could be off-base -- that they'll let anyone log on once, but will require a reboot before you can log on again. Sometimes, logging on works fine, though. There really appears to be little rhyme or reason to what happens. In the Samba logs, I'm getting: [2006/10/20 08:08:14, 0]

Suddenly in the past week we have been having users who share excel files via our Samba complain that the file has become corrupt, and also some database files (Orcad .tdb database files). Fortunately there has in each instance been a good copy in the .recycler... so far. I came across some docs and threads in the net about oplocks. I did find an error in the samba log: [2008/04/14 10:19:05,

We have about 300 users distributed on different vlans using private ip network spaces, and sharing one single public IP when going out to the Internet. Our samba (3.0.24) server has a pulbic IP and is running as a primary domain controller. All clients receive Sambas's public IP as their WINS server. I am able to join the domain but samba stops responding sporadically. Looking at the

Heloo My server hangs up :((machine not only samba) I've upgrated my system. Now it is Gentoo 2005.1 - K 2.6.14 - Samba 3.0.20b Everything works exelent and much more faster now but sometimes it hangs up. The last hang up was when I have loged one user on w98 :( to domain. Only strange thing that I've found in logs are : : [2006/01/05 07:59:13, 0]

Debian Latest stable. Linux newton 2.6.18-4-686 Samba 3.0.24 PDC 3Com 3812 Gigabit switch (connection between WinXP client & server) Others connect through 3Com 3225 100 Mbit -> 3Com 3812 -> Server Windows XP SP2 fully updated. F-Secure client security (look down for firewall settings) In advance, thanks for reading this. Any suggestions are welcome! I'm having a hard time here.

Hi List, One particular user is kicked quite often (espescially during the usage of Outlook). When she tries to login she isn't very succesfull. The serverlog show this: Jul 13 10:41:14 server smbd[12277]: [2006/07/13 10:41:14, 0] lib/util_sock.c:write_data(554) Jul 13 10:41:14 server smbd[12277]: write_data: write failure in writing to client 192.168.1.101. Error Connection reset by

ZFS introduces a new and incompatible ACL interface into Solaris and this seems to be not yet fully completed in addition to the fact that is causes a lot of problems for software that needs to be compatible with Solaris-2.5 like star. Proof for incompatibility: create a file on UFS and set an ACL for this file. Use Sun tar cpf out file to archive this file. Unpack this archive file on ZFS