2020-11-30 18:18:46 +0000 | received badge | ● Notable Question (source) |
2020-11-30 18:18:46 +0000 | received badge | ● Famous Question (source) |
2020-11-30 18:18:46 +0000 | received badge | ● Popular Question (source) |
2019-06-23 06:25:48 +0000 | answered a question | Identifying source & destination port #'s Jaap First of all, thank you for cleaning up my horrible entry of my first question to wireshark. I will become better a |
2019-06-23 06:25:48 +0000 | received badge | ● Rapid Responder |
2019-06-23 06:23:23 +0000 | marked best answer | Identifying source & destination port #'s New to wireshark. Not wanting anyone to spend too much time in answering this question. Trying to be polite. If you want to reference me to a specific article or example; that would be great . in conjunction with studying for ccna ... was looking for some help with the following. Example: If I typed in www.bing.com into my web browser ... and I was successful in accessing the site. And then I performed a ping to www.bing.com / which was successfull. I see from the ping response that I can determine [www.bing.com]'s Destination IP address = 2620:1ec:c11::200 . If I perform for example, a powershell session and perform a 'netstat' command to view my pc's network activity : I can see relatively / easily that the Destination Port # 443 / which is [ default ] for https. But, due to much information that is populated from the 'netstat' search, i cannot figure my pc's exact [ source port # ] for my particular web request to: www.bing.com . Can a wireshark capture assist me with determining my pc's specific [ source port # ] that was used during the web search ? I know my pc's ip address. I know how to set a TCP protocol filter on wireshark. Just not too savy , for example ; in finding a specific 'source-port #' . Could anyone possibly assist ? Thank you ! secrseel |
2019-06-23 06:23:23 +0000 | received badge | ● Scholar (source) |
2019-06-23 05:27:06 +0000 | asked a question | Identifying source & destination port #'s Identifying source & destination port #'s new to wireshark. not wanting anyone to spend too much time in answering |