Vendor troubles..
-
@WrCombs said in Vendor troubles..:
I asked them how I'm supposed to troubleshoot when they take away my layer 3 troubleshooting tools such as tracert (to show the hops = layer 3, right? )
That's correct, that's layer 3 (routing.) But what's expected to be the case is layer 4 (ports).
-
-
That took all day to post.
-
Wouldn't
test-netconnection destination:portwork as well for this, assuming @WrCombs is on windows? -
@DustinB3403 said in Vendor troubles..:
test-netconnection
Should, yes.
https://docs.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection?view=win10-ps
-
-
@scottalanmiller said in Vendor troubles..:
Good video.
The only addition I'd like to make is that you want to do ping first. Not primarily to see if its working or not, but to test DNS / hostname resolution.
If you ping abcxyz123.com and you can see that it's gets the IP address, you know that there you don't have a problem with the hostname resolution.
Next step after testing with (ping, telnet, wget etc) is to get serious and test tcpdump/wireshark. Basically recording network traffic to analyze what happens.
BTW, on windows telnet is not enabled/installed by default.
-
@Pete-S said in Vendor troubles..:
BTW, on windows telnet is not enabled/installed by default.
Hey I knew that one! lol I ran into that in the past, I just didn't know what telnet was used for.
-
@WrCombs said in Vendor troubles..:
@Pete-S said in Vendor troubles..:
BTW, on windows telnet is not enabled/installed by default.
Hey I knew that one! lol I ran into that in the past, I just didn't know what telnet was used for.
Sort of... everything, lol.
-
@scottalanmiller said in Vendor troubles..:
@WrCombs said in Vendor troubles..:
@Pete-S said in Vendor troubles..:
BTW, on windows telnet is not enabled/installed by default.
Hey I knew that one! lol I ran into that in the past, I just didn't know what telnet was used for.
Sort of... everything, lol.
well, I see that now, I watched the video then did my own research for it.
