1
00:00:01,040 --> 00:00:02,100
In this demonstration,

2
00:00:02,100 --> 00:00:06,680
we'll work with hybrid cloud network troubleshooting in Windows Servers.

3
00:00:06,680 --> 00:00:08,640
Sound like a plan?

4
00:00:08,640 --> 00:00:12,680
Speaking of which, I'm on a Windows Server 2022 member server right now.

5
00:00:12,680 --> 00:00:15,230
Let me bring up an elevated PowerShell prompt,

6
00:00:15,230 --> 00:00:18,660
and we're just going to be using just native built‑in

7
00:00:18,660 --> 00:00:21,010
Windows Server Windows client PowerShell.

8
00:00:21,010 --> 00:00:24,440
I would strongly recommend that you run an update‑help

9
00:00:24,440 --> 00:00:26,230
so that you have local help files.

10
00:00:26,230 --> 00:00:27,200
Why do I say that?

11
00:00:27,200 --> 00:00:29,860
Well, when I teach people PowerShell basics,

12
00:00:29,860 --> 00:00:34,840
we talk about the big three commands those are Get‑Command,

13
00:00:34,840 --> 00:00:37,080
Get‑Help, and Get‑Member.

14
00:00:37,080 --> 00:00:40,030
That Get‑Help, in particular, is so useful.

15
00:00:40,030 --> 00:00:43,450
So what you can do is get‑help, pass it the name of a command,

16
00:00:43,450 --> 00:00:46,950
like how about that Resolve‑DnsName command that I mentioned,

17
00:00:46,950 --> 00:00:48,900
and just throw on Examples.

18
00:00:48,900 --> 00:00:52,230
Now PowerShell doesn't ship with online help by default,

19
00:00:52,230 --> 00:00:56,180
that's why it's important to run‑update help periodically.

20
00:00:56,180 --> 00:00:59,520
And it'll give us here, hopefully, several examples.

21
00:00:59,520 --> 00:01:03,870
And the way that the content developers at Microsoft work is

22
00:01:03,870 --> 00:01:07,200
they start with the most basic common use case,

23
00:01:07,200 --> 00:01:10,640
and then they gradually get more complicated.

24
00:01:10,640 --> 00:01:14,560
So it looks like at base, you're resolving a DnsName,

25
00:01:14,560 --> 00:01:18,450
passing in an FQDN, and it'll give you back an IP.

26
00:01:18,450 --> 00:01:23,960
So I can do a Resolve‑DnsName dc 1, that's my local domain controller,

27
00:01:23,960 --> 00:01:26,500
and I'll easily fetch the IP address.

28
00:01:26,500 --> 00:01:30,630
So we could use Resolve‑DnsName as a very quick and easy way

29
00:01:30,630 --> 00:01:33,390
to get the IP address of a remote host.

30
00:01:33,390 --> 00:01:39,740
Resolve‑DnsName, how about syr.edu, Syracuse University.

31
00:01:39,740 --> 00:01:41,540
I like to use that when I teach.

32
00:01:41,540 --> 00:01:44,540
I'm from Syracuse, New York, full disclosure.

33
00:01:44,540 --> 00:01:46,770
And I taught at SU for a while too,

34
00:01:46,770 --> 00:01:50,540
so I like to pick on it and use it in examples and so on.

35
00:01:50,540 --> 00:01:55,140
Note that you can do things like look for particular record types.

36
00:01:55,140 --> 00:01:59,830
We definitely are looking at a variant of nslookup here.

37
00:01:59,830 --> 00:02:02,030
That's really what we're talking about, all right?

38
00:02:02,030 --> 00:02:06,440
So that's that, and that actually can go through a number of different commands.

39
00:02:06,440 --> 00:02:10,400
Let's see, what are some other very common network troubleshooting?

40
00:02:10,400 --> 00:02:17,240
Why don't we do a get‑help for Test‑NetConnection, and again, we'll do Examples.

41
00:02:17,240 --> 00:02:20,190
Wow, that is really unfortunate.

42
00:02:20,190 --> 00:02:22,740
I don't see any examples here.

43
00:02:22,740 --> 00:02:23,860
I hate when that happens.

44
00:02:23,860 --> 00:02:25,800
Let me actually make a note of that.

45
00:02:25,800 --> 00:02:27,380
Something else you could try when you're

46
00:02:27,380 --> 00:02:31,180
troubleshooting this stuff is do a ‑online.

47
00:02:31,180 --> 00:02:34,570
The online version cannot be, I'll be darned.

48
00:02:34,570 --> 00:02:35,890
Wow, that's really weird.

49
00:02:35,890 --> 00:02:38,000
Okay. All right.