Displaying 20 results from an estimated 1000 matches similar to: "confused: when do I have to use \\DOMAN and when \\ip.address"
2009 Mar 09
1
how to add a linux box into a samba domain
hi there,
I am trying to setup a test nework to learn the interaction of the diverse tools
in a smaba/windows network.
now it looks as if I do something wrong when adding a linux box into the domain.
I have a samba domain ROTTI.
It is running on server haydn.redcor.home
from windows I can log into this domain.
now I have a linux box I wanto to join to this domain.
this is its global section:
2009 Mar 04
1
problem when PDC machine name equals domain name
Hi there,
I am trying to learn samba, ldap and co.
now I installed a test net consisting from three computers
haydn: this is the pdc with haydn.redcor.home (ip 10.168.1.102)
memphis: tis is a windows box -> memhis.redcor.home (ip 10.168.1.103)
chrissy: this is a unix box -> chrissy.redcor.home (ip 10.168.1.100)
dns server, ldap-server and samba are all running on haydn.
on haydn samba
2009 Feb 18
1
samba can not contact the ldap server
hi there,
I am working trough a tutorial on setting up samba and ldbap on a suses 11.1 box
everything worked fine so far but now samba can not contact the the ldap server.
all command trying it issue the following error message.
Failed to issue the StartTLS instruction: Can't contact LDAP server
how can I trace down what causes this?
thanks for your help
I added my slapd.conf and the
2009 Mar 22
1
samba4:login works, but domain not found afterwards
Hi there,
I am trying to work trough the samba4 tutorial.
What I did so far downloading samba, and updating it afterwards with git pull.
I did compile and install samba 4, and added the base user database with
./setup/provision.
I can start samba 4 and and use smbclient //localhost/test -Uadministrator%XXX
which puts me at the smb: \> prompt.
I did *not* configure the Step 8 (Optional):
2015 Mar 15
0
centos 7 database access only possible trough localhost and not IP
Hi Robert,
I have almost no experience with CentOS 7(still using CentOS 6). However, I
recommed the following checks:
1. Check that PostgreSQL is listening on 0.0.0.0 (all ip addresses) and not
127.0.0.1. To check, you can use the command:
netstat -tuplan
If PostgreSQL is listening only on 127.0.0.1, you'll never be able to
connect to it from the network. You'll have to change the
2019 May 06
0
Doman join issues
On Mon, 6 May 2019 02:51:18 +0000
Praveen Ghimire via samba <samba at lists.samba.org> wrote:
> From: Praveen Ghimire via samba <samba at lists.samba.org>
> To: "samba at lists.samba.org" <samba at lists.samba.org>
> Subject: [Samba] Doman join issues
> Date: Mon, 6 May 2019 02:51:18 +0000
> Reply-To: Praveen Ghimire <PGhimire at sundata.com.au>
2004 Aug 20
2
make_user_info_map in log with blank Doman and UserID args
Samba 3.0.5 Debian Package
Kernel 2.6.7 custom compile on Debian Testing
Configure Samba per my KLUG presentation on Samba PDC to Win2K Clients:
ftp://ftp.lueckdatasystems.com/pub/presentations/klugsamba3pdc-bookreview.pdf
In the error condition, a user account is assigned to the domadmin and ntadmin Linux groups.
In smb.conf -> admin users = @domadmin
On the workstation there are mappings
2019 May 06
0
Doman join issues
On Mon, 6 May 2019 07:35:07 +0000
Praveen Ghimire <PGhimire at sundata.com.au> wrote:
> Hi Rowland,
>
> I get the same error messages even with the following smb.conf,
> generated by the migration process.
>
> [global]
> workgroup = LIN
> realm = LIN.COM
> netbios name = LINSERVER01
> server role = active directory domain
2004 May 15
2
Doman Group in new version of samba
New to list sorry if this has been address but didn't see it in recent
archives.
FC1 with Samba 3.0.2
I had an older RH73 system running samba 2 on it and recent moved up to
FC and samba 3. Most everything transfered over well. I just took my
smb.comf from the old system and put it on the new system and then ran
swat making sure I didn't forget anything. Restarted server and wow...
It
2019 May 06
0
Doman join issues
Hi Louis,
Thank you for that.
I don’t have a /var/lib/samba/bind-dns/dns/ , only have /var/lib/samba/private/dns.
Apparmor is now stopped and masked. I had masked the smbd and nmbd post the migration, have masked the winbind now.
Have edited samba and bind as per your suggestion, changed the named.conf.options and krb5.conf
Rebooted the server post the changes and tried to join a windows 7
2019 May 06
0
Doman join issues
Hi Rowland,
Sorry about the confusion. It is Ubuntu 18.04 with Samba 4.7.6
I have a script that installs the following
apt-get install -y acl attr autoconf bind9utils bison build-essential \
debhelper dnsutils docbook-xml docbook-xsl flex gdb libjansson-dev \
libacl1-dev libaio-dev libarchive-dev libattr1-dev libblkid-dev libbsd-dev \
libcap-dev libcups2-dev libgnutls28-dev libjson-perl \
2019 May 06
1
Doman join issues
On Mon, 6 May 2019 11:12:17 +0000
Praveen Ghimire <PGhimire at sundata.com.au> wrote:
> Hi Rowland,
>
> Sorry about the confusion. It is Ubuntu 18.04 with Samba 4.7.6
>
> I have a script that installs the following
>
> apt-get install -y acl attr autoconf bind9utils bison build-essential
> \ debhelper dnsutils docbook-xml docbook-xsl flex gdb libjansson-dev \
>
2019 May 06
2
Doman join issues
Hai,
1) apparmor, disable it, and try again, so we can confirm if its an apparmor settings.
2) winbind is starting from systemd while as AD-DC you should disable that.
- stop the member parts of samba and systemd.
systemctl stop winbind smbd nmbd samba
systemctl disable winbind smbd nmbd samba
systemctl mask winbind smbd nmbd samba
- enable the samba-ad-dc part in systemd.
2019 May 06
3
Doman join issues
Hi Rowland,
I get the same error messages even with the following smb.conf, generated by the migration process.
[global]
workgroup = LIN
realm = LIN.COM
netbios name = LINSERVER01
server role = active directory domain controller
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate
idmap_ldb:use
2019 May 06
2
Doman join issues
Hi,
We are running test migration on the following environment in preparation for the prod migration. Any suggestions will be grealty appreciated.
OS: Ubuntu18.04
Hypervisor: Proxmox Container (LXC)
Samba Version 4.6.7
DNS: BIND9_DLZ
AD and File server in the same server. Have gone through the Samba documentation regarding this
We get the following when adding a machine (Windows 7) to the
2015 Mar 15
4
centos 7 database access only possible trough localhost and not IP
Hi there and hello to everybody,
I am all new to centos but I have good experience working with ubuntu and suse.
We are moving a an elderly SuSe box to a virtual machine running centos 7.
Now I experience the following problem.
I can only access postgres using localhost as host. If I use the IP address
(even 127.0.0.1).
I found a similar problem when accessing the
2019 May 06
3
Doman join issues
On Mon, 6 May 2019 09:47:44 +0000
Praveen Ghimire via samba <samba at lists.samba.org> wrote:
> Hi Louis,
>
> Thank you for that.
>
> I don’t have a /var/lib/samba/bind-dns/dns/ , only
> have /var/lib/samba/private/dns.
>
> Apparmor is now stopped and masked. I had masked the smbd and nmbd
> post the migration, have masked the winbind now.
>
> Have
2004 Dec 01
0
Can not connect to share "NT_STATUS_BAD_NETWORK_NAME"
I have Suse 9.1 + Samba 3.0.9 + winbind joined to a Windows
2000 AD domain "MyCompany". Yesterday for some unknown
reason (appears to be Win2K issue) connections to Samba and
the ability to browse the domain "MyCompany" from Win2K/XP
workstations failed but connections to the public share
offered by the Win2K server were OK. Also, all Win98
workstations and were unable to
2009 Dec 29
1
FW: tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Hi Dominic,
I wanted to wait for the original mail to pop up on the list.
But somehow it did not appear yet.
So while the problem seems to be solved meanwhile, I wanted to
comment on the relevant log portion below (see inline):
Dominic Gamble wrote:
> Hi Michael,
>
> As I mentioned, here is the full log file.
>
> Thanks for your time.
>
> Cheers,
> Dominic.
>
>
2009 Sep 06
1
NT_STATUS_BAD_NETWORK_NAME
Hi i'm trying to list the shares on my Brother HL-5250DN printer with the
smbtree command on linux but i keep getting the NT_STATUS_BAD_NETWORK_NAME
error message. I can however print to one of the shared printing services with
cups through the Device URI: smb://BRN_E1BEFA/BINARY_P1. Does anyone know what
the problem could be?
linux-wick:~ # smbtree
Password:
WORKGROUP