similar to: Samba PDC + Win2k Server & Terminal Server Client

I'm trying to locate the list of registry values to adjust how Win2K clients handle the user profile with the Win2K boxes joined to a Samba PDC and logging in with domain accounts. Specifically I would like to DISABLE roaming profiles!!! Many moons ago, the WarpServer Win2K client from IBM came with very good documentation on how to adjust that client to not create roaming profiles, etc...

I have joined my win2k client machines (win2k professional or win2k professional server) to my PDC. This worked fine and I did all recommended as e.g. in the HOWTO http://hr.uoregon.edu/davidrl/samba/samba-pdc.html#joining. So far I can also login localy to the win2k client machines using a local account and connect a network drive from the PDC using a valid account on the PDC (as given in the

I am having problems making the client win2k machine join the domain . My Samba PDC is configured as follows : 1>added trust account to the smbpasswd file (account to the win2k machine name). 2>set the global admin parameter to "student" (student acnt exists on smb server) Client is configured as follows : 1>user 'student' has been created . Problem : When I change

My Win2k client is able to recognize the domain but is unable to authenticate into the domain . Earlier i had created a trust account for the win2k client . Which username/password am i supposed to give here ? The manual says that the samba server admin usr/pwd should be given here , but which account is this . Below in the smb.conf you will see that the admin user is set to 'student' .

Hi Folks: I am seeing excessively long logoff times on my Win2k clients - I am using Samba as a PDC. Excessively long == 6+ minutes. Network is 100BT switched. Total cable feet between client and server (including switch) - 10 foot. According to the switch, both machines are running at 100BT speed, full duplex. There is what appears to be a lot of network traffic between the client and the

Win2k client is recognising the domain but is unable to logon . It asks for the usrname/passwd , which usrname/passwd am i supposed to give here . As shown in the smb.conf file below,admin user is set to 'student ' , but it does not accept this username , says ' unknown username or bad password '. Earlier the trust account of the client machine was created on the samba server .

Hi, We have Samba 2.2.6(+2.2.7 security patch) installed on solaris. Samba is used as PDC for WinNT and Win2K clients. The WinNT machines have no problems geting into the domain as machine trust accounts exist in /etc/passwd and smbpasswd file. However, Win2k clients are not able to join the domain. I did go through the documentation, and hence created root account in 'smbpasswd'

Hi All- Please tell me if I'm posting to the wrong list. I looked for the list called samba-ntdom (listed at http://us1.samba.org/samba/archives.html) because it seemed a more appropriate forum, but it looks like that list has been dissolved. Has the discussion for that list moved to some other list? Anyway, here's the problem that I'm hoping someone can help me with: I have

Hello all, Yesterday I've setup samba 3.0.2pre1 as PDC on linux Debian Wooody with 2.4.24 kernel on my home network. I have also 2 additional machnies running win2k with sp4 included. Samba conf file is as attached below: [global] ???netbios?name?=?zasoby ???workgroup?=?mojezasoby ???server?string?=?Serwer?Zasobow ???passdb?backend?=?smbpasswd ???os?level?=?65 ???preferred?master?=?yes

Hello, I have a Samba PDC running (using LDAP in the back-end). I'm able to join systems to the domain, and log in to each machine, at the console, as domain users. However, when I try to log into our Win2k Terminal Server (w/ Citrix Metaframe), the log in session crashes with winlogon.exe trying to reference memory. If I log into the machine via terminal server, as a local

Last week both win2k hosts on my clients network stopped working. Both report that they cannot copy files that are in the profile. All other versions of windows (includes XP, 98 and ME) kept working. Before last week all machines worked just fine. Here is what samba has to say about it: [2004/02/05 08:30:07, 0] rpc_server/srv_netlog.c:api_net_sam_logon(206) api_net_sam_logon: Failed to marshall

Dear sirs(madams): I've just configured samba 2.2.2 on FreeBSD 4.5 to server as a windows NT PDC. The domain once worked well after configuration. But today, I suddently encountered with certain trouble, that I can't join any clients to the domain any more. Even those I've joined to the domain sucessfully other days can't be joined to the domain either after I removed them and

I have a server running Samba 2.2.1a, which I'm trying to use as a PDC for a small LAN with Windows 2000 Pro and Windows XP Pro clients. The main problem I have is that users sometimes get this error when attempting to logon: `Windows cannot copy file \\mars\meadens\profile\My Documents\My Webs\_vti_pvt\services.cnf to location C:\Documents and Settings\meadens.GALAXY\My Documents\My

Quick Summary: I am trying to join some Win2k (Service Pack 4) machines to a NT4 style domain with a Samba PDC. One machine successfully joins the Samba domain. One fails. Current configuration: SambaPDC: - FreeBSD 4.9-RELEASE - Samba 2.2.8a (from binary package) Host1 (Silv): - Windows 2000 SP4 (5.00.2195) Host2 (Plaid): - Windows 2000 SP4 (5.00.2195) All machines are

Hello everyone! I'm having a strange issue with Samba. Here's the setup: WindowsNT 4 PDC Windows 2000 clients. Samba 2.2.7 on a Mandrake 9 system that has successfully joined the domain and is visible when the client systems browse the network. (config files and error log samples below) The problem is getting the Win2k clients to authenticate when they try to connect to shares that

I'm sure this has been discussed before, but would it then be possible to join a "real" NT4 or Win2k BDC to the Samba domain and establish the trust relation from our other Win2k? Or does the trust relationship have to be "registered" with the entire domain and therefore all the domain controllers? Khanh Tran Network Operations Sarah Lawrence College 1 Mead Way

I've setup Samba as a PDC. I have two machines using it for authentication. The rest of the clients on the network are still not using it. Before I switch I need to know more about how administering access to different network resources is going to work. For instance, we are running Terminal Server on Win2k and in the local user / group manager for each of the local users properties

My Win98(SE) Samba clients can query the Samba-exported printer status, but Win2K(SP3) clients cannot. Both clients can actually print documents. I am running Samba v2.2.3a on a Linux (Red Hat v7.3) system. This server makes 2 printers (via a LPR subsystem) and several shared directories available to our Linux, Win98 and Win2K (soon to be WinXP also) clients. From a Win98 client, print

This weekend I upgraded SAMBA from 2.2.2 to 2.2.3a then made it the PDC on our LAN. Original PDC was an NT4 Server. There is a Win2K Server running Citrix Metaframe-XP, and the old NT4 PDC Server was replaced with another Win2K Server to be the Database Server. I didn't want to bother with setting Win2K up as a DNS and DFS/ADS Server (required for being a PDC), so selected to make SAMBA the

I have set up a Samba PDC with LDAP password backend schema. I found the way of connecting win2k workstations to this Samba server by setting the parameter "workgroup" (in smb.conf) to the name of the domain I created previously in Samba/LDAP. Once in win2k workstations, I changed the identification from workgroup members to domain. But when validating, it asked for any user who