Having trouble adding a second server to domain?

MouseUK

Hi,

Only starting out so its probably something simple :S

Created one DC (Server01) which has the domain smallbusiness.local (keeping it simple).
Created a second Server (Server02 - I know, origional) which currently is on a work group as when ever I try to add it to the same domain it errors.

I'm using VMware Workstation,
There on the same Vnet (virtual network),

Both servers can ping each other on there IP's and Server02 can ping Server01.smallbusiness.local.

The error I get from Server 02 is:
"
Note: This information is intended for a network administrator. If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\WINDOWS\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain smallbusiness.local:

The error was: "This operation returned because the timeout period expired."
(error code 0x000005B4 ERROR_TIMEOUT)

The query was for the SRV record for _ldap._tcp.dc._msdcs.smallbusiness.local

The DNS servers used by this computer for name resolution are not responding. This computer is configured to use DNS servers with the following IP addresses:

192.168.56.133

Verify that this computer is connected to the network, that these are the correct DNS server IP addresses, and that at least one of the DNS servers is running.

For more information on how to correct this problem, click Help.
"

Where 192.168.56.133 is Server01's IP (which also is a DNS server), Tried it using 192.168.56.2 (which VMware seems to pick out of mid air) which also doesn't work.

Server 01's current ipconfig:

"
Windows IP Configuration

Host Name . . . . . . . . . . . . : Server01
Primary Dns Suffix . . . . . . . : smallbusiness.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : smallbusiness.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-0C-29-3A-40-77
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.56.133
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.56.2
DNS Servers . . . . . . . . . . . : 192.168.56.2
"

Server02:

"
Windows IP Configuration

Host Name . . . . . . . . . . . . : Server02
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : localdomain

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : localdomain
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-0C-29-A9-1F-7C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.56.134
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.56.2
DHCP Server . . . . . . . . . . . : 192.168.56.254
DNS Servers . . . . . . . . . . . : 192.168.56.133
Primary WINS Server . . . . . . . : 192.168.56.2
Lease Obtained. . . . . . . . . . : Tuesday, September 29, 2009 7:17:56 AM
Lease Expires . . . . . . . . . . : Tuesday, September 29, 2009 7:47:56 AM
"

Any help would be apreciated

I have the Windows Server 2003 Microsoft Training Kit, I think it pursumes u already know how to link domains together

I've since ordered one of the books mentioned on this forum and also another one advised by someone at work lol So hopefully I'll get there

Thanks for reading,
Sorry for the woffle....

Mouse

Essendon

- Set server1 to use itself as the DNS server. Give it a static IP address.
- Set server2 to use server1 as the DNS server. Give it a static IP address too.
- Disable the DHCP and NAT service that VMware offers, it unnecessarily complicates things.
- Ensure server1 and server2 are on the same subnet ( eg. use these addresses 10.10.10.10 and 10.10.10.11.)
- I'd recommend you create new VM's. Your server1 could have some issues which can make life hard since your just starting out.
- Let us know how you went.