I am developing a client server database with Access 2007 connecting to a SQL Server 2008 r2. This is a new development. On my development machine I have VMware desktop 9.2. I am trying to mimic my clients network while I do my development. I created a virtualized Windows 2008 R2 server which installed fine. It is fully patched. I installed SQL Server 2008 r2 on the server with SA security. I was able to create my database with no problem. I made the Server a domain server. I created a second virtualized machine with Windows 2007 and Office 2007 to use as the workstation to develop the front end. I joined the workstation to the domain fine. I can access the server and create a directory on it. I created a user account on the database for myself, made myself owner and gave myself permissions.
On the workstation, from the Computer, I can click on the TESTSERVER and see three directories. netlogon Share, Sysvol share, and mssqlserver Share. I can open the netlogin and sysvol shares fine and create files on the server. When I try to open the mssqlserver Share it says "Windows cannot access \\Testserver\mssqlserver." The database I am trying to connect to is Kennedy1.
I cannot establish an ODBC connection either. On the workstation I created a User DSN, Select SQL Authentication, enter my userID and Password that I assigned on the SQL Server but it says:
Connection failed:
SQL State: '01000'
SQL Server error: 10060
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection Failed
SQLState: '08001'
SQL Server error 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not exist or access denied.
On the SQL Server Event Properties I see Event 4013 with the following message.
The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
I can't really tell from all of this what the problem actually is.
I have a lot of development experience but little network setup or troubleshooting.
THIS IS AN ISOLATED DEVELOPMENT MACHINE ONLY. NO PRODUCTION FROM THIS MACHINE.
So there is one server and one workstation, that's it. I can't solve this last step to connect to the SQL Server. I am not sure what else to tell you. Please ask questions.
Thanks
Fred