ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Vendor troubles..

    Water Closet
    wrcombs firewalls
    5
    13
    1.0k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller @WrCombs
      last edited by

      @WrCombs said in Vendor troubles..:

      How the hell am I supposed to verify it's actually leaving the site then ?

      telnet

      This is always the case. You can't test with different protocols for others. E.g. you can use a test for X to see if Y is allowed. ICMP (Ping and Traceroute, which are really both Ping) is a different protocol stack than TCP/IP. So while it's a useful tool to test some things, they are correct that it tells you nothing about what you are trying to test.

      Ping is used to test routing, not firewalls. You are testing a firewall, not routing.

      1 Reply Last reply Reply Quote 2
      • scottalanmillerS
        scottalanmiller
        last edited by

        If CC's use HTTPS from a machine to destination X:Y (where X is IP and Y is port), then to test you either need a complicated testing harness or just use telnet, which is the standard tool we all use. From the machine in question...

        telnet X Y
        
        1 Reply Last reply Reply Quote 1
        • scottalanmillerS
          scottalanmiller @WrCombs
          last edited by

          @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).

          1 Reply Last reply Reply Quote 1
          • scottalanmillerS
            scottalanmiller
            last edited by

            Youtube Video

            1 1 Reply Last reply Reply Quote 3
            • scottalanmillerS
              scottalanmiller
              last edited by

              That took all day to post.

              1 Reply Last reply Reply Quote 0
              • DustinB3403D
                DustinB3403
                last edited by

                Wouldn't test-netconnection destination:port work as well for this, assuming @WrCombs is on windows?

                scottalanmillerS 1 Reply Last reply Reply Quote 2
                • scottalanmillerS
                  scottalanmiller @DustinB3403
                  last edited by

                  @DustinB3403 said in Vendor troubles..:

                  test-netconnection

                  Should, yes.

                  https://docs.microsoft.com/en-us/powershell/module/nettcpip/test-netconnection?view=win10-ps

                  1 Reply Last reply Reply Quote 0
                  • PhlipElderP
                    PhlipElder @WrCombs
                    last edited by

                    @WrCombs

                    WFetch
                    https://support.microsoft.com/en-us/help/284285/how-to-use-wfetch-exe-to-troubleshoot-http-connections

                    1 Reply Last reply Reply Quote 0
                    • 1
                      1337 @scottalanmiller
                      last edited by

                      @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.

                      WrCombsW 1 Reply Last reply Reply Quote 1
                      • WrCombsW
                        WrCombs @1337
                        last edited by

                        @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.

                        scottalanmillerS 1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller @WrCombs
                          last edited by

                          @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.

                          WrCombsW 1 Reply Last reply Reply Quote 0
                          • WrCombsW
                            WrCombs @scottalanmiller
                            last edited by

                            @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.

                            1 Reply Last reply Reply Quote 1
                            • 1 / 1
                            • First post
                              Last post