similar to: msdfs root problems even after a reboot?

Hello, my company recently changed the stucture of some shares (Win2000). Since then, we are not able to access these shares from Linux/Solaris anymore. I tried smbmount and smbclient and can access the top-level directory of the share and see the directory structure, but I can't see any data inside these directories. A few days ago, someone told me that msdfs is used for the new structure

We restored to 3.0.23d after update to 3.0.25a because of strange dfs behavior. the detailed situation: on msdfs root server 'samba' ls -lR dfsroot/: drwxr-xr-x appl1 dfsroot/appl1 lrwxrwxrwx share1 -> msdfs:server1\share1 [dfs] comment = "SaMBa DFS root" path = /path.../dfsroot # next line does not work prior 3.0.25 !!! # hide unreadable = Yes

Dear Gents, We are using libsmbclient smbc_getFunctionRead to read from a Microsoft DFS share. Before each 64k read there are a QUERY_PATH_INFO and a GET_DFS_REFERRAL which slow down the transmission. Is there a way to query these only once at the beginning of the transmission and cache it? system: 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24) x86_64 GNU/Linux lib:

Since upgrading from 3.0.24 to 3.0.25a this past weekend, network drive connections are randomly being closed and immediately reopened. This creates "Delayed write failed" errors for Firefox and Thunderbird, various errors for Outlook with its PST files on network drives, and errors from programs like InDesign that "The network connection was lost for the file, or the file was

Hi all, Samba 4.3.11 is serving printers in my office from a server called "printserver". If a Windows 7 client tries to reach it using a short name \\prinserver , it can see the list of printers, but can't connect to any of them: "Windows couldn't connect to the printer" pop-up appears immediately. Weirdly, it doesn't happen all the times, sometimes it can

I'm trying to set up a new CentOS 4.2 desktop, and gdm refuses to start. It blanks the screen, displays the swirling blue circle mouse cursor that appears to be an hourglass equivalent, then drops back to the console window. It repeats this several times then displays the following error: The display server has been shut down about 6 times in the last 90 seconds, it is likely that something

Hi, First, I will try to make my terminology clear: There are two "things" MS calls DFS: 1. Server/share DFS - in this case you can define a "virtual server/share" that when a client tries to connect to, the server will direct it to another, real, server/share to which the client should connect. The virtual server/share may contain one or more real server/share

Hi, Iam trying to setup Samba version 3.2.3 on Redhat (RHEL5) server to use Active Directory for authentication. I followed the instructions from article in following website: http://technet.microsoft.com/en-au/magazine/dd228986.aspx Setup Winbind + Samba + Kerberos and it seems to work fine. I can see the users in Active Directory through winbind as well as authenticate users using NTLM

The permissions are apparently set incorrectly on the vnc SRPM in the FastTrack repo on mirror; I get "permission denied" when I try to mirror it. Thanks. Josh Kelley

I am using a Samba 3.0.21a share to centrally access my source code from multiple Windows workstations. Everything works as expected (in Samba), but there is a slight (but annoying) problem with the modification timestamp of the files on the Samba share. While I have verified that both server and workstation are synchronized to the same time (using NTP), it seems that there is a few milliseconds

I'm running Samba 3.0.21a (blastwave build) on Solaris 9. The Solaris servers have no printers attached or accessible, just file service. Samba users authenticate off a Win2003 AD controller and get printing from that. I got rid of the "Unable to connect to CUPS Server" errors by adding to smb.conf the line printing=bsd but I am still getting smbd[4809]: [ID 702911 daemon.error]

Is anyone using sk98lin Gigabit Ethernet adapters under CentOS 4.x? The version of the driver that ships with CentOS 4.x kernels was too old to support the onboard NICs on some Intel server boards that we recently got, so we installed a newer driver using DKMS. However, we're having problems finding a stable driver to use: the first version that we tried (7.09) gave a kernel panic when I ran

I am currently having problems accesing our samba msdfs shares from Windows XP SP2, Windows 2000 and WinXP SP1 seem unaffected. I have attached the smb.conf and the exports files that define the shares. Running ethereal on the different clients seems to point to the fact that XP SP2 no longer seems to be using the netbios-ssn (139) port. for GET_DFS_REFERRAL instead its using microsoft-ds

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

Recently I had the chance to look at smb service response times over OpenVPN using Wireshark/TShark. Here are 2 samples. In both samples a Win XP Pro machine is connecting to a server running samba-3.3.7 and openvpn-2.0.6_9 on FreeBSD 7.2-STABLE. Location #1 =================================================================== SMB RTT Statistics: Filter: Commands Calls Min

Why is that when you create a share, the default is 'msdfs root = yes'? Also, why is that a share that is set 'msdfs root = yes' -- or, rather, a share that does /not/ set 'msdfs root = no' -- advertises that it is a DFS root to the Linux CIFS client, /even /when 'host msdfs = no'? This sounds like A) a bug (ignoring 'host msdfs', and B) a misfeature (msdfs

Hi, We have been a samba shop since way back and have used DFS quit a lot the last years. When we went with security ads instead of domain our dfs died. We have tried 3.028(sun) in solaris wich we are leaving and 3.2.1 in linux, our migration target. For our 3.2.1 installation the config looks liket this and the problem manifests itself as a empty share. [Global] kernel oplocks = False oplocks

Is the issue below addressed in 3.0.25b? (no freebsd port available yet so I'm still at 3.0.25a) I can't see anything specifically about this in the release notes. I just want to add that I've also seen this behaviour on a windows xp x64 client. It's a pretty serious problem.. so I'm also thinking I may have to revert to an earlier version if it doesn't look like a

> What exactly is happening in my situation? As of now use FQDN due to lots of security fixed MS applies this is needed. So best is, dont use short (netbios) hostnames but FQDN. Read samba list subject: ( google for it ) > "Re: [Samba] Windows 10 point and print restriction" Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at

Hi Jeremy, It's now clear. We'll do a short term workaround somehow. I created the bug. https://bugzilla.samba.org/show_bug.cgi?id=11295 Thanks for the useful reply. Kind regards, Szilard 2015-05-28 2:27 GMT+02:00 Jeremy Allison <jra at samba.org>: > On Wed, May 27, 2015 at 11:16:08PM +0200, Szilard Matyas wrote: > > Dear Gents, > > > > We are using