HyperV and Samba
realrichardsharpe at gmail.com
Sun Apr 12 16:56:20 MDT 2015
On Fri, Apr 10, 2015 at 8:59 PM, Steve French <smfrench at gmail.com> wrote:
> I was doing some experiments with Richard and David's HyperV patches
> which seemed to work ok (at least for image creation, it failed when
> actually running the image due to a configuration issue) - I could see
> the effects of the three major sets of changes they made in the
> wireshark traces
> set compression
> request resilient handles
> various sparse file features used in image creation
> but something very basic caused problems when I didn't do image
> creation via PowerShell (as Jose's presentation gave as an example).
> With Samba 4.1 (even without any changes)
So, you managed to create the image via HyperV but it failed to start.
Do you have a trace of the failure? Perhaps we are not declaring
ourselves capable of Persistent Handles and other stuff when joining
> - "net ads join" (and also
> "net rpc join") will create and join a Samba/Linux computer to Windows
> 2012R2 domain (which you can prove by doing "dsquery computer") but
> the Samba server does not show in the list of servers in any of the
> Windows GUIs (e.g. HyperV list of servers, or the List of File
> Servers) so it is hard to manage. I can of course explicitly connect
> to the Samba server from Windows (NET USE or explorer), but am puzzled
> how to get Samba server to show up in the list of file servers (in
> HyperV configuration) so we don't have to do this through obscure
> power shell commands.
> Anyone have any success getting Samba to show up in list of file
> servers in these Windows GUIs - I had assumed that some LDAP entries
> need to be udpated in "net ads join" that aren't being updated.
More information about the samba-technical