Configure Windows Server 2016 & SQL Server 2016 for cross-domain windows authentication

• Scott In Sydney

  Hall of Fame

  Points: 3331

  More actions

  July 30, 2018 at 1:38 am

  #355047

  Hi,

  I fully admit this is more a Windows Server configuration question than SQL Server per se.  However,
  1) I've gotten no joy from posts to serverfault.com and superuser.com;
  2) the end goal is in fact SQL Server functionality - the Windows Server machine configuration is merely to support that goal;
  3) I'm hoping someone here has set this up before and can advise me.

  tl;dr;  How can I configure Windows Server and/or SQL Server to allow Windows Authentication with a domain account in DOMAIN_A to a SQL Server instance running in Windows Server 2016 in DOMAIN_B?

  Details:
  My desktop machine is running Windows 7 Enterprise in domain somedomain.mycompany.com.au.
  Windows 7 can't install SQL Server 2016+.
  We are upgrading to SQL Server 2016 in 6 - 9 months or so.
  I want to learn new features of SQL Server 2016 now, and potentially start development using those new features to "be ahead of the game" when we have SS 2016 in production.
  I have obtained a Windows Server 2016 license to support this activity.

  To that end, I have installed Windows Server 2016 in Virtualbox with machine name WINSRV2016.  That VM is a domain controller, with Active Directory, with a local domain of winsrv.local.  I have configured Bridged Networking, with static IP address, and my corporate DNS server as the DNS server.  The easiest thing was for me to disable IPv6 on the network adapter (I need to read up on configuring static IPV6 addresses).  I get Netbios name resolution (i.e. WINSRV2016) on both my local (running VB) and other machines (not hosting the VM).  I don't have FQDN resolution yet; ping WINSRV2016.some.domain fails.  I don't have access to my corporate AD or DNS. 

  I'm thinking I need to setup a one-way domain trust relationship from somedomain.mycompany.com.au to winsrv.local (???).

  My goal is to launch the VM, and have me on my local machine (running Virtualbox), and select colleagues from their machines, be able to use their local clients (eg. SSMS) to connect to this VM and SQL Server, and use Windows Authentication from their corporate accounts.  IOW, SOMEDOMAIN\MYACCOUNT can use Windows Authentication to connect to WINSRV2016, in the WINSRV.local domain, running SQL Server 2016 & 2017.

  In SSMS, I want to be able to connect using the Database Engine, Analysis Services, Integration Services, and Reporting Services.  Some of these only allow Windows Authentication.

  I could setup remote access, port forwarding, plus RDP access, and we could all RDP into the VM and do everything local to the VM, but that is not my preferred approach.

  Any ideas more than welcome...

  Thanks!...