similar to: samba in NATed network

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

Hi everyone, I hope someone can help me with the following problem: I administer 2 separate networks, each with one samba server (samba versions are 3.0.14 and 3.0.22) and serveral windows xp professional clients. There were never any problems, but recently one of the employees bought a laptop with windows xp home that he wants to use in both networks. He does not log on to the domain like

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

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

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

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

hi all, i have a Samba version 3.2.5 server running in a debian 5.0.8 (a little old, i know...). the network setup is: -one local office using samba -one remote office (we call it cberg) using samba remotely over a vpn (linksys-cisco) -another remote office (we call it colon) using samba remotely over a vpn (linksys-cisco) the local office and colon office are working fine the remote office

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

Bonjour, I'm running samba 2.0.4 on a Sparc Solaris 2.5.1 and I have some error logs when I'm trying to connect to a sharing directory from *some* NT4 WS (SP4 or SP5): pchp2 (194.xxx.xxx.xxx) connect to service centreAS as user truc (uid=1326, gid=1320) (pid 22939) [1999/08/26 15:52:57, 0] lib/util_sock.c:write_data(415) write_data: write failure. Error = Broken pipe [1999/08/26

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

Hi, i have a lot of entries in my logs which i can't solve, but everything works as expected. my setup: samba pdc - bacula samba bdc - mule Ubuntu 10.04-LTS Server samba 3.4.7 log file entries: Aug 1 08:25:40 bacula smbd[23854]: canonicalize_connect_path failed for service alex, path /\\mule\alex Aug 1 08:25:41 bacula smbd[23854]: [2012/08/01 08:25:41, 0]

I've been fighting with a samba install on top of a amd64 Ubuntu 10.4 system for a couple months now. I have a small flotilla of Windows systems running anything from Win 2000 up through Windows Server 2008. All save for the 2008 systems are setup with nightly NTBackup jobs with my samba server as the destination. The 2008 systems are running MS SQL and use the samba server as the

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

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.

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]

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

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,

Hi, I just upgraded my server to support Windows 7 and so installed Samba 3.5.4 from 3.2.5. OS is Debian Lenny. Now my Windows XP clients cannot join the Domain. When joining the Domain, I get a wrong password error on Windows. In my samba logs it shows the following: [2010/08/03 12:10:19.681501, 0] lib/util_sock.c:1432(get_peer_addr_internal) getpeername failed. Error was Transport endpoint