[Samba] Suggestions testing Samba 4 on same subnet as Standalone Samba 3 Server

[Mike]

On Tue, Jul 30, 2013 at 5:00 PM, Gary Dale <garydale at torfree.net> wrote:

> You're way overthinking this. Just give the new server an IP address that
> is on a different subnet. e.g. if your current server is 192.168,.1.10/24,
> give your new server 192.168.2.10/24.
>
> Secondly, since you don't have an NT domain, the differences between it
> and AD are not relevant. What you will find is the difference between a
> workgroup and a domain. This involves the logins and roaming profiles.
>
> What really doesn't change much are the file shares, although you can now
> simplify them by setting sharing according to domain group rather than
> individual ids.
>
> An even simpler way is to simply NOT use a separate subdomain. Set up the
> new server as the domain controller for the group. Leave the files &
> printers on the old server. Once all the clients have been switched from
> the workgroup to the domain, move the files and printers over to the new
> server, shut down the old one, then create an alias for the old server on
> the new one. This way, there are no more changes required on the clients.
> If a problem is identified, you can simply remove the alias and bring the
> old server back.
>
> Of course, you can convert the individual workstations to use the new
> server name at your leisure so that you can eventually remove the alias.
> However this is not necessary. In fact, if you later replace the new
> server, the replacement can assume the old name so that the alias isn't
> needed any more.
>
>
Gary,
Thank you very much for the helpful response.
Definitely going to find more info about creating an alias for the old
server on the new S-4 DC server.

One question regarding giving S-4 server address on different subnet -- how
would you ssh into it from a client on the other subnet -- 192.168.10/24?