search for: nulti

Is anyone out there running Microsoft's Visual Source Save with a samba share? We are doing so here and are encountering difficulties. The "working directory" is a samba share. It seems that VSS is not manipulating file permissions appropriately when items are checked in and out. User always has write access to the item. Is anyone using MS VSS successfully with samba and care to

We have a total of 2 desktops upgraded to the recent Window 8.1. Neither is able to map the home share, which happens to be a DFS root, and of course cannot access DFS links. Errors we are seeing are "Server unable to perform requested operation" Or Using net use - system error 64 Or Using net use with ip addr in lieu of NetBIOS name -

The setting that fixed this issue for us was adding the following to our smb.conf: Server signing = yes We are now able to delay our implementation of samba 4.1 for the short term. Many thanks, Helen -----Original Message----- From: Marc Muehlfeld [mailto:samba at marc-muehlfeld.de] Sent: Monday, December 02, 2013 2:42 PM To: Nulty, Helen P; samba at lists.samba.org Cc: Hill, Jennifer

We have a central campus kerberos server. We have a local Active Directory domain which is a member of the main campus forest. We have 2 samba 3.0 servers currently configured: security = domain password server = SPHDC0 SPHDC1 where SPHDC0 is the primary domain controller, SPHDC1 is backup domain controller and neither of which runs in native mode. We want everyone, for both domain and

Mac OS details: Our client was able to access her network resources without any problem until yesterday. She is using a high end Macbook Pro. She has the latest full version of Dave 7.1 installed. Her Mac OS X is 10.4.11 When she attempts to connect to these resources she receives the following error: "The Finder cannot complete the operation because some of the data in

Hi list DFS Links in a separate share seems to work, but in the [homes] section does not. Is this a known problem? Samba is 3.0.26a. /etc/smb.conf excerpts: ---------------------------- 8< ---------------------------- [global] ... host msdfs = yes ... [homes] ... msdfs root = yes ... [dfstest] path = /data/dfsroot msdfs root = yes ---------------------------- 8<

Hello Johan, I'm having the same problems with DFS and WinXP clients since I upgraded to 2.2.8. I tried to clear the cache on the client side with dfsutil.exe that comes with the Win2000 SP2 but to no avail. Can anyone else confirm this problem? It's also strange that on the WinXP clients the version of the samba server is still registered as a previous version (2.2.6 or 2.2.7).

To sunmanagers and samba@lists readers: Thank you all so much for your help with the samba issue. Although the problem was not solved, your suggestions made it possible for us to narrow down the problem. We believe the problem are two office PCs that were recently configured with some new test software. All other PCs and user accounts work fine. I do need to upgrade samba to a newer version

Please note that Windows 9x clients are not true members of a domain for reasons outlined in this article. Therefore the protocol for support Windows 9x style domain logons is completely different from NT4 domain logons and has been officially supported for some time. Did you read this document? Let me know what needs to be updated and i will take care of it. Cheers, jerry

We are trying out samba 3.2.8. All of our samba servers have multiple network interfaces. With version 3.0.31 we were able to use Socket address = xxx.xxx.xxx.xxx, 127.0.0.1 and nmbd worked fine as did swat. With 3.2.8 that syntax causes nmbd to crash and complain about an invalid address. If we adjust the syntax to use Socket address = xxx.xxx.xxx.xxx Or socket