-Original Message-
From: Marc Muehlfeld [mailto:sa...@marc-muehlfeld.de]
Sent: Thursday, June 06, 2013 7:02 PM
To: Ferencik, Samuel: Markets (PRG)
Cc: samba@lists.samba.org
Subject: Re: [Samba] NT_STATUS_BAD_NETWORK_NAME for Windows Server 2008
Hello Samuel,
Am 06.06.2013 18:28, schrieb
On 06/06/13 16:10, samuel.feren...@barclays.com wrote:
[SNIP]
Hi Jeremy,
Version 3.0.33-3.39.el5_8
and
Version 3.6.9-151.el6
Package names suggest you are using a RHEL derivative. Do yourself a
favour and on your RHEL5 boxes install the Samba3x packages to get
something remotely recent.
On Wed, Jun 05, 2013 at 05:14:47PM +0100, samuel.feren...@barclays.com wrote:
Hi,
Our smbclient calls have started failing on connections to Windows 2008 AD
servers. (Previously there were only Windows 2003 Servers, so we had no
issues.)
Domain=[INTRANET] OS=[Windows Server 2008 R2
-Original Message-
From: Jeremy Allison [mailto:j...@samba.org]
Sent: Thursday, June 06, 2013 4:51 PM
To: Ferencik, Samuel: Markets (PRG)
Cc: samba@lists.samba.org
Subject: Re: [Samba] NT_STATUS_BAD_NETWORK_NAME for Windows Server 2008
On Wed, Jun 05, 2013 at 05:14:47PM +0100
On Thu, Jun 06, 2013 at 04:10:46PM +0100, samuel.feren...@barclays.com wrote:
-Original Message-
From: Jeremy Allison [mailto:j...@samba.org]
Sent: Thursday, June 06, 2013 4:51 PM
To: Ferencik, Samuel: Markets (PRG)
Cc: samba@lists.samba.org
Subject: Re: [Samba
-Original Message-
From: Jeremy Allison [mailto:j...@samba.org]
Sent: Thursday, June 06, 2013 5:35 PM
To: Ferencik, Samuel: Markets (PRG)
Cc: j...@samba.org; samba@lists.samba.org
Subject: Re: [Samba] NT_STATUS_BAD_NETWORK_NAME for Windows Server 2008
On Thu, Jun 06, 2013 at 04:10:46PM
Hello Samuel,
Am 06.06.2013 18:28, schrieb samuel.feren...@barclays.com:
3.6.9 should connect. Open up a bug at bugzilla.samba.org
and attach a wireshare trace and debug level 10 log of
the connection attempt. That should help us track down
what config is incorrect.
Thanks. I've filed
cli_start_connection: failed to connect to BRN_E1BEFA20 (0.0.0.0). Error
NT_STATUS_BAD_NETWORK_NAME
Without more information I'd say it's because the name maps to the IP
address 0.0.0.0 which is invalid. Try using the correct IP address
instead of the name when you connect.
Cheers,
Adam.
--
Finally found the answer after reinstalling and even the fresh reinstall
didn't work. A review of dmesg showed that selinux was running. Thanks to
this link
http://howtoforge.com/installing_a_lamp_system_with_fedora_core_6_p3 I found
out how to turn off selinux and problem solved. Hope nobody
On Mon, 31 Jul 2006 16:56:07 -0300
pfoglia [EMAIL PROTECTED] wrote:
Hello,
I installed samba 3.0.23 on Fedora Cora 4 and I configured it with this
smb.conf file:
[global]
dos charset = UTF-8
workgroup = OAF_ADMIN
server string = OAF Samba PDC Server
Eric you rule
Such a simple change.
Thanks!.
-Original Message-
From: Eric Hines [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 30, 2006 6:13 PM
To: Frank Simorjay
Subject: Re: [Samba] NT_STATUS_BAD_NETWORK_NAME
At 03/28/06 23:52, you wrote:
Hello,
I could
11 matches
Mail list logo