similar to: Access denied using IP when joined in MS domain with RODC

Hello, Concerning my problem with not being able to connect to our domain with our Samba clients, there is a further piece of evidence in my samba.log, and I'm hoping that someone who is more experienced in dealing with WINS and domains can clarify the nature of these messages from the log: sync_with_dmb: Initiating sync with domain master browser PLEIADES<20> at IP

I am seeing the following messages logged every 20 min on a Centos 5.5 Samba 3.5.7 (SerNet RPMs) PDC. wins server = yes is set and the 172.17.1.50 address is the address of the PDC. From a Windows client perspective the the domain is functioning as expected. There is a Samba BDC and mulitple Win2008 R2 member servers in the domain. Are they anything to be concerned about? [2011/03/11

Hi all. After set up a BDC, I found a weird problem on my log.nmbd file, the case is that my nmb (on BDC) is not able to connect to the local wins "server", just receive a time out . I set the wins support = yes which is the only mandatory parameter according to samba doc. I tried to shut down the firewall even. The log output is: === ....... === become_logon_server: Atempting

Hello, I said earlier that out big Samba problem appeared to be completely resolved after I finally made sure to get a clean install of Samba 3 and ensured that the daemons were being started up properly. However, that was before I checked on our win2K clients! We have an odd little problem here, in that all of our WinXP clients can connect to any of our Samba shares without any problem,

Hi, here is a client computer and a server computer (Debian Wheezy, armel, samba Version 3.6.6, IP address: 192.168.1.2, Name: xyz). Problem: wins doesn't answer nmblookups by the client on the broadcast address: client$ nmblookup -S xyz querying xyz on 192.168.1.255 name_query failed to find name xyz Why is that so? How to fix this? When I specify the the server IP I do get an answer:

Hi, I have checked out the cvs tree on Monday, Aug 25 which includes your patch, built and installed it but without success: log.nmbd: [2003/08/27 16:34:00, 0] nmbd/nmbd_nameregister.c:(73) register_name_response: Answer name EMEA.CORPDIR.NE<00> differs from question name EMEA.CORPDIR.NET<00>. [2003/08/27 16:34:00, 0] nmbd/nmbd_nameregister.c:(73) register_name_response: Answer

Hi list, Thanks in advanced. I have written a winbindd client software to do NTLM authentication by using WINBINDD_PAM_AUTH_CRAP message. that is to say, my winbindd client is similar to ntlm_auth, but with high performance. when I test it under large traffic, most of the time they all work well. and the transaction per second can reach more than 900. but sometimes, winbindd will return

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everybody I'm trying to set up a samba server on a win98 net. Samba server is running over linux Fedora Core 3 and the domain server and dhcp server are running on a windows xp. The problem is that can connect to any resourse at the samba server, and I got the message: on Win98 client "No route host to the network" or something

Hi i have a big quantity of problems with Winbindd/squid ... it's very unstable on my proxy server and don't know why ... first problems: 1- I have restart my PDC and after restart, my winbindd denied all access and put a INVALID_COMPUTER_NAME ... i restart winbind and that's work now ... winbindd can't contact another PDC ? he can't recontact automatiquely the PDC

Ok, but why if i browse the network from the client with the remote rodc and the rwdc used as replication partner for rodc join online, everything work as expected, but if i shutdown the rwdc used for rodc join replication partner offline, client no work anymore? The join command for the remote rodc RODC-1 is: samba-tool domain join scratch.lan RODC --server=dc-1.scratch.lan --realm=SCRATCH.LAN

On Mon, 30 Dec 2024 16:07:31 +0000 Manzini Enrico via samba <samba at lists.samba.org> wrote: > Hi Rowland > We actually use RODC's because we have a customer with hub and spoke > configuration with 4 RWDC's in the central site, and about 80 remote > sites with RODC's deployed, all of these with low hardware security, > sites where the machine can physically can

Hi Rowland We actually use RODC's because we have a customer with hub and spoke configuration with 4 RWDC's in the central site, and about 80 remote sites with RODC's deployed, all of these with low hardware security, sites where the machine can physically can be stolen, so we opted to use RODC's machines at the remote sites The connectivity and dns resolution works both fine, with

Hi Marc, > Am 08.04.2015 um 17:25 schrieb BRIEC, Pierre: >> On Site1, the machines accounts are specifics, same for the Users and >> Groups except 1 group that is common with Site2 (The Teachers). >> Today, each site is independant, >> >> Now, i would like a create a new domain Samba4 AD whith all machines and >> users from site1 and site2 together. >>

I just checked the SOA records on my samba DCs and noticed a few oddities: michael at sles-bree:~> for i in ad{1..4} sles-bree sles-shire; do host -t soa main.adlab.netdirect.ca $i | grep SOA; done main.adlab.netdirect.ca has SOA record ad1.main.adlab.netdirect.ca. hostmaster.main.adlab.netdirect.ca. 177 900 600 86400 3600 main.adlab.netdirect.ca has SOA record ad2.main.adlab.netdirect.ca.

On Tue, 24 Dec 2024 11:38:17 +0000 Manzini Enrico via samba <samba at lists.samba.org> wrote: > Hello, > we are testing a dc/rodc configuration with Samba AD, but we are > stuck with a problem that occurs when one of the writable DCs (the > one that was used as a partner during rodc join) is shutdown: Test > configuration: > - writeable dc and read only dc Samba

Hi Rowland I try some several test and: - tried fsmo transfer from the rwdc used as replication partner to the secondary dc, no luck, problem persist - tried join with no replication partner specification, no luck, problem persist Also during the join procedure the rodc anyway find a domain controller to use as a replication partner (it say "find dc dc_name", and after the join

Hi, If you don't make much progress on your own, one thing you could do is turn up the logging level and send in some logs and network traces (and the steps you took). This is usually the easiest way to diagnose any obvious issues and gives a much better sense of what is actually happening. One other thing is that we generally recommend against .LOCAL domains although I would have no

On Sun, 5 May 2019 10:13:07 -0300 Emerson Kfuri <emersonkfuri at gmail.com> wrote: > On Sun, May 5, 2019 at 9:52 AM Rowland Penny via samba < > samba at lists.samba.org> wrote: > > > On Sun, 5 May 2019 09:20:37 -0300 > > Emerson Kfuri via samba <samba at lists.samba.org> wrote: > > > > > Hello, > > > > > > Recently I

On Wed, 24 Oct 2018 09:45:39 +1300 Garming Sam <garming at catalyst.net.nz> wrote: > > On 23/10/18 9:48 PM, Rowland Penny via samba wrote: > > On Tue, 23 Oct 2018 10:07:29 +1300 > > Garming Sam via samba <samba at lists.samba.org> wrote: > > > >> Hi, > >> > >> On 20/10/18 1:26 AM, Julien Ropé via samba wrote: > >>>  The

Hello Denis, Am 09.04.2015 um 15:37 schrieb Denis Cardon: > could you please develop on that RODC support? I am very curious to know > what should be working and what should not. > > Actually I've been using RODC with partial success: RODC join, user and > machine account preload (with corresponding patch), dns update throught > netlogon service on RWDC, connexion when RWDC