[bobm]

I currently have an NT4 domain with domain name 'mydomain'. I have also installed SBS 2003 R2 with a different domain name 'newdomain.local'. The SBS server is not configured as a DC and AD is not active. I access an mission critical database, running on SQL on the SBS R2 server via the IP address from the NT4 domain. I would now like to install a Windows 2008 server as a DC with Active Directory with a different domain name, and migrate the NT4 users. Would I still be able to access the SBS 2003 R2 (with the the SQL DB) on the 'newdomain.local' domain.

This post has been edited by bobm: 19 November 2009 - 02:57 PM

[fdv]

I currently have an NT4 domain with domain name 'mydomain'. I have also installed SBS 2003 R2 with a different domain name 'newdoain.local'. The SBS server is not configured as a DC and AD iis not active. I access an mission critical databes, running on SQL on the SBS server via the IP address.
I also have a 2003 Standard Edition server (NOT a DC and No AD), purely running as a webserver. I would now like to install a second Windows 2003 server as a DC with AD and migrate the NT4 users. Would I still be able to access the SBS server and the SQL DB.

So, before
NT4 Server = mydomain (presumably a domain controller)
SBS 2003 = newdomain.local, not a DC, AD not running, runs databases
Standard 2003#1 = unspecified domain, not a DC, AD not running, runs IIS

After
NT4 Server = mydomain, taken offline
(new) Standard 2003#2 = mydomain.local, domain controller, AD running
(unchanged) SBS 2003 = newdomain.local, not a DC, AD not running, runs databases
(unchanged) Standard 2003#1 = unspecified domain, not a DC, AD not running, runs IIS

I do not, on the face of it, see a problem with the (new) mydomain.local accessing any kind of data on newdomain.local, not a DC and running databases, via its IP address.