On 12/19/2011 02:05 PM, Jeremy Allison wrote:
On Fri, Dec 16, 2011 at 02:00:17PM -0500, Allen Chen wrote:
I have the same message in samba log file, even though I set up "log
level = 0".
My Samba 3.4.5 PDC is listening on both ports 139 and 445 under
CentOS 5.6 32bits.
Here is the message:
[20
eremy Allison; samba@lists.samba.org
Subject: Re: [Samba] "getpeername failed" error when signed communications
policy enabled
On Thu, Dec 15, 2011 at 09:10:11AM +, Hilton, David wrote:
> No, the only error that we see is the "getpeername failed" error in the
Samba log fo
On Wed, Jan 04, 2012 at 10:02:45AM +, Hilton, David wrote:
> We've found a solution for this and it turns out to be a setting at the
> Windows end:
>
> If you add the value AllowGuestAuthWhenSigningRequired = 1 to the registry
> key
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanman
.samba.org
Subject: Re: [Samba] "getpeername failed" error when signed communications
policy enabled
On Wed, Dec 07, 2011 at 11:01:50AM +, Hilton, David wrote:
> Hi,
>
> I'm looking for help with an issue that we are seeing with the following
> configuration:
>
> W
On Fri, Dec 16, 2011 at 02:00:17PM -0500, Allen Chen wrote:
> I have the same message in samba log file, even though I set up "log
> level = 0".
> My Samba 3.4.5 PDC is listening on both ports 139 and 445 under
> CentOS 5.6 32bits.
> Here is the message:
> [2011/10/26 16:02:05, 0] lib/util_sock.
Jeremy Allison wrote:
On Wed, Dec 07, 2011 at 11:01:50AM +, Hilton, David wrote:
Hi,
I'm looking for help with an issue that we are seeing with the following
configuration:
We are using Samba (3.5.12-72.fc15) to share out CUPS printers from a Fedora
15 machine. However, a requirement of
On Thu, Dec 15, 2011 at 09:10:11AM +, Hilton, David wrote:
> No, the only error that we see is the "getpeername failed" error in the Samba
> log for the client machine that is trying to print the job.
Then I doubt it's a signing issue (which makes it strange).
What does a debug level 10 say
On Wed, Dec 07, 2011 at 11:01:50AM +, Hilton, David wrote:
> Hi,
>
> I'm looking for help with an issue that we are seeing with the following
> configuration:
>
> We are using Samba (3.5.12-72.fc15) to share out CUPS printers from a Fedora
> 15 machine. However, a requirement of the system is
Hi,
I'm looking for help with an issue that we are seeing with the following
configuration:
We are using Samba (3.5.12-72.fc15) to share out CUPS printers from a Fedora
15 machine. However, a requirement of the system is that these printers are
not directly visible from client systems (Windows 7
Of Andrew Masterson
Sent: Thursday, March 10, 2011 1:56 PM
To: Jack Bush; samba@lists.samba.org
Subject: Re: [Samba] getpeername failed. Error was Transport endpoint is
notconnected (3.0.37)
>
> Hi All,
>
> I have a Solaris 10 server (Sun Fire T5520) that has recently been patched
wit
>
> Hi All,
>
> I have a Solaris 10 server (Sun Fire T5520) that has recently been patched
> with
> Samba 3.0.37 but is not able to share any drives to Windows clients. Instead,
> the /var/samba/log/log.smbd is showing the following errros:
> getpeername failed. Error was Transport endpoint
Hi All,
I have a Solaris 10 server (Sun Fire T5520) that has recently been patched with
Samba 3.0.37 but is not able to share any drives to Windows clients. Instead,
the /var/samba/log/log.smbd is showing the following errros:
getpeername failed. Error was Transport endpoint is not connect
I'm using samba 3.5.6 + PDC and connected to LDAP directory
In log level 1 there is many entries like this :
Feb 18 18:13:42 samba smbd[21646]: getpeername failed. Error was
Transport endpoint is not connected
Feb 18 18:13:42 samba smbd[21646]: write_data: write failure in
writing to client 0.
Hello all,
I have a simple share on samba 3.2.5-4lenny13 defined like this :
[global]
workgroup = MYDOMAIN
realm = MYDOMAIN.ORG
server string = %h server
security = ADS
obey pam restrictions = Yes
load printers = No
idmap uid = 1-2
Hi everyone.
Does anyone can tell me what does mean this message?
getpeername failed. Error was Noeud final de transport n'est pas connecté
[2010/09/13 08:31:00, 0] lib/util_sock.c:get_peer_addr(1224)
my /var/log/smbd.log is full with this such message.
--
Olivier Pavilla
S.C.I.R.C. Orléans (
Dear All,
Suse 10.2 Samba 3.2.8
How to get rid off the annoying: Samba getpeername failed. Error was
Transport endpoint is not connected.
I made iptables I INPUT 1 p tcp dport 445 j DROP and it finished. But
this could not be the solution.
Since the newer versions of samba this port makes
This is the first time I've noticed this with Samba 3.2.8 on Irix:
[2009/02/19 16:40:15, 1] smbd/service.c:make_connection_snum(1194)
eowyn (161.253.154.245) signed connect to service warburg initially as
user warburg (uid=123, gid=20) (pid 13408)
[2009/02/19 17:20:06, 0] lib/util_sock.c:re
After a year of running a stable Samba connection, I can no longer connect to
my Linux server. The error "getpeername failed. Error was Transport endpoint is
not connected" shows in the error log.
What would (could) be the cause of this, and where do I start troubleshooting?
Thanks for any tips
Hi,
About 10 days ago, I started looking at the "getpeername failed. Error was
Transport endpoint is not connected" message appearing on our logs. This
message was being produced very frequently during the day and somewhat
less frequently at night.
Anyone can help me to fix it ??
Here're messa
Hi,
I am discovering several error messages from one of our samba servers.
Logcheck says:
Security Events
=-=-=-=-=-=-=-=
getpeername failed. Error was Transport endpoint is not connected
getpeername failed. Error was Transport endpoint is not connected
getpeername failed. Error was Transpor
Hi,
I am discovering several error messages from one of our samba servers.
Logcheck says:
Security Events
=-=-=-=-=-=-=-=
getpeername failed. Error was Transport endpoint is not connected
getpeername failed. Error was Transport endpoint is not connected
getpeername failed. Error was Transpor
Hi,
I am discovering several error messages from one of our samba servers.
Logcheck says:
Security Events
=-=-=-=-=-=-=-=
getpeername failed. Error was Transport endpoint is not connected
getpeername failed. Error was Transport endpoint is not connected
getpeername failed. Error was Tra
Franck Y wrote:
Hello,
Thanks for your reply !
Not something in particular but i get more when i was doing a backup
It s so weird.
I think it something with acces to files u don t know and it pi**ing me off...
Franck
To my understanding Windows (XP at least) tries to connect to both port
Franck Y wrote:
Fellows,
I need some help regarding this thing!1!
I get tons of messages like this ?
Can anyone help me with resolving this problem ?
Dec 18 13:52:42 constellation smbd[8063]: [2005/12/18 13:52:42, 0]
lib/util_sock.c:send_smb(647)
Dec 18 13:52:42 constellation smbd[8063]: Erro
Fellows,
I need some help regarding this thing!1!
I get tons of messages like this ?
Can anyone help me with resolving this problem ?
Dec 18 13:52:42 constellation smbd[8063]: [2005/12/18 13:52:42, 0]
lib/util_sock.c:send_smb(647)
Dec 18 13:52:42 constellation smbd[8063]: Error writing 4 bytes t
Fellows,
I need some help regarding this thing!1!
I get tons of messages like this ?
Can anyone help me with resolving this problem ?
Dec 18 13:52:42 constellation smbd[8063]: [2005/12/18 13:52:42, 0]
lib/util_sock.c:send_smb(647)
Dec 18 13:52:42 constellation smbd[8063]: Error writing 4 bytes t
Hello NG
I'm trying without success to join a XP workstation in a Samba/openldap
domain
SuSE 9.3)and to connect this samba/ldap as fileserver.
On samba machine I'm getting this errormessage:
my var/log/samba/smbd:
[2005/10/26 16:24:04, 0] lib/util_sock.c:get_peer_addr(1150)
getpeername fail
I have a similar error, I can us XP workstation ad domain members, and they
even use the shares, but two or threes times per day the connection resets,
and I have to kill the smbd and start it again (only restart does not work).
Take look at my LOG. Any idea?
[2005/10/04 11:02:10, 0] lib/util_sock
On Wednesday 24 August 2005 09:57, Bahya NASSR EDDINE wrote:
> --- Bahya NASSR EDDINE <[EMAIL PROTECTED]> a écrit
>
> > Date: Wed, 24 Aug 2005 12:14:37 +0200 (CEST)
> > De: Bahya NASSR EDDINE <[EMAIL PROTECTED]>
> > À: samba@lists.samba.org
> > Objet: [Sam
--- Bahya NASSR EDDINE <[EMAIL PROTECTED]> a écrit
:
> Date: Wed, 24 Aug 2005 12:14:37 +0200 (CEST)
> De: Bahya NASSR EDDINE <[EMAIL PROTECTED]>
> À: samba@lists.samba.org
> Objet: [Samba] getpeername failed
>
> Hello there,
>
> I am using a samba 3 PDC wi
Hello there,
I am using a samba 3 PDC with OpenLDAP directory. I
can't log on to my samba domain any more from my
windows clients!
Once the samba domain joined, I reboot the client
machine and I try to log on to the domain. The later
operation falls with an error message telling that it
a connec
Hello,
Using Samba 3.014 on SLES9 on a proliant Xeon server.
All clients (XP) fixed IP addresses,
Ip <> hostname in hosts table.
During the boot of a XP client I receive these messages in the log file's
Can anybody explain why or what is causing this.
Most of the XP clients reporting none of thes
Hello,
Using Samba 3.014 on SLES9 on a proliant Xeon server.
All clients (XP) fixed IP addresses,
Ip <> hostname in hosts table.
During the boot of a XP client I receive these messages in the log file's
Can anybody explain why or what is causing this.
Most of the XP clients reporting none of thes
Are you sure? In wich scenario? I have a pdc on samba and when i check
the "netstat" i have a lot of open conections with the 445 port on the
smbd binary.
Ed Kasky wrote:
I went around and around with this issue for months replacing cables,
switches and nics on a couple of machines all to no av
I went around and around with this issue for months replacing cables,
switches and nics on a couple of machines all to no avail. I played
around with something I found in the archives:
http://lists.samba.org/archive/samba/2004-April/084048.html
Using iptables to drop port 445, I eliminated the
I've also seen a post somewhere (forgive, don't remember where "somewhere is)
suggesting that "smb ports = 445" would corect this issue. So, which is it,
139 or 445?
Dimitri
On Monday 18 April 2005 05:55 am, Fabian Arrotin wrote:
> I've already seen this in my logs...
> A little search on Goog
man, 18.04.2005 kl. 08.58 skrev Guido Lorenzutti:
> I get this error message "getpeername failed. Error was Transport
> endpoint is not connected" in my logs very often. Any ideas how to fix it?
Correct your network problems; make sure that all computers in your
network are reachable and booted.
I've already seen this in my logs...
A little search on Google shows me that Windows XP client try try to
connect to port 139 and 445 in parallel and drop the connection to port
139 if the connect to 445 is successful.
In fact, no one was complaining about real network connection loss ...
More inf
I get this error message "getpeername failed. Error was Transport
endpoint is not connected" in my logs very often. Any ideas how to fix it?
Tnxs in advance
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Hi, I'm seeing this a log in my logs:
Apr 13 09:09:23 mail2 smbd[11431]: [2005/04/13 09:09:23, 0]
lib/util_sock.c:get_peer_addr(1000)
Apr 13 09:09:23 mail2 smbd[11431]: getpeername failed. Error was Transport
endpoint is not connected
Apr 13 09:09:23 mail2 smbd[11431]: Connection denied from 0
Hi all,
I'm using Samba 3.0.7, OpenLDAP 2.2.17, smbldap-tools-0.8.5
It has been configured pdc with tls.
tls work fine:
ldapsearch -x -ZZ -h ldap.domain.com.br -D
cn=suport,dc=domain,dc=com,dc=br -L -W
...
...
It trying port 430 and 455?
Why??
Palavras de Fernando Ribeiro [Tue, Oct 05, 2004 at 01:45:26PM -0300]:
> Hi all,
>
> I'm using slackware 10, running samba-3.0.7, OpenLDAP-2.2.17 with ssl,
> tls and sasl2.
>
>
> While i trying include a workstation windows xp in the samba dom
Hi all,
I'm using slackware 10, running samba-3.0.7, OpenLDAP-2.2.17 with ssl,
tls and sasl2.
While i trying include a workstation windows xp in the samba domain it
return this:
[2004/10/05 12:51:25, 0] lib/util_sock.c:send_smb(647)
Recently I started getting these error messages in log.smbd...
[2003/08/27 16:45:27, 0] lib/util_sock.c:get_socket_addr(919)
getpeername failed. Error was Transport endpoint is not connected
Any ideas on what it is trying to tell me?
Spencer
--
To unsubscribe from this list go to the followi
Hi,
I'm using Samba 3.0beta2, and I am getting the following errors in
log.smbd every time a machine connects:
[2003/07/10 15:09:22, 0] lib/util_sock.c:get_socket_addr(895)
getpeername failed. Error was Transport endpoint is not connected
At the same time I get a log.0.0.0.0 file, as well as a
Anyone know what's up with this?
Jun 20 09:48:37 alsi smbd[5235]: [2003/06/20 09:48:26, 0]
lib/util_sock.c:get_socket_addr(895)
Jun 20 09:48:37 alsi smbd[5235]: getpeername failed. Error was Transport
endpoint is not connected
Jun 20 09:48:37 alsi smbd[5235]: [2003/06/20 09:48:26, 0]
lib/util_so
46 matches
Mail list logo
