similar to: Not Able to access share when SE_BACKUP_NAME enabled

Hi all, I committed win32-driveinfo 0.1.0 to CVS. What is it? =========== A class for getting information of drives Synopsis ======== include Win32::DriveInfo (sectorsPerCluster, bytesPerSector, numberOfFreeClusters, totalNumberOfClusters, freeBytesAvailableToCaller, totalNumberOfBytes, totalNumberOfFreeBytes) = getDriveSpace(''c'').to_a

I'm trying to configure a samba server in a Win2K3 domain as a dfs host. The dfs host part is working: from a win client I can map the dfs root on the samba server (on FC3 fwiw) and see the link I've created to a share on a Win2k3 active directory domain controller. From samba server, I can smbclient to the share on the Win2k3 DC, and can mount the share as "-t cifs" (but not

Hello all, this patch allows master process to drop more root priveleges under Solaris. My limited testing shows that code works, but I'm not sure that defined privilege set is permissive enough for dovecot. Unfortunately I have no root access to our Solaris servers to really test it. So if someone is ready to test this patch please do it :) Best regards. -------------- next part

Ok, this one has me stumped... I am implementing 3.0.1 on a new machine - Slackware 9 based. Got everything compiled (OpenLDAP, Kerberos 5) and installed Kerberos pulls the ticket without problem. The samba machine joins the domain without any difficulties. Here is where it gets weird. From the Win2k3 DC, I can not browse the samba machine - won't recognize passwords. However, from

I have the following problem: As DomainAdmin I want to be able to mount a Windows directory, do a complete directory listing, read and possibly write all files in that directory. And all that even if the user has not included the DomainAdmin in the list of permitted users. To do this properly, I need to raise the following DomainAdmin privileges: SE_CHANGE_NOTIFY_NAME SE_BACKUP_NAME

I'm using Samba 3.0.21a on Fedora Core 3 to authenticate against an AD domain. The box running AD is Win2k3 R2, so AD has the RFC2207 schema extensions applied. I've successfully configured Fedora to do auth through winbind with the normal backend (using uid/gid mappings). Now I'd like to reconfig to use AD as the backend. I was able to do this against a pre-R2 Win2k3 server with

This is Red Hat Enterprise Linux 3.0 server. It has the following samba packages installed: samba-3.0.2-6.3E samba-swat-3.0.2-6.3E redhat-config-samba-1.0.16-1 samba-common-3.0.2-6.3E samba-client-3.0.2-6.3E It is a standalone domain member server, joined to WinNT 4.0 domain. Everything works fine, except I could not copy large file from Windows to Samba share, always got this "The Path is

It turned out that Samba can not handle the following situation: 2 network cards bonded together, and they are connected to different switches. Samba can handle the following situation: 2 network cards bonded together, and they are connected to the same switch. Thanks, Hai >>> "Hai Wu" <hwu3@wpo.it.luc.edu> 05/05/04 12:34 PM >>> This is Red Hat Enterprise

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:

I have a problem related to what I thought would be a fairly simple procedure. We have a working OSX Server 10.4.10 Open Directory system, with Windows Services enabled via Samba as a PDC. We have joined approximately 20 WinXP workstations to the Samba domain, and OD users can log into these systems as expected (i.e. authentication works). I have a Win2K3 server that was recently purchased and

While attempting to use cifs to mount a win2k3 share, I get this error: [root@dhcp190 root]# mount //win2k3/data -t cifs -o username=administrator /mnt/smbfs cli_negprot: SMB signing is mandatory and we have disabled it. 2687: protocol negotiation failed SMB connection failed Where exactly do I enable smb signing? kernel 2.6.5 + samba 3.0.3

Dear Community, i have a problem with a new debian XEN 64bit squeeze Server, when i started a windows hvm domU. I tested with the routed and now in the bridge network mod. I start the domU with xm create win.cfg and 1 or 2 second the dom0 is reboot. I install a debian domU on the system, and this is without any problems in routed and bridge mod. In the logfile are no informations, in the routed

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

>From a discussion on samba technical about the inability to have Samba work as a DC when the original DC is a Windows Server 2000 machine. > > as Andrew asked you previously, the main question is : do you have some > > specific requirements for keeping a DC on that computer (eg. Exchange or > > whatever)? > > > > If you don't need to keep the DC role on

Greetings ... It seems I have really got myself confused ... I have a Win2K3 ADS domain, I have two FedoraCore systems, one with Samba 3.0.0 and the other with Samba 3.0.1. Both give me the same problem. If I try access the Samba shares from Win2K3 using the host number, I get prompted for a username and password, and no matter what I type in, I can't get in. If I use

Hi All, I've had Samba 3.4.7 setup as a fileserver connected to a Win2K3 domain controller working great for a while now. Roaming profiles work perfectly when logging in from the machines locally. However when I try and login to a WinXP or 2K3 machine via an RDP session (Terminal Services) it is unable to locate the profile. I bumped the logging up and still saw no reason why. When

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:

Hi I am trying to join a out-of-the box win2k3 AD domain controller it's been + forest prep for r2 domain samba Version 3.3.2 on Freebsd 6.3-RELEASE openldap-sasl-2.3 heimdal 0.6.3 adserver = AD DC server i installed (win2k3 box) domain = my domain name /etc/resolv.conf search domain.net nameserver adserver contents of /usr/local/etc/smb.conf [global]

I've attempted to create a Windows Server 2003 Native AD/Samba3 hybrid network (for curiosity's sake). Read extensively through all resources I could find and from what I can tell, I've set everything up as it should be. The Samba3 server properly authenticates to the Windows Server 2003 kdc, pull down users and groups via winbind, and is able to view the Win2K3 shares via smbclient.

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