Sunday, January 06, 2013 11:31 AM
How to configure the AD authentication when the database located on backend network?
The AD server that located on frontend network is cannot reached backend network because network was physically separated.
In this situation, If you were me, how to configure the AD on backend network so that the database could AD authentication login?
My software version environment is following;
OS:Window Server 2008 R2
Netwok:Common network that you think
Sunday, January 06, 2013 9:54 PM
I'm not sure what your question really is. Aer you asking how to setup a domain controller or domain services from a windows infrastructure perspective or are you asking how you can get SQL Server to use AD authentication when no domain controller is available?
If it's the second part, the answer is that you can't. If your network access does not allow you to talk to a DC then windows authentication is not possible except for local accounts.
If the quesiton is the first part, you may want to ask it in a windows forum as I believe you'll get more responses of better quality.
Monday, January 07, 2013 1:37 AM
Sorry for ambiguously question.
As you said that how I can get SQL Server to use AD authentication when no domain controller is available was more similar with my question.
As I could more exactly expression to my question, how could SQL Server to use AD authentication when two separated network by front-end network and back-end network, the domain controller that existed on front-end network is couldn't reached back-end network environment, and I hope to connect with the domain controller that exsited on fron-end netwok because it'll more easy management for servers.
Many people using the database located on back-end network environment. so that I've question that how could using it? just using without AD authentication and using SA login?
- Edited by David Hur Monday, January 07, 2013 1:37 AM
Monday, January 07, 2013 4:23 AM
I found the way to use AD authentication when back-end.
See the detailed infromation is following;
And I reconized this question proper to Windows Server forum.
Sorry that I confused it.