VMware Communities
MouseUK
Contributor
Contributor

Adding 2 Servers into a single Domain on VMWare Workshop?

HI,

I'm using VMWare Workshop in an attempt to reinforce some of the concepts I've been reading through for one of the Microsoft Exams (70-290),

I managed to setup a 2003 Windows Server in VMware with no issues (called Server01), then give it the role of a domain controler with the active directory Domain name of "contoso.com",

Then I setup another 2003 server (called Serve01) on the same VNet3 and that where my problems started...

For some reason I can't link them to the same domain? heck they have the same subnet, diffrent ip's (Server01: 192.168.1.230 and Server02: 192.168.1.229) both with the same default gateway?

Not sure whats wrong and why they can't see each other?

Any help would be apreciated Smiley Happy

Thanks

MouseUK

0 Kudos
12 Replies
TobiasKracht
Expert
Expert

What kind of mistake?

StarWind Software R&D

StarWind Software R&D http://www.starwindsoftware.com
0 Kudos
MouseUK
Contributor
Contributor

"What kind of mistake?"

I want to add both servers to a domain,

1st sever is setup with a domain "consto.com" with activy directory installed,

the 2nd server can't seem to see, connect, to the 1st. The 1st can't see the 2nd server either?

2nd server is setup as a workgroup at present, because every time I try and set it up to link ot the same domain it errors?

*Not at home at the moment so can't copy and paste the error...

Any ideas?

0 Kudos
TobiasKracht
Expert
Expert

You mean there in network connection between servers?

StarWind Software R&D

StarWind Software R&D http://www.starwindsoftware.com
0 Kudos
MouseUK
Contributor
Contributor

Server01 and Server02 can't ping each other, there both on the same vertual network but can't see each other.

Not sure how to fix this?

0 Kudos
prakashraj
Expert
Expert

Hi,

Can you provide HOST ip details?

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!

Prakash

If you found this information useful, please consider awarding points for "Correct" or "Helpful". Thanks!!!
0 Kudos
TobiasKracht
Expert
Expert

OK, I see now that you mean that it`s network problem of VmWare and not MS. Are they bridged? As I see must be. Can VMs ping the host?

StarWind Software R&D

StarWind Software R&D http://www.starwindsoftware.com
0 Kudos
louyo
Virtuoso
Virtuoso

>>Not sure whats wrong and why they can't see each other?

1. Do NOT use valid domain names belonging to others if your VM's are connected to the Internet. Contoso.com is a valid domain at Microsoft (it resolves to the same address as microsoft.com, 207.46.232.182). Most people use a .local ending domain name (lous-stuff.local) which avoids any conflicts (except for Mac's, they don't like .local).

2. When you say they "can't see each other" what exactly are you doing? Can they ping each other by IP address? By name? What are you using for DNS server settings?

3. Post the results of ipconfig/all for both guests and the host.

4. Is DNS server properly configured on both DC's? Check with nslookup.

Lou

MouseUK
Contributor
Contributor

Thank You Louyo for a VERY helpful answer Smiley Happy

1 - I was following the microsoft training guide that advised using Contoso.com, but that maybe causing part of the issue Smiley Happy So I will try and use.local and see where that gets me Smiley Wink

2 - I meant that they can't ping each other via ip, they should be on the same vertual netowrk, both got the same subnet mask and default gateway, but I'll have a play with 1, 3 and 4 when I get back form work and see what I can work out Smiley Happy (best way to learn is to play, brake things etc).

3 - Will do if I'm still struggling Smiley Happy Thanks for the help :smileygrin:

4 - Pass... Think so, but then again... this is the first MCP I'm looking at... Used to doing techsupport on ADSL stuff Smiley Wink

Thanks

Mike

0 Kudos
louyo
Virtuoso
Virtuoso

FWIIW: I have always found Mark Minasi's "Mastering Windows Server XXXX" to be more than helpful, if somewhat verbose.

Probably available from Amazon, used, for low price.

No, I don't have any affiliation with any of them Smiley Happy

Lou

0 Kudos
MouseUK
Contributor
Contributor

Hi again... (RDP for the win, I can play from work... Anyway)

"1. Do NOT use valid

domain names belonging to others if your VM's are connected to the

Internet. Contoso.com is a valid domain at Microsoft (it resolves to

the same address as microsoft.com, 207.46.232.182). Most people use a

.local ending domain name (lous-stuff.local) which avoids any conflicts

(except for Mac's, they don't like .local)."

Fair Do's, used "smallbusiness.local" for now...

"2. When you say they "can't see each other" what exactly are you doing?

Can they ping each other by IP address? By name? What are you using for

DNS server settings? "

I've tried lots of diffrent ways of doing it...

But currently I've set it upto DHCP, DNS auto configs to 192.168.56.2 and is pingable?

Server 01 is on 192.168.56.133 (Domain smallbusiness.local)

Server 02 is on 192.168.56.134

Both with a subnet mask of 255.255.255.0

They can both ping 192.168.56.2 but not each other or smallbusiness.local?

"3. Post the results of ipconfig/all for both guests and the host."

Server01

"

C:\Documents and Settings\Administrator>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Server01

Primary Dns Suffix . . . . . . . : smallbusiness.local

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : smallbusiness.local

localdomain

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : localdomain

Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection

Physical Address. . . . . . . . . : 00-0C-29-3A-40-77

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.56.133

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.56.2

DHCP Server . . . . . . . . . . . : 192.168.56.254

DNS Servers . . . . . . . . . . . : 192.168.56.2

Primary WINS Server . . . . . . . : 192.168.56.2

Lease Obtained. . . . . . . . . . : Thursday, September 24, 2009 2:27:00 PM

Lease Expires . . . . . . . . . . : Thursday, September 24, 2009 2:57:00 PM

"

Server02

"

C:\Documents and Settings\Administrator>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Server01

Primary Dns Suffix . . . . . . . : smallbusiness.local

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : smallbusiness.local

localdomain

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : localdomain

Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection

Physical Address. . . . . . . . . : 00-0C-29-3A-40-77

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.56.133

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.56.2

DHCP Server . . . . . . . . . . . : 192.168.56.254

DNS Servers . . . . . . . . . . . : 192.168.56.2

Primary WINS Server . . . . . . . : 192.168.56.2

Lease Obtained. . . . . . . . . . : Thursday, September 24, 2009 2:27:00 PM

Lease Expires . . . . . . . . . . : Thursday, September 24, 2009 2:57:00 PM

"

"4. Is DNS server properly configured on both DC's? Check with nslookup. "

Not got a clue, new to this... Pointers :smileygrin:

Thanks,

Mouse

0 Kudos
MouseUK
Contributor
Contributor

Thanks Smiley Happy

I'll look it up...

Right...

I managed to work out the issue with them not being able to ping each other... (helps if I enable IMCP on the windows firewall :P)...

So... one bit done... however Smiley Sad Still not working correctly...

When I try adding the domain to server 2 I get the following error:

"

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: "DNS name does not exist."

(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for ldap.tcp.dc._msdcs.smallbusiness.local

Common causes of this error include the following:

- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:

192.168.56.2

- One or more of the following zones do not include delegation to its child zone:

smallbusiness.local

local

. (the root zone)

For information about correcting this problem, click Help.

"

0 Kudos
louyo
Virtuoso
Virtuoso

Assuming that you can now ping all systems via IP address, off hand, it looks like your DNS server roles are missing or not fully/properly configured. Look in the event logs for DNS errors.

Off the top of my head.

1. Your servers should both have static addresses.

2. The first server, that was created in the domain (PDC, if you will), should be the main DNS server and have it's own IP address as the first static DNS server entry.

3. The second server should also have the DNS server role but should have the first server's IP address as its first entry in the static DNS server entry and its own address second (not sure the order is that important but I would enter them both, this can effect start up time ).

4. Both DNS servers need forward and reverse lookup zones defined. They should also be configured to allow dynamic updating.

5. You can use nslookup to test the DNS servers.

6. Although all this should work with your VM NIC's configured for Bridged, you could use NAT but still assign static addresses (outside the range of your DHCP server)

At the risk of sounding like "RTFM" (not my intent), you need to find some good examples of this process on line or in a good book. Smiley Happy

Good luck.

Lou

0 Kudos