[PLUG] Having trouble with MS-DFS still...
I tried googling for MS-DFS client and got a ton of information about setting up Samba as a DFS server, but nothing about being a client. ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Having trouble with MS-DFS still...
I'm not convinced there IS anything different on the client side... The whole point of DFS seems to be to abstract away all of the client side complications that come with multiple SMB servers in an Enterprise. In other words... It appears to be an entirely server-side solution. OK, I am going to have to suggest a very not-Unix next step: You're gonna have to set up a Windows Server lab... I have a Windows Server 2008 license lying around, and I know Microsoft offers free trial WS2008 images on their website, so this is going to be focused on that... Although, I'm sure Google can help find similar guides for other Windows versions... First, here's a nice Microsoft blog introducing the idea at hand: https://blogs.technet.microsoft.com/josebda/2009/03/10/the-basics-of-the-windows-server-2008-distributed-file-system-dfs/ Then read the TechNet: http://technet.microsoft.com/en-us/library/cc753479.aspx Then use this step-by-step to setup a virtual swarm of Windows servers: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2003/cc737358(v=ws.10) Then set up a nice clean Windows 8 install with a free trial license, and connect to it... My GUESS is that it will connect exactly the same as it would to a single server... I may also expect the client to connect to the individual "Target folders" directly if they so choose... I don't know how to block them. Once you confirm that works... Then set up a nice clean Linux image and repeat the tests. I would expect it to also connect without noticable difference to connecting to a single SMB server. You may also be able to connect to individual "Target Shares" directly. Again, no idea how to block that... I would try it all myself, cuz this looks kinda neat, but I don't like the idea of using Windows in a production environment, so I guess it doesn't look REALLY neat... So it's hard to motivate myself :/ On Tue, Apr 3, 2018, 07:48 michael wrote: > I tried googling for MS-DFS client and got a ton of information about > setting up Samba as a DFS server, but nothing about being a client. > ___ > PLUG mailing list > PLUG@pdxlinux.org > http://lists.pdxlinux.org/mailman/listinfo/plug > ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Having trouble with MS-DFS still...
I have one instance of Windows Server 2012 R2 180 day trial running in Virtualbox on top of CentOS 7. Do I need two to three instances of Windows 2012 R2 to implement DFS properly? There are plenty of Windows 10 computers in the office, can the DFS server reference a single share across two Windows 10 systems? Do I need to bridge Windows Server 2012 R2 or is the default NAT that virtual box does good enough? Can I set a different IP address when I bridge? The Linux box is on 192.168.1.2, I don't want the Windows Server to share that IP address. I want the Windows box to be on 192.168.1.xxx. How do I implement Active directory? I apparently have to use Active directory if I'm going to implement MS-DFS. Other than that, can I use a samba server to replace a Windows server if I have to have multiple servers? ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
Re: [PLUG] Having trouble with MS-DFS still...
On Wed, Apr 4, 2018, 11:08 michael wrote: > I have one instance of Windows Server 2012 R2 180 day trial running in > Virtualbox > on top of CentOS 7. > That should work... Do I need two to three instances of Windows 2012 R2 to implement DFS > properly? Probably not for the tests you are running... I mean, replication is probably Windows Server only, but that's not critical to verifying that Samba clients can connect... There are plenty of Windows 10 computers in the office, can the DFS > server reference > a single share across two Windows 10 systems? > Probably...? I didn't see anything that specifies any requirements of the Target folders. If you aren't using replication, I don't even see a reason why a Samba server can't be a Target... Of course, one could simply try... Do I need to bridge Windows Server 2012 R2 or is the default NAT that > virtual box > does good enough? Can I set a different IP address when I bridge? The > Linux box is > on 192.168.1.2, I don't want the Windows Server to share that IP > address. I want the > Windows box to be on 192.168.1.xxx. > The clients have to be able to ping the DFS server. I imagine it could be done despite NAT, but I would want everyone on the same subnet, same broadcast domain, same NAT layer... How do I implement Active directory? I apparently have to use Active > directory if I'm > going to implement MS-DFS. > I don't think that Active Directory is a strict requirement... The example in the How To is in Directory mode, but it says a Stand-Alone mode is available... On the other hand... If the original system in question is in ActiveDirectory, then all of the clients will have to be in ActiveDirectory as well, and that may be part of your problem... Other than that, can I use a samba server to replace a Windows server if > I have to have > multiple servers? > I think that's what the server oriented discussion on the aforementioned Samba wikis was talking about... ___ PLUG mailing list PLUG@pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug
