similar to: Samba 3.0.28a PDC and Vista Clients

Did you have profile files written? With Xp it is profiles.V2. I made my profile-path reside in the home directories of the users And it worked on the fly Ex: [homes] path=/windows/winuser/%U [profiles] path=/windows/winuser/%U/profile Greetings Daniel -----Urspr?ngliche Nachricht----- Von: samba-bounces+mueller=tropenklinik.de@lists.samba.org

Hi folks, I've been testing out Windows Vista Enterprise today. It defaults to only using NTLMV2 authentication. I'm testing with Samba 3.0.23d running on Sparc/Solaris 8. Samba is configured with security = domain The password server is a Windows Server 2003 domain controller. I've joined Samba to the domain. I simply can't get Vista to connect unless I change its security

I searched around and couldn't get a clear answer on a Samba 3 PDC and the ability to have a Vista "business edition" client: 1. Join the Samba 3 PDC domain for single sign-on. 2. Access Samba 3 PDC controlled shares I read that as of Samba 3.0.21 or so that NTLMv2 works well with Vista computers (which default to only NTLMv2) so they can work with Samba provided shares. This is

Hello :-), I have some problem with the cifs client of linux. I can't mount a volume from a Windows 7 machine with NTLMv2 authentication. e.g. # mount -t cifs //win7-box/C\$ mount-point --verbose -o sec=ntlmv2,credentials=smb-passwd mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) #dmesg | tail Status code returned 0xc000000d

Vista32 3.0.25pre2 (I understand vista patches for "share level" are already in) security = share (with "valid users" on share definition) host msdfs = no user/pass in smbpasswd file. If I use "connect network drive..." method with "connect as another user", then it will always work. If I use start, search , \\server\share and then type user/pass in

I have a Linux server providing file and print services to a small network of XP systems. The printer and most of the shares are available to all as read-only. One particular share is used by the XP Administrator accounts (mapped to root) to hold XP backup data. This has been working fine for the last couple of years. A new system added to the network runs Vista Home Premium and along with

I am suddenly no longer able to see any existing files on one of my shares, from my Windows clients. I have a Linux server (Fedora Core 8) which used to be my firewall and router as well as file and print server. There are two Samba shares on it I have mounted on various Windows clients: my home directory and a multimedia directory with my music and videos, etc. I mount the former as H: on all my

I'm trying to use smbclient to look at a Vista box but I keep getting: # smbclient -L user-pc -U Kellie Password: <Kellie's password> session setup failed: NT_STATUS_LOGON_FAILURE I know the user/password combination is good. I googled around and got the impression that Vista didn't play well with Samba because of some authentication protocol that Vista uses but I also got the

I'm having a very strange permissions problem with Samba 3.4.7 (installed via backports.org) running on Debian Lenny: If a Windows 7 or Windows Vista client tries to use Windows Explorer to access a user's home directory with permissions 0700, the client gets a permission denied error. If the directory is made world readable, it works. (For one user, group readable also works. For

We've got nicely ADS integrated Samba-3.0.27a servers that are working fine with Win2000 through to standard Vista. However, we are starting to test RC1 of Vista SP1 and discovered that once applied, that workstation cannot connect to Samba server shares - unless the share is open - i.e. no "valid user" style settings. The moment one is defined, Vista fails to connect and pops up an

Hello to all. I?m using squid + samba to authenticate my users with active directory. The error occour only in the first time i authenticate an user. All works fine, but i have this is my logs: ==> /var/log/samba/log.winbindd <== [2008/05/21 00:32:36, 2] nsswitch/winbindd_util.c:add_trusted_domain(171) Added domain BUILTIN S-1-5-32 [2008/05/21 00:32:37, 2]

I found the solution: I tried the srvmgr tool from microsoft to get connected to my samba 3 domain (from an XP client). And this tool told me the same "There is no PDC found for your domain. You may go on but but your rights may be Restricted." As I logged on I saw that both my PDC and BDC where BDCs. I stopped my BDC. Logged on to my PDC and remembering that I had also smbd4wins

Hi guys i asked about this a couple days ago but i'm guessing everyone glanced over it. So here's my problem. I have a SambaPDC with LDAP With WinXP i can join/login the domain fine. With WinVista i can join the domain but can't login to it after i join to the domain. It gives me an RPC failure. I noticed that it doesn't seem to even find the PDC. I don't even get any

What is Your samba version? If above 3.02 In Your smb.conf global section: #vista compatibility client lanman auth=no client ntlmv2 auth=yes Next on your vista business or higher Go to your networkcenter an put recognize network(netzwerkerkennung) to on. -----Urspr?ngliche Nachricht----- Von: samba-bounces+mueller=tropenklinik.de@lists.samba.org

I'm trying to get a new Vista Business client to connect a newly created Samba server. Windows XP clients connect without issue. I have tried changing 'Network Security: Lan Manager Authentication Level' to 'Send LM & NTLM use NTLMv2 session security if negotiated', as suggested on other sites, but to no avail. We have a domain, but both the Samba server & the Vista

All, I need to force XP clients to use NTLMv2 when mapping to samba 3.6.12. My config is: ntlm auth = No client NTLMv2 auth = Yes client lanman auth = No client plaintext auth = No lanman auth = No XP systems can still map shares with the above config. If I add: max protocol = SMB2 min protocol = SMB2 W7 systems map shares, XP systems cannot map shares even if I change LAN Manager

Hi, Problem: Out of the blue Vista on my laptop decides it doesn't want to mount a share over PPTP VPN connection. I can mount the share in the local network but I can't do it over VPN. When trying to access the server, using "net view \\172.16.1.71" it shows the error in the subject. Platform/Versions: OS: Sun Solaris 10 11/06 release Samba version:

We have Samba setup for our shared drive. I have pasted the smb.conf file below. Everything is working well accept when we try and run an EXE file using Windows Vista. When we run an EXE file it first ask for UAC control then it pops up the username and password prompt. You must then type your username and password in again before it will run. I think the issues is that UAC is now running the

I'm working on trying to get Samba 3.0.23c to work with Vista and I've run into a snag. If a share is set up for security = share, and protected with a password, when I try to mount the share using Start->Run->\\server\share, the password is rejected by Samba for about the first 10 seconds, but after that, it lets me in. I've tried all the common suggestions such as changing

3.0.25rc1 has the same issue. On Fri, 06 Apr 2007 22:52:05 +0200, Giulio <giulioo@gmail.com> wrote: >Vista32 >3.0.25pre2 (I understand vista patches for "share level" are already in) >security = share (with "valid users" on share definition) >host msdfs = no > >user/pass in smbpasswd file. > > >If I use "connect network