similar to: samba & dns

Date: Sun, 2 Jan 2000 18:55:12 +0100 From: "Wout de Jong" <woutdejong@yahoo.com> To: <samba@samba.org> Subject: samba & dns Hello, I encountered the following problem: First I installed samba-server (1.9.18, supplied with Red Hat 5.2) and everything worked fine. Then I added a DNS (named) at the same machine, just as an experiment. Now samba became unfriendly.

Hi, I can't get "net view \\<servername>" to work from my Windows test client. It fails with "The network path was not found". I followed some of the online debugging guides and have found that a couple of the test nmblookups on the server are failing. The server is named 'fileserver1' and its IP address is 155.2.196.251 for the purpose of this email.

Hi all, I am running RedHat 7.3 and Samba 2.2.3a. I am using DHCP for my Linux box (hostname: NGPLinux, IP 132.189.26.62). I can see the list of shares I defined by using "smbclient -L NGPLinux -N". I can resolve the name using "nmblookup -U 127.0.0.1 NGPLinux". However, when I tried to use "nmblookup -B 132.189.26.255 NGPLinux" on the local machine, I got the

I have an open PMR with IBM regarding a slowness issue when more than 450 smbds are trying to login and download roaming profiles. The system is a 6H1 with 6 RS64-III 668MHz cpus and 6 GB memory w/Gb ethernet. We have over 10,000 student accounts with roaming profiles and 800 XP-SP1 workstations for them to choose from. I've compiled 2.2.7a in 64 bit and 32 bit modes. Run it on both the 32

> Maybe there isn't a glibc version (although > it shouldn't be hard to port the Solaris version to >glibc). I will try to port nss_wins to glibc. I made some changes to smb.conf and follow the tests described in Samba diagnosis (www.samba.org/samba/docs/diagnosis.html) smb.conf [global] workgroup = NETMANAGER server string = Deltacom Samba Server printcap name =

Hello, With AIX 4.2 and samba 1.9.18 (or previous versions), I have a problem when i type : smbclient -L <servername> these are the errors in nmbd log: adding IPC service Added interface ip=10.120.1.250 bcast=10.120.1.255 nmask=255.255.255.0 Opening sockets Connecting to 10.120.1.250 at port 139 Connected write_socket(3,76) write_socket(3,76) wrote 76 Sent session request Session request

> -----Oorspronkelijk bericht----- > Van: James Atwell [mailto:james.atwell365 at gmail.com] > Verzonden: donderdag 13 augustus 2020 16:48 > Aan: samba at lists.samba.org > CC: L.P.H. van Belle > Onderwerp: Re: [Samba] Samba DNS fails when queried with > nslookup commands > > > On 8/13/2020 9:57 AM, L.P.H. van Belle via samba wrote: > > Hai James, > >

I have a Centos server that is running BIND and has IPv6 global addresses. I have entered a number of AAAA records into this copy of BIND in a local view and zone (tld is htt). Over IPv4, I have no trouble with nslookup ('nslookup - 127.0.0.1' and 'nslookup - 192.168.128.55'). I get the AAAA records back. But if I try to use the IPv6 address of the system I get a time out.

I have the following situation: Windows XP (SP2) clients connected to a Samba 3 PDC (3.0.7-2.FC2) on the domain "MNET". Also a separate Windows 2003 AD domain "SCH" (using Native Mode). I want to allow users in the AD domain "SCH" to logon to that domain from the XP clients by using their existing credentials and simply choosing the SCH domain in the XP logon

Yes, all these work here also (! With bind9_dlz ) nslookup nasa.org $(hostname -i) ( running the command on the DC itself.) nslookup nasa.org 1.1.1.1 nslookup nasa.org 8.8.8.8 Old samba version without the root zone provisioned maybe? That is an old bug. Which samba version is this? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at

Hi Louis, I'm going to update OS version following? your and Rowland's hint. Thank you Andrea Il 15/07/20 08:57, L.P.H. van Belle via samba ha scritto: > Yes, i believe you hitted "not" having the "root zone" in internal DNS. > If i recall correctly its somewhere in 4.4. or 4.5 fix. > > But as Rowland said, i suggest also upgrading. > > ps other fix

Hai, Only the forwarder is running in this systemd setup. This : 127.0.0.53:53 does NOT conflict with normaly resolv.conf setting Because samba or any dns server does not run on 127.0.0.53 Dont make the mistake to see this for : 127.0.0.1 Please show : /etc/hosts /etc/resolv.conf Depending on which one your using: /etc/network/interfaces and/or /etc/netplan/01-netcfg.yaml

On Sat, 08 Oct 2016 08:53:31 -0500 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > On 2016-10-08 07:58, Rowland Penny via samba wrote: > > > On Sat, 08 Oct 2016 07:50:03 -0500 > > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > > >> I have built a second dtdc03 and joined to my first dtdc01. Thought >

Hi Louis, root at dc:~# samba -V Version 4.3.11-Ubuntu Andrea Il 14/07/20 13:55, L.P.H. van Belle via samba ha scritto: > Yes, all these work here also (! With bind9_dlz ) > > nslookup nasa.org $(hostname -i) ( running the command on the DC itself.) > nslookup nasa.org 1.1.1.1 > nslookup nasa.org 8.8.8.8 > > Old samba version without the root zone provisioned maybe? >

Hi, I'm trying to get a Samba (version 3.0.8pre1-0.pre1.3) to play with some WinXP boxes. I'm using WORKGROUPS, not DOMAIN. The server is running under Fedora Core 3. And I'm following the troubleshooting chapter in the O'Reilly book, Chapter 9. I cannot browse the shares from my WinXP machine. I CAN browse and access shares okay as a client on the Samba server machine. I

Yes, i believe you hitted "not" having the "root zone" in internal DNS. If i recall correctly its somewhere in 4.4. or 4.5 fix. But as Rowland said, i suggest also upgrading. ps other fix is, switch to bind9_DLZ But again i still advice to upgrade. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens

Hello all, I am trying to configure a subdomain DNS server on a Cent OS 5.1 - for my lab. Brief configuration: Lab machine ---> 192.168.17.2 (should respond to DNS queries from hosts in 192.168.16.0/20 network) 1. I would also like to forward any queries outside the above network to our corporate domain (no firewalls between our 192.168.16.x network and the corporate network. The domain

On 05/06/16 10:05, Jo wrote: > I joined a Windows 10 Pro system to my (still experimental) domain. The > windows system actually hosts DC2 as a VM, and another Windows (Server 2008 > R2) at another location hosts DC1 also as a VM. The two locations are > connected via a VPN, both systems run only when needed. The windows system > does not directly use DC2 for DNS but instead talks

Hi Rowland, Thats not the point here, if this is a AD-DC or not.. ;-) I'll explain. This is about, how DNS requests are done on the system and accepted by the "dns service" You can install unlimited DNS servers on the AD-DC and chain them, but wize.. No offcourse not. :-) Turning off systemd-resolved is probably a good idea, yes, it is. But it does not harm if its on as long

On 2016-10-08 07:58, Rowland Penny via samba wrote: > On Sat, 08 Oct 2016 07:50:03 -0500 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I have built a second dtdc03 and joined to my first dtdc01. Thought >> all was well but, discovered that reverse dns is not correct on second >> dtdc03. >> >> root at dtdc03:~# host dtdc03