similar to: Status of samba 3.0 against Win 2003

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Perhaps using a MS-DFS share would be more useful in this case? This would allow three real shares: \\server\accounting \\server\personal \\server\public which would appear as \\server\users\accounting \\server\users\personal \\server\users\public. See http://samba.org/~jht/HOWTO/Samba-HOWTO-Collection.pdf for more information on MS-DFS - -Tom

I've been reading through a lot of documentation and haven't found the answer to this question. I'd like to setup a DFS Root on a Win2K3 server with some Samba server shares participating as replica links. Is this possible? I've got the shares setup on the Samba servers and have no trouble accessing them from windows computers. I tried to setup the links on the Win2k3 server, but

Hi All, Any clues as to what is causing this? I have seen similar questions asked before in regards to joining ADS domain but have not been able to find a solution to my problem. The domain is a Native mode ADS on win2k3 with signing required. Please let me know if additional info or logs are required to diagnose the problem. I did a 'net ads join ADSDOM -U

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Would it not be possible to make the archive bit map to a Posix extended ACL instead of to the execute bit? - -Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFBWDuj2dxAfYNwANIRAvmnAJ4r1Q/2X7YyPKgGWbnnB3pv6WKDjwCgn+Vd 8USnnc35+uAa2GxUmejlDBc= =Bu48 -----END PGP

New issues (2) ================================================= 1) Data corrupted after copied into a 32bit win2k3 guest on 64bit hypervisor with rtl8139 http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1025 2) pcnet network of 32bit win2k/64bit hypervisor is not stable. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1026 Fixed issues (1)

I've gotten samba working with ACLs over an XFS filesystem. Everything works pretty well with knowledge of the workarounds (cannot remove group everyone, etc.) The only major problem I have is that ACLs don't inherit correctly. The default in Windows 2000 is to have a sub folder inherit the permissions of the folder it is in on creation. By default, the Samba share's folders don't

Hi all: I'd like to know if (and if so by when) Samba will be able to run as an Windows 2000 server (Active Directory Server) in itself..? Is that scheduled in future plans at all ? I read Samba 3 can run as a member server, but I'd like to know if I can hold on my migration from NT4 projects, until I can have a Samba only network..? Thanks in advance for any feedback, Carlos

I've been trying to setup Samba to authenticate users against accounts existing on a Windows 2003 Server without any backwards capability. Ideally, this needs to be done without any changes to the Windows 2003 Server. Users will not be logging into the Samba shares at all. This is merely for authentication. I'm running FreeBSD 4.10-Relase #4 with Samba 3.0.8. This is my smb.conf file:

There are many discussions about this problem, but none of the developers of samba stepped in and gave any good explanation. Is this solved in Samba3.0.0 official release? (In what's new section of 3.0.0rc4, the 14th point is win2k3 security settings related matter. Is this the fix for SMB signature?) In one of the discussions there is a mention of disabling security option of Digitally

Hi list, Just in order to avoid loosing my time, I would be happy to know any success stories about configuring a Win2k3 as a Samba 3 client, just as any others MS client ( WinNT pro, Win2k pro, WinXP pro ). If so, is there any tuning on the Win2k3 client and the server ( Samba 3 PDC + ldapsam, but no kerb ) ? I'm expecting mistakes with users sharing their roaming profiles between Win2k

New issues (0) ================================================= No new issue. Old issues (4): ================================================= 1) IA32E/PAE: 32bit Vista RTM network doesn''t work. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=840 2)time latency is a negative number on window guest when vcpu > 1 http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=895 You

Hello folks! I am trying to make sure we can use Linux/Win2k3 mix in my company. After reading up in the documentation I fealt it sounded so good I would propably get there with little effort... Well, halfway there I got fast enough. But that won't do... I have successfully joined the AD-Domain from my Linux host. And I also can authenticate a AD user in the Linux host. I used nsswitch and

Hi list, My goal is to share a few shares from a solaris 9 host with a new win2012 domain. Im rather new to solaris (some years of linux exp, but samba has been a LONG time ago) The solaris machine has been created as a machine account in AD under its hostname by the windows admins in the new win2012 domain. (Thats not me, although I have domain admin access if need be) I have an issue changing

It might help if you view the default directory ACLs using the getfacl utility. These are what will be inherited by stuff created in the lower directories. I would ask yourself if you actually need ACLs at all. The Samba share permissions are pretty thorough and life is far easier without ACLs as you can clearly see what permissions are in use and backups are not an issue. ACLs can quickly

Samba doesn't allow connections from usernames that have & in them. For example, using 2.2.5 and winbind with security = DOMAIN password server = win2kmixed workgroup = MIXEDDOMAIN all my users can login, (for example MIXEDDOMAIN+aho, MIXEDDOMAIN+tdickson), but my users named "&" and "bobalso&" (which should be MIXEDDOMAIN+& and MIXEDDOMAIN+bobalso&)

Running the command: wbinfo -aDOMAINNAME+Administrator%password works, in fact, all of the wbinfo commands report data as they should. However, when I try to connect to a share on the SMB server, I get the following error message in the logs: [2003/04/21 08:28:59, 0] smbd/password.c:connect_to_domain_password_server(1328) connect_to_domain_password_server: machine DWP rejected the tconX on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What is the standard procedure for making edits of smb.conf take hold? For example, what I'm seeing is a share that has given R/W access to a user named Tom, when I change Tom to read only, he is still able to write to that share until I stop Samba and restart it. The documentation seems to refer to a 1 minute reread of smb.conf, but I don't

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ~ /usr/bin/net ads join -Udennisb dennisb password: [2004/11/02 17:31:56, 0] libads/ldap.c:ads_add_machine_acct(1006) ~ Host account for if-srv-hos1 already exists - modifying old account [2004/11/02 17:31:56, 0] libads/ldap.c:ads_join_realm(1342) ~ ads_add_machine_acct: No such object ads_join_realm: No such object Also: net user | wc -l reports

Here's the procedure: # qemu-img -f qcow2 /vm/win2k3.img 8G # virt-install --connect qemu:///system -n win2k3 -r 512 --vcpus=1 -c /home/temp/win2003sp2ins.iso -f /vm/win2k3.img -s 4 --network=bridge:br0 --mac=00:ff:ff:ff:58:58 --noautoconsole --vnc --os-type=windows --os-variant=win2k3 --hvm --accelerate And I get error as below: Starting install... internal error unable to start guest: qemu:

Hi, for the last two weeks ive been trying, to authenticate against a samba-domain using a win2k3-server. the server joined the domain without any problem and the basic login seems to work. but if i try to execute programs from mapped network drive (mapped using a domain-logon-skript), it fails with a message telling me, that i dont have sufficient rights to do so. the share has a forced user