similar to: Expected service, found `wins, dns, files'

Displaying 20 results from an estimated 3000 matches similar to: "Expected service, found `wins, dns, files'"

2002 Oct 04
2
Smbclient Connection to Samba server failed
I played with the smb.config file long enough to get both the smbd and nmbd daemons to run. Then ran TESTPARM against the correct smb,conf file without issue. Finally I tried the following command: [root@cofr3 /]# smbclient -U illingsk -L MySQL added interface ip=172.17.60.6 bcast=172.17.63.255 nmask=255.255.248.0 wins_srv_died(): WINS server 172.16.0.121 appears to be down. Connection to MySQL
2002 Dec 31
1
Trouble pinging servers DNS name.
I can ping the virtual Linux servers NetBIOS name and access a share. Perhaps someone can examine the attached named.conf file for errors and/or omissions. My virtual Linux server (172.17.60.6) has been configured as a WINS server, and a PDC. I am not, however, certain how to configure it as a DNS server beyond what is in the attached named.conf file. Here are the results of pinging the
1998 Feb 19
7
smbstatus
Have just upgraded to samba 1.9.18p3 on a RedHat 5.0 linux system... now... when i type smbstatus... this is what i get.. Couldn't open status file /var/lock/samba/STATUS..LCK so i assume that for some reason... this status file is not created upon startup.. Pat.
2003 Oct 19
21
Samba PDC
I'm trying to config Samba PDC using: The Unofficial Samba HOWTO but error apeared: The following error occurred attempting to join the domain MYDOMAIN: The specified network password is not correct I tried: Use Window's Group Policy Editor (gpedit.msc) to make the following changes in the Local Computer Policy\ Computer Configuration\ Windows Settings\ Security Settings\ Local
1999 Jan 23
4
smbwrapper
> What you are looking for is smbwrapper, which is in fact included with Samba > 2.0. However as it is not supported on all systems it is not included > in the default build (it should work nicely on Solaris though). > Essentially smbwrapper is a preloaded library which intercepts system calls and > simulates a /smb filesystem, so you can access /smb/SERVER/SHARE/file.txt.
2000 Sep 05
7
NMBD Not Starting
I moved an entire RH 6.2 server from one CPU to a new one using a tape backup/restore. Everything from the old server is working on the new server, but when SysV starts up smb, the nmbd daemon (2.0.6) exits with an error: create_subnets: No local interfaces! eth0 has already started according to the logs and console. Any ideas? Thanks. ______________________ Greg Kelley, IT Director SSA, EAA,
2002 Dec 19
0
Add Win2kPro Workstation to new Linux PDC
I created a new virtual Linux server running the Red Hat v7.2 distribution. After getting a MySQL/PHP application running, the next step was to add a Win2kPro Workstation to a new Linux PDC. Towards that end I modified the smb.conf file as described below to turn the virtual Linux server into a stand alone PDC. A 'MACHINE.SID' was created in the /usr/local/samba/private directory.
2008 Jul 29
2
syconf(_SC_PAGESIZE) versus getpagesize()
hello karel, thanks a lot for the klibc portability merges. current HEAD klibc failure: mkswap.c: In function ?init_signature_page?: mkswap.c:148: error: ?_SC_PAGESIZE? undeclared (first use in this function) although POSIX encourages sysconf() could util-linux use getpagesize() ? -- maks
2009 Mar 17
3
rndc: connect failed: 127.0.0.1#953: connection refused
My BIND9.6.0 on FreeBSD 6.2 works fine when I manually start with: root@ns2# named -4 -S 1024 -c /etc/namedb/named.conf But it won't start on boot and no error messages or log. And it won't start using rndc, it cause error message. Why does the error shows port 953 when I specified for port 53 in the config? rndc: connect failed: 127.0.0.1#953: connection refused Below are
2009 Nov 25
7
rndc start fails with "rndc: connect failed: connection refused"
CentOS 4.8, BIND 9.2.4 Hi All: I have a rather annoying problem with rndc which I have not been able to resolve despite much searching and many attempts to correct. When making changes to our DNS entries I have tried to use the following procedures: 1. Flush the cache buffers: rndc flush 2. Stop named: rndc stop 3. Delete the journal files: rm *.jnl 4. Edit the forward and/or
2016 Apr 28
3
RNDC errors using SAMBA_INTERNAL_DNS
Hi all, I've set up a simple domain using Samba 4.4.2 from source under Ubuntu 16.04. I accepted the usual defaults and basically followed wiki.samba.org to the letter. The main thing is I'm using Samba's internal DNS and not Bind (Bind is not even installed on the system). In the log.samba file on the first DC I kept getting this: [2016/04/28 17:01:02.716292, 0]
2018 Mar 12
9
Workaround for bind9 reload bug : samba_dlz Ignoring duplicate zone
Hi samba team ! I'm face with a new problem on a new Samba PDC install (Debian 9). I don't know why, but systemd run multiples "rndc reconfig" commands during the init script. So the bind9 log file show : -> A successful start -> A failed reconfig (samba_dlz Ignoring duplicate zone) at each boot/reboot. So I need to restart bind9 each time manually. I created a wrapper
2007 Sep 21
3
named & rndc
I've done something a while back that has messed with my named.conf and prevents me from restarting named service normally... My problem... # service named restart Stopping named: [FAILED] Starting named: named: already running [FAILED] nothing gets logged in /var/log/messages obviously, I can do this to restart it... [root at
2013 Feb 15
2
bind-chroot rpm only builds chroot tree?
I just downloaded the bind-chroot rpm and looked into it with Archive manager (so I am lazy), and no files, just the chroot tree. I am assuming there is some script that Archive manager does not show, or I am just missing it, because the ROOTDIR= did get added to /etc/sysconfig/named (and the one in the bind rpm is without this line). Just interesting that if you chroot, you are expected to
2007 Apr 24
5
Centos 5 where is rndc.conf and named.conf?
In /var/named/chroot/etc there is no rndc.conf or named.conf. Where are they? Webmin built a named.conf, but it is missing many of the 'default' entries. And it did not set up the symbolic link to /etc I am trying to follow instructions at: http://www.wains.be/index.php/2007/02/04/centos-chroot-dns-with-bind/
2005 Nov 26
2
rdnc error
Hello, I noticed in my logwatch file I have an error with my rndc key. I could 'play' around with it and may fix it but most likey just hose things up. I think I see the problem but not 100% sure. I think the key file has 3 different names. Here's the error: **Unmatched Entries** /etc/named.conf:23: couldn't find key 'rndckey' for use with command channel
2016 Apr 28
2
RNDC errors using SAMBA_INTERNAL_DNS
On 4/28/2016 1:05 PM, Rowland penny wrote: > On 28/04/16 17:21, Wayne Merricks wrote: >> Hi all, >> >> I've set up a simple domain using Samba 4.4.2 from source under >> Ubuntu 16.04. >> >> I accepted the usual defaults and basically followed wiki.samba.org >> to the letter. The main thing is I'm using Samba's internal DNS and >>
2020 Sep 30
3
Bind9 issue
Yesterday I had an issue with Samba v 4.13.0. Went to backup and discovered backup computer has a drive failure and backup is gone. Only resort is to rebuild the DC. I cannot figure out why bind9 will not "host -t SRV _ldap._ tcp.ad.dtntwk.work." or "host -t SRV _kerberos._udp.ad.dtntwk.work." root at dc1:~# host -t SRV _ldap._tcp.subdom.example.com. >
2006 Sep 14
1
bind errors after yum update to 4.4 CentOs
I recently upgraded my name server to CentOs 4.4 from CentOs 4.3 and bind was one of the many packages upgraded. I get the following message when performing an rndc reload " rndc reload rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid." which
2006 Nov 18
1
Bind problem - rndc key (after update?)
Hi list, here is what happened: today I noticed some resolution's problems on my network. I did a "service named status" and here was the output: # /etc/init.d/named status rndc: connection to remote host closed This may indicate that the remote server is using an older version of the command protocol, this host is not authorized to connect, or the key is invalid. In the