similar to: Spoke too soon - problems with logons using new PDC

Hi - I'm setting up a new Samba PDC here in a 30-person architectural office. The current PDC is running on an older computer and hasn't been updated in a while. The new PDC will be Samba 3.4.0 running on Ubuntu 9.10. We don't use roaming profiles. My question is this - is there a way to "seamlessly" migrate the desktops to the new PDC from the old one without

Hello, I recently migrated all data and user accounts from our old Samba file server to a new (Samba 3.4.0 on Unbuntu 9.10) one. Everything is working fine except that there is one user whose SID is showing in the "Owner" column of Windows Explorer instead of the user name. It's not a big problem, but the user is uncomfortable with it and I'd like to know why it's

I am seeing some very peculiar things in the routines that REGISTER my * server with several accounts. I saw this on my console: . . . NOTICE[5126]: File chan_sip.c, Line 1878 (sip_reg_timeout): Registration timed out, trying again NOTICE[5126]: File chan_sip.c, Line 1878 (sip_reg_timeout): Registration timed out, trying again NOTICE[5126]: File chan_sip.c, Line 1878 (sip_reg_timeout):

I have succeeded in getting two tinc1.0pre3 hosts to connect, but I can't ping one from the other. I can ping the local tap interfaces. tcpdump shows that icmp echo requests are received by the other host, but no replies are sent. The two hosts are North and South. It is the same pinging North to South and South to North. The hosts are configured as follows: South: Debian 2.2

Hi, It seems unlikely that the KCC is the cause of these issues. The KCC is only responsible for telling who to connect (and when) and doesn't actually affect any underlying network connectivity. Connectivity between the spokes should not be required and the communication between them is usually just some stale data. But none of that should affect either of these commands. Unless the DRS

On Sun, Dec 18, 2016 at 5:20 PM, Garming Sam <garming at catalyst.net.nz> wrote: > Hi, > > It seems unlikely that the KCC is the cause of these issues. The KCC is > only responsible for telling who to connect (and when) and doesn't > actually affect any underlying network connectivity. Connectivity > between the spokes should not be required and the communication

Samba 4.5.1 (started with this version as well) I started with 3 domain controllers, DC1 and DC2 at the hub, and another, DC3 as a spoke. Everything was running smoothly with this config. No problems with 'samba-tool drs showrepl'. As soon as I started adding more 'spoke' domain controllers I'm getting timeouts in the 'samba-tool drs showrepl' command. I believe

Hey all, might be a tad bit off topic to samba, but not entirely unlrelated. Anyhow, as I understand it, the task of a BDC is to process most if not all of the domain logons before a PDC does so is it not? It has been my understanding that the BDC generally accepts and processes domain logons before the PDC does on a network to keep the load down on the PDC until such time as the BDC cannot

Hello, I ran into a problem the other day where our NT PDC and BDCs starting flaking out. They all thought that there was another PDC on the network and so would not promote. After several hours of fighting with the NT servers, we checked a change that had been made to our smb.conf on our fileserver. Namely, the addition of "domain logons = yes". My understanding was that this

Hi everyone, I have this code in Person.rb: def hashed_password(password) require ''digest/sha1'' require ''base64'' new_password = Digest::SHA1.new new_password << password new_password = "{SHA}" << Base64.b64encode(new_password.digest).chop end And here''s my test: def

Greetings. I'm having a bit of a problem using the sipdtmfmode app. I have two incoming paths to * from pstn via FWD that use differing dtmfmode. IPKall wants rfc2833, libretel wants inband. If I set dtmfmode= in the fwd peer config in sip.conf each works seperately, and I'm trying to use gotoif and sipdtmfmode to switch based on the CID calling. Output seems to indicate sipdtmfmode

Hello, I'm running Samba Version 3.4.7 on Ubuntu 10.04.2 LTS. I'm using Samba as the Primary Domain Controller. Things that work: - Clients can logon - I can run logon scripts - Roaming profiles are created for new users on logon However, when I try to logon again with the same user, I invariably get this error message: "Your roaming profile is not available. You are logged on

Hi, I am running a nice Samba PDC that caters to a dozen or so Windows XP-SP2 clients. Point is, those clients should login to the domain, then access the shares. But they don't, some of the users are stubborn, refuse to login and just access the shares via direct IP. What I want is such a setup that only those users that are actually logged in to the PDC via domain logon can access the

Dear List, I can't logon from my Windows XP clients to my Samba 3.0.10 PDC on gentoo - I have setup samba 3 pdc's on SuSE boxes earliers - I do not find a mistake in my smb.conf. The problem might be my win xp sp2 boxes. Can you tell me which settings to implement on my windows xp pro sp2 systems in order to be able to logon to a samba 3.0.10 pdc? Thank you for you help! Best,

Hi all, I'm using samba 3.4.7 on a debian stable with kernel version 2.6.26-2 smp running on a P4 3.0Ghz with 1Go memory. There are about 50 users in the domain, all worked fine til i upgrade from samba 3.0.14 to samba 3.2.5 from the stable debian repository and then to samba 3.4.7 from the lenny-backports rep, as i've already seen slow logon with the samba 3.2.5. here is the result

Hi! We're using Samba as PDC, and recently had a strange crash on the system (none of the NT-machines authenticated anymore). I re-created the user database and passwords on the server (TurboLinux 2.2.14-5, with Samba 2.0.6 & 2.1alpha for auth.) and also re-newed the profiles making 'em local on the NT-workstations. Sometimes when the NT-PC gets rebooted, I can't authenticate it

Hi all, I have setup Samba 2.2.3a on Mandrake 8.2 and have domain logons for my Windows 2000 Pro box working perfectly (although I've had to move the profile path to inside each user's home directory to avoid "Access is Denied" errors during logon - suggestions welcome!). Whenever I try to join with one of my XP boxen though, the domain joining stage works up until it comes

Hi, I am running OpenVPN where i have one central hub VPN server, and multiple spoke VPN clients. I can ping from each client to the server and each client to computers on the subnet which the server resides (192.168.2.0/24) so it works ok there. I cannot however, ping from one client to another client. I guess the packet path would go: clienta -> vpn -> shorewall/router -> vpn ->

List, from the Dutch "Computable" paper ICT tabloid and daily ICT subscribable mailing-list and so-called verwittigingsbrief/ad hoc news letter, partly translated into English by me ;) Dutch readers only: http://www.computable.nl/nieuws.htm?id=524000 "Manage Windows clients from Linux servers" blahblahblah Zenworks 7, the latest release of Novell's sysadmin suite".

Hi Folks, This has been driving me nuts all day. I've been unable to google myself out of it. Maybe someone here can help? I followed the instructions from: http://www.tinc-vpn.org/examples/macbook-install/ Ubuntu server <-> Ubuntu server works just fine with the same config. Ubuntu server <-> Mac laptop not so much. The error I'm getting is: 2012-04-10 21:48:44