similar to: Samba 3.6.23 and Windows 7

Yes, if you're using roaming profiles Vista will automatically accept your login (if your PDC is configured correctly, check the firewall on the clients and server also, write/read access to the profile for the current user, but i guess these things were already said here but I'm only replying to your last question without having read most of the rest) The profile is not needed to be

Hi people, I'd like to know about registry key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System\WaitForNetwork. The question is simple, but I didn't get to find the answer; so, the time to be specified, per default, is in minutes or in secounds? Thanks a lot, -- Marcio Oliveira. "Tudo concorre para o bem daqueles que amam ? Deus." (Rom 8,28)

Hi, I found that login to Samba4 PDC takes few seconds in XP, but very long in Win7. The Login in Win7 is fast when setting this: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\System] "WaitForNetwork"=dword:00000001 If I set it to 1, the login takes about 3 seconds. If I set it to 90 (decimal), then the login takes more than 90 seconds. Setting it to 0 means using the

> Yes, but do you delete the default Policies that are > hardcoded into AD ? > > Rowland > > You mean the default Default Domain policies. No, but i've never done that and im using these so im not deleting them :-) And stupid me i forgot the most important one. Open the registry editor and locate the below path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows

Hi all, I've got some problems with vista sp1 + samba 3.0.28a vista will not save the profiles nor load them. ! I'm all familiar with the .V2 thing. vista however does create the "profilename.V2" directory, but does not populate it with the data Xp machines work like a charm however. profiles path's are: \\<server>\profiles\testuser so the problem with the .V2 part is

I have Samba 3.6.6 configured as a domain controller, but am unable to get new machines to join the domain. I've set the WINS on these machines in the IPv4 network configuration and get as far as entering my samba (ldap) credentials, but the whirlything spins for a while then says it cannot contact the domain, domain does not exist. If a machine had already been part of the domain when it

You have a dotted domain like my.dom? The windows 8.1 will refuse to join. Just look at: http://tam.belchenstuermer.de/join-a-samba-domain-with-dot-in-its-name-using -windows-8-1/ Good Luck Daniel EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de Internet:

Hi. my last post was about upscale configuration for my WinXP clients, because I believed I had it working, but ... Next day I booted the client and .... it wouldnt let me log onto the domain again. :-( I am using Samba 2.2.8a with Ldap backend which works great in workgroup mode. Joining the domain is very easy and works well, but then after rebooting I get: "Es kann keine

El 6/7/2015 7:22 p. m., "Chuck Theobald" <chuckt at uoregon.edu> escribi?: > > On 6/26/2015 3:32 AM, Daniel M?ller wrote: >> >> You have a dotted domain like my.dom? >> >> The windows 8.1 will refuse to join. >> Just look at: >> http://tam.belchenstuermer.de/join-a-samba-domain-with-dot-in-its-name-using >> -windows-8-1/ >>

In FreeBSD 5.x only telnet/telnetd works 'out of box' with kerberos. Why ftp/ftpd, ssh/sshd and cvs do not support kerberos ? Thanks!

I have a Samba server which I set so that Windows clients have roaming profiles. It works but when the user logs off, his personal folder in C:\Documents and Settings remains there, although i created the key DeleteRoamingCache (as a DWORD) in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WinLogon and set it to 1. It seems a problem with the Windows client, but I'm not

Hi there! I have a Samba 2.2.2 PDC on linux 2.4.13 with ACL (acl.bestbits.at) support installed. There seems to be a problem with Roaming Profiles. Win2k with local NTFS filesystem will never delete roaming profiles (yes, I have regedited the DeleteRoamingCache to 1). In fact, any time TheUser logs back in, a new folder named TheUser.OURDOMAIN.??? (where ? is an integer) will be created,

Dear users, I have monthly station data (44) stations data for 45 years which I have read in R using read.table. the data is in the format: Year Month Station1 Station2 ...................................... Station 44 (i.e the column names in the 1st row), I also have the latitude and longitude of the stations in a separate file in R (in the format : Station LAT LON). I wish to

hello list, I noticed that when I run the command gpupdate in the clients I get the following error C:>gpupdate Updating policy... Computer policy could not be updated successfully. The following errors were enc ountered: The processing of Group Policy failed. Windows attempted to read the file \eccm g.cupet.cusysvoldomainPolicies{31B2F340-016D-11D2-945F-00C04FB984F9} gpt.ini from a domain

On Thu, Apr 21, 2016 at 01:25:14PM +0100, Rowland penny wrote: > My understanding is that the Badlock patches fixed a multitude of security > problems, That's not disputed, and is why we have persevered in trying to make the patched version work instead of just reverting back to the previous version (you'll note that one response on this thread advocated doing that). >

On Wed, Apr 20, 2016 at 03:42:47PM -0500, Karen Magee wrote: > Also tied winbindd and that was a disaster of a > different sort. > > It wouldn't use the local unix groups first, which will cause way too > many issues. > > All along, however, the PCs that connect (when not trying to use > winbindd) have consistently > been able to connect and use

On 21/04/16 12:46, Ian Collier wrote: > I hear your frustration - we've had the same troubles. My understanding > of this (which may be wrong) is: > > - The Badlock patches broke something in the Samba server which > means it's no longer able to contact the Windows AD in order to > authenticate users. My understanding is that the Badlock patches fixed a

I know it's an old release, and my apologies for wasting anyone's time. I've been asked about an older version of AIX 7.1 with Samba 3.6.23 installed. The requestor is moving to a Windows Server 2012 R2 domain. They want AIX/Samba 3.6.23 to be a domain member, using the 2012 R2 AD to authenticate users to access Samba shares on the AIX server. This is the way it's working

> > Good morning. > > I am looking to resolve the above vulnerability on our T-4 Solaris boxes. I have not worked or patch Samba before and not sure of the process. > > When I find and apply the patch will it resolve the issue on the version that we are running or do I need to bring our current version more up to date? > > Any assistance would be greatly appreciated.

I've now tired both client ipc signing = auto or client signing = required server signing = auto --- that did not work...Also tied winbindd and that was a disaster of a different sort. It wouldn't use the local unix groups first, which will cause way too many issues. All along, however, the PCs that connect (when not trying to use winbindd) have consistently been able to connect and