If you haven't already seen it:

Youtube Video

Man all y'all are lucky. I work at a college, lol. They making faculty staff and students do remote learning!

I really hoping to be at home soon. I have shit to do. Baseboards and doors need painted, cabinets need stained, I have 5 weeks until I take the Networking + test. I could really just use the extra time home in general.

Playstation had a sale in the store and I was able to buy Tomb Raider Definitive Edition (better than Shadow of the Tomb Raider somehow), Rise of the Tomb Raider, HUE, Dead Island, Dead Island Riptide, and Dead Island Retro Revenge (not a great game) for around $30!

It's only a matter of time before they send us all home for a while, so I got some mostly good games to play.

@Dashrender Ah, so in the future I need to pay more attention to the /26 part (which they did not notate here), but would have been implied had I known what I was doing prior to reading it.

I wasn't getting what I needed from my lesson and turned to google to grasp a better understanding of Subnetting. I'm reading this article : https://support.microsoft.com/en-us/help/164015/understanding-tcp-ip-addressing-and-subnetting-basics

About halfway down the page under Subnetting it explains that "The subnet mask 255.255.255.192 gives you four networks of 62 hosts each. This works because in binary notation, 255.255.255.192 is the same as 1111111.11111111.1111111.11000000. The first two digits of the last octet become network addresses, so you get the additional networks 00000000 (0), 01000000 (64), 10000000 (128) and 11000000 (192)....Using a subnet mask of 255.255.255.192, your 192.168.123.0 network then becomes the four networks 192.168.123.0, 192.168.123.64, 192.168.123.128 and 192.168.123.192. These four networks would have as valid host addresses:

192.168.123.1-62
192.168.123.65-126
192.168.123.129-190
192.168.123.193-254

Remember, again, that binary host addresses with all ones or all zeros are invalid, so you cannot use addresses with the last octet of 0, 63, 64, 127, 128, 191, 192, or 255."

---

What I don't understand is why they are excluding 63, 127, and 191? I've converted those to binary and they aren't all 1's or 0's

63=00111111
127=01111111
191=10111111

In fact, 64, 128, and 192 aren't all 1's or 0's either, are they incorrectly explaining leaving room for a switch or DC or is there another reason to exclude those numbers?

Edit: my binary conversions needed work, but I fixed that

Studying for my Networking + certificate with flash cards I made from the lessons. About 5/22 lessons through, with 139 flash cards made so far. Also drawing Fiber Optic connector types in Adobe Illustrator, and adding them to my desktop wallpaper so I have to see them constantly. Anything helps. Shooting for 8 weeks from now for the test.

@scottalanmiller said in Group Policy points to wrong DC:

It really only boiled down to I don't want to wait 15 minutes (the minimum replication between DC's) for a GPO to apply.

Then time to go to a single DC

But GPOs aren't meant to work this way, really. If you want faster results, GPO is the wrong tool.

What alternative to Group Policy do you recommend?

@Dashrender said in Group Policy points to wrong DC:

@G-I-Jones said in Group Policy points to wrong DC:

@Dashrender said in Group Policy points to wrong DC:

@G-I-Jones said in Group Policy points to wrong DC:

e secondary to another site, then it would default to the one I wanted it to, but I got two things wrong: first and most i

As I recall - it's either which ever DC is provided by DNS when a query for a DC is given, OR in the case of broadcast - whomever answers first.

Yea I think it might be the latter, as the DNS for my machine's NIC is pointing to the primary DC, but set replies with the secondary.

you're misunderstanding DNS. The query the client machine is making is - give me the IP of a DC - ANY DC, and DNS is likely following a round robin affect and just handing out the IP of the next one that hasn't been handed out.
Let's assume there are 2 DCs.
ClientA queries for any DC - answer - DC1
ClientB queries for any DC - answer - DC2
ClientC queries for any DC - answer - DC1
etc

Ah, I see what you are saying here. Goes in with the idea that these are a pool. Appreciate that point of view, I hadn't thought of that just yet.

@Dashrender said in Group Policy points to wrong DC:

@G-I-Jones said in Group Policy points to wrong DC:

e secondary to another site, then it would default to the one I wanted it to, but I got two things wrong: first and most i

As I recall - it's either which ever DC is provided by DNS when a query for a DC is given, OR in the case of broadcast - whomever answers first.

Yea I think it might be the latter, as the DNS for my machine's NIC is pointing to the primary DC, but set replies with the secondary.

@scottalanmiller said in Group Policy points to wrong DC:

@G-I-Jones said in Group Policy points to wrong DC:

Your client devices will use the DC that is in their same site, and if there's more than one DC in it's site, the best DC will be chosen... which leads to the second point.

I guess what I was playing at was how I could trick the process of "the best DC will be chosen".

So if this is just an exercise in learning. Great. If not, let's back up. Why do you want to do this? What makes you feel one is better than another?

It really only boiled down to I don't want to wait 15 minutes (the minimum replication between DC's) for a GPO to apply.