 | 1 | initial version |
Few things.
The browser opens one (or more) TCP connections to the bing server to get the HTTP page information, but then closes them once the pages are received. Therefore you won't see them using netstat because they would be long gone before you can look.
Wireshark on the other hand captures the network traffic as it happens. So it can show you the TCP packets involved and therefore the port numbers involved in these connections. Find the TCP packets with the correct IP addresses (yours and bing's) and then look at the TCP layer details. It shows you the port number at bing's end (443) and the port number at your end.
