similar to: Migrating W2K Workstation to Samba Domain

I have recently set up an small SAMBA network(just my server and a W2K SP4 Workstation). My Server is acting as a PDC. Everything seems to work flawlessly, users, roaming profiles, netlogon script, etc... But I cannot make this machine to read my NTConfig.pol file. I have it at my NETLOGON share [/srv/netlogon] with rwxr-xr-x permissions. I have tried with different filenames (NTConfig.POL,

In our company's W2K-domain we decided to put all roaming profiles on Samba-servers (RH 9.0 / samba 2.2.8) The Samba-servers are configured for using DOMAIN-security. Part of our /etc/smb.conf look like [Profiles] path = /usr/local/samba/profiles comment = Profile-share browseable = no writeable = yes create mode = 0600 directory mode = 0700 We simply copied al the "old"

Samba 4.0.4 installed, provisioned by classicupgrade, running on Debian Squeeze: -------------------------------------------------------------------------------- The issue is, that changes to the roaming profile is not transferred after log ins/outs between Win2K and XP machine. In example: I log into the W2k machine with my testuser and create a "testdir1" and "testdir2" on

Hello samba-insiders, we have a WinNT 4.0 SP5 PDC and our samba 2.2.3a is member of the domain. The roaming profiles of our clients stored on the samba 2.2.3a server. All seams to be perfect but clients with W2K SP2 cannot use there roaming profiles. ---> "Access Denyed" is the W2K error message. But if the same user loggs on on a client machine with W2K SP1 all things are ok. In

Hallo, I'm running a W2K AD network with about 20 clients (mostly Windows XP machines, some Ubuntu 10.04 clients). I also have a couple of samba servers (debian 5) which are joined to the domain. I need to upgrade from W2K to something which is not EOL. The AD server is also a print server for the domain. I only have about 20 user accounts, so recreating them from scratch would be not

I've been running verious version of samba 2.2.x up to last night. I now converted all my server so 3.0 with ldapsam. All my w2k roaming profiles now refuse to load, complaining about not being able to load various files in the profile dir containing special chars. Things like Sendto\3>> floppy... or 3?floppy or 3||!!|floppy is displayed where it should be 3<ascii character for

Hello samba-insiders, we have a WinNT 4.0 SP5 PDC and our samba 2.2.3a is member of the domain. The roaming profiles of our clients stored on the samba 2.2.3a server. All seams to be perfect but only clients with W2K SP2 cannot use there roaming profiles. ---> "Access Denyed" is the W2K errro message. But if the same user loggs on on a client machine with W2K SP1 all things are ok.

Is there a way to disable Roaming Profiles on a Computer, with logon scripts or policy files? I have a network with W2K Workstation clients, but we also have a WinXP Pro computer that we must use and cannot install Win2K. I have read that using roaming profiles between different windows versions can cause problems. So I thought i could use login services from my PDC on that computer and avoid

I need to replace a Windows 2000 Server with a Samba box. The W2K is the only domain controller in the network and it runs Active Directory. I know the Samba-3 limitations as an Active Directory Domain Controller, but I don't need absolutely all the features. What I would ideally need is: * Single Sign On * .adm policy files support (for client security and use restrictions - clients are

I hope someone has some ideas on this problem I've hitting against since yesterday afternoon. I've set up a samba server (samba 2.2.3a on RH7.2) as a PDC as per the combined samba howto docs. I have no problem joining Win9x machines to the domain but cannot add a w2k machine to the domain. It always fails with the message (on the W2K worksation): login failure: unknown user name or

Hi, Trying to be simple and direct. My last email didn't get answers. Thank you and best regards. Problem: ----------- W2K workstations remains connected do samba server at port 139, even after logoff, and this causes: false wtmp information and no possibility do control (even no fail proof) simultaneous logins. Workaround ( not acceptable )

I'm using Samba 3.0.22 on Ubuntu 6.06.1 as PDC for our Windows workstations. The passdb backend is tdbsam. I want to employ roaming profiles and due to the fact that we have a mixed Windows environment (Windows 2000 Pro and Windows XP Pro) I have the following entry in my smb.conf: logon path = \\%L\profiles\%U\%a Basically, this works fine. If a user is working on a W2k workstation, his

I want to setup a linux box with samba as a file and print server for a LAN of 20 NT 4.0 SP3 workstations. I want the home direcotories to be on the server the clients to have roaming profiles. For this, do I have to make the linux box a domain controller? I want to avoid it if I can, because the domain control code in not on the production releases. I don't want to setup an NT server either.

I've some queries on Samba, hope that someone in the mailing list can help me :) 1) I've Samba PDC with W2k workstation (w2kwks). When I login into w2kwks, it created a folder with my username in C:\Documents and Settings directory (which I think is the roaming profile directory?) 2) When I configure Outlook 2000 on the w2kwks (for imap), it automatically create a Personal Folder in

> -----Original Message----- > On Mon, 29 Dec 2003, [ISO-8859-1] ?ncor Gonz?lez Sosa wrote: > > With Samba you can do only what you can do with NT4 using the > NTConfig.POL file. > > > You can copy the files Win2K creates in > c:\WINNT\SYSVOL\sysvol\domainname\profiles to a share called > "SYSVOL" under the path: >

I have a SMB Domain set up with a PDC and BDC. The BDC is joined to the PDC domain fine and shows up in the LDAP directory. I can add and delete users to the LDAP directory. I can use the user accounts to access the Linux boxes. My W2K boxes see the domain and domain servers when browsing. I can access the shared drive on the PDC. I cannot join the Windows servers to the domain. I get an error

There appear to be significant hurdles to migrating from a Microsoft to Samba PDC environment, something which I've been trying to do now for many months. The difficulties arise in moving user's accounts over to Samba 1. Local profiles. It does not seem to be possible to move from an NT4 PDC to a Samba PDC while retaining local profiles. NT4/W2k machines consider logons to the Samba PDC

After a frightening experience with W2K Active Directory, we've been considering an "emergency migration" to Samba. I've been looking at both 2.2.7 and the latest 3.0 alpha, but have found little information about migrating from W2K. Most information seems to be about Windows NT PDC. What I've tried is to pull the information from the AD tree with pwdump3 and put it in the

Hello, I still have a problem with my Samba installation. Userprofiles don't work under W2K SP4. They work fine with Windows NT 4. When loggin on for the first time the user profile directory is created. After loggin off however no data is written to the profile directory on the Samba PDC. When logging on there ist the following activity in the logs (debug level = 1; log.pc1): =====>

Hi everyone, I'm relatively new to Samba and struggling with the folowing: The system is a W2003 domain with W2K clients and Samba 3.0.14a-3sa on Debian (Debian package) I've made two shares: [homes] comment = Home directory read only = No valid users = %S create mask = 0755 directory mask = 0775 browseable = No [profiles] path = /mnt/sdb1/data/profiles/