Question about AD Server 2008 Course

[Johnneke]

Hey guys I'm in the process of doing the Train Signal course for Server 2008 Active Directory. I'm doing everything that is done in the course on my own VMWare workstation LAB. But I'm a bit stuck now.

First the NY site was created it has DC1, 2 & 3 at ip's: 192.168.5.2/192.168.5.3 & 192.168.5.5 and a member server at 192.168.5.4.

Now I'm at the video where the Chicago site and he assigns a subnet of 192.168.5.0/26 to the Chicago site, isnt this in conflict with what was done earlier? I also noticed the instructor had given his DC1 in Chicago the ip 192.168.5.4 which overlaps a server in NY.

Now I dont know much about WAN links yet or better how to build a child domain at another geographical location but I would think the subnet for NY should be 192.168.5.0/26 and then a subnet for Chicago at for instance 192.168.5.64/26 and then DC1 in chicago at 192.168.5.65.

Am I missing something here? If anyone can give more directions on how I can build this on 1 pc running vmware workstation that would be great.

Well as opposed to how Coach Culbertson did in his video I gave my Chicago site the subnet 192.168.5.64/26 and the server the ip 192.168.5.65. It got detected during dcpromo as being part of the Chicago site. changing the ip to the 192.168.5.0/26 range detected it as being part of the ny site since I set that subnet for the ny site. Hopefully someone can clarify for my what is wrong or right :)

[Biggles77]

Haven't seen the video but I would be inclined to check the subnet mask. I think you have either made a typo or misread the mask as I don't think it would be /26.

[Johnneke]

http://www.speedweb.be/26subnet.jpg

As you can see I didnt misread it, this is a screenshot from the actual course

[Johnneke]

Also a picture of the setting of the initial domain controllers on the New York site so you can see where my conflict comes from:

http://www.speedweb.be/firstdcs.jpg

[Biggles77]

As per your attachment, you obviously read it correctly.
As per my attachment you have obviously understood the subneting, as .65 for Chicago looks correct.

I now have only one thing to say:

COACH!! (That should get his attention)

4

[Johnneke]

As per my attachment you have obviously understood the subneting, as .65 for Chicago looks correct.


Haha your right there, subnetting is my strongsuit :D I even had to teach it to my class instead of the classroom teacher (I'm a student).

Courtesy of the great Train Signal TCP/IP Essentials :D

[gabi_cavaller]

Good spotting, I have just gone through this myself and did not pick it up.

:(

[Coach]

Ok, I'm man enough to step up and take a hit on this. I'm going to review the video and see where I might need to make edits. Thanks for pointing this out, you're absolutely right about the TCP/IP aspect, and I'll go see what's up and make it right.

[Biggles77]

Really good find John. I bet it is going to be a tiny typo somewhere in all the Virtuals. (God helps us when IPv6 becomes mandatory.)

Coach will find the answer even if it does spin, spin, spin a bit.......but in the meantime, it's back to the Regular Scheduled same Bat Time, same Bat Channel. :D

Quick response time Coach, less than 24 hours. Bloody impressive. :thumbsup: (That's K One W One speak)

[Biggles77]

Video 16, 15mins 33 secs, NA-DC1-2k8, IP 192.168.5.4

This server was a member server (same IP ) setup earlier as per 3rd line of John's first post. This Member Server is now being DCPromo to being the Chicago DC and it is on the same subnet as the NY DCs. (Don't forget the NA-DC1-2K8 is the North America (NA) DC that is located in Chicago)

Here is now the ex Member Server that was created with the NY-DCs. NY Member Server no longer exists as it is now the NA-DC1-2K8.na.global ete etc in Chicago. It is also on the same subnet as NY since it is going to be replicating the AD with them.

5

So, no overlapping IPs with the different locations. 1.06am and Mr Sandman is calling. I hope that makes sense John and as I said a very small typo about no mention of using the .4 Member Server (in NY) becoming the the NA-DC1 in Chicago.

Coach, you owe me a Regular Scheduled Channel changer. :eek:

[ali_manzoor]

this video will be change ?????????

[Biggles77]

this video will be change ?????????
What do you mean?

[ali_manzoor]

What do you mean?

I mean any Error in this video because i have not see yet

[Biggles77]

Form the little I have seen, there is no error. There may have been a small misunderstanding between what Coach has said and the way John has interpreted it.

Gabi has gone through this Lab and all the settings seem to have worked correctly for him/her (sorry).

The quality control on these Labs is very rigorious so the chance of an error is extremely small. As I mentioned in an earlier post is was most likely a minor typo. I now believe this is a minor misunderstanding (like a typo) in what Coach has said and John has heard.

I believe reviewing Video 16 with my input in mind should clear up the initial confusion over the apparent confliction IP Addresses of the 2 Servers (NY-DC & the member Server that was going to be DCPromoed to the NA-DC Server)
John could you post back with how this now works with the new information/interpreration supplied (by me). Thanks.

Disclaimer:
I would like to add that I am NOT a paid or unpaid employee of Train Signal so my opinion is mine only and does not reflect any from Train Signal or its Management.

[Johnneke]

It's not a error that makes anything not working, but it just is something that people who have a good understanding of subnetting will have trouble with. I dont think there is a typo or anything misunderstood. Even if you are moving a server from 1 site to another, your not going to leave that server on it's original ip.

But to clear up, the way it was explained might lead to someone understanding the adding of subnets in sites & services wrongly but I highly doubt that this is anything that will pass by on the exam

If anyone who has been watching this or will be watching this you just have to keep in miind that when you assign a subnet to a site to make sure that you use different subnets for each site. And place your servers on each site in the correct subnet you assigned to it.

So my point didn't have anything to do with the member server having 192.168.5.4 as ip which was later promoted to dc in the chicago site. My point is that if you give your initial servers in a site called new york ip's like 192.168.5.1/192.168.5.2/... then assign a subnet that includes these ip's to the site new york and assign another subnet to chicago. When trying all this in a lab it's simple to use the following subnets (and keep the netmasks for each pc 255.255.255.0, this way they can all communicate without needing routers and whatnot in your lab)

192.168.5.0/26 ->
Valid IP's 192.168.5.1 till 192.168.5.62
Network ID 192.168.5.0
Broadcast 192.168.5.63

192.168.5.64/26 ->
Valid IP's 192.168.5.65 till 192.168.5.126
Network ID 192.168.5.64
Broadcast 192.168.5.127

192.168.5.128/26 ->
Valid IP's 192.168.5.129 till 192.168.5.190
Network ID 192.168.5.128
Broadcast 192.168.5.191

192.168.5.192/26 ->
Valid IP's 192.168.5.193 till 192.168.5.254
Network ID 192.168.5.192
Broadcast 192.168.5.255

[gabi_cavaller]

Gabi is a he :) ......... Gabriel - blasted parents!

Nice Disclaimer Biggles :p

Not quite sure why you would do a /26 instead of a /24?

For instance, if you had three sites, with say a maximum of 200 nodes, I pressume this would be ok ?

10.1.10.1/24
10.1.20.1/24
10.1.30.1/24

Sites in different locations, VPN, all subnets the same, thus communication being ok in a life environment and lowish traffic,

:)