no port 80 on window7 with netstat -a -n -o

Ask Question Forum:

Model Library:2025-02-08 Updated:A.I. model is online for auto reply question page

Show

ASK RECENT

no port 80 on window7 with netstat -a -n -o

Asked by duncanb7

at 2024-02-27 01:45:45

Point:500 Replies:7 POST_ID:828889USER_ID:11059

Topic:

Windows 7;Hypertext Transfer Protocol (HTTP);Networking Protocols

Question-1
I restart my Window 7 computer , and type command netstat -a -n -o
to display all network port but I could NOT find any port about 80 (http port)
Why ? and I go to try my other XP computer, it shows the 0.0.0 0:80 on
Local Address from netstat -a -n -o command output.

Question-2
When I open chrome browser on my window 7 computer, and
go to check netstat -a -n -o command, and find the following output
Yes, of course since issue on question-1, I could NOT find any port of 80
But I think about how can I go to google.com default page on my chrome
browser without port 80 listen? And I check the following output, I found
something like
TCP 219.77.4.127:49708 74.125.128.120:443 ESTABLISHED 448

The 219.77.4.127 is my ISP address after check ipconfig command and 74.125.128.120:443 is google.com 's https site.

Why the port for http on my local address is 49708 instead of 80 ?

Or some hidden software installed on my computer to switch port 80 to 49708
such as http proxy ? But I never use any http proxy on my this window 7 computer .

Please advise
Duncan

TCP    0.0.0.0:135            0.0.0.0:0              LISTENING       900  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING       4  TCP    0.0.0.0:554            0.0.0.0:0              LISTENING       1032  TCP    0.0.0.0:2869           0.0.0.0:0              LISTENING       4  TCP    0.0.0.0:10243          0.0.0.0:0              LISTENING       4  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING       580  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING       964  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING       500  TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING       628  TCP    0.0.0.0:49156          0.0.0.0:0              LISTENING       652  TCP    127.0.0.1:2869         127.0.0.1:49703        TIME_WAIT       0  TCP    127.0.0.1:2869         127.0.0.1:49704        ESTABLISHED     4  TCP    127.0.0.1:5354         0.0.0.0:0              LISTENING       1620  TCP    127.0.0.1:49157        0.0.0.0:0              LISTENING       1928  TCP    127.0.0.1:49169        0.0.0.0:0              LISTENING       984  TCP    127.0.0.1:49704        127.0.0.1:2869         ESTABLISHED     1032  TCP    169.254.202.6:139      0.0.0.0:0              LISTENING       4  TCP    219.77.4.127:49706     173.194.127.244:443    TIME_WAIT       0  TCP    219.77.4.127:49708     74.125.128.120:443     ESTABLISHED     448  TCP    219.77.4.127:49709     74.125.128.120:443     ESTABLISHED     448  TCP    219.77.4.127:49710     74.125.128.94:443      ESTABLISHED     448  TCP    [::]:135               [::]:0                 LISTENING       900  TCP    [::]:445               [::]:0                 LISTENING       4  TCP    [::]:554               [::]:0                 LISTENING       1032  TCP    [::]:2869              [::]:0                 LISTENING       4  TCP    [::]:10243             [::]:0                 LISTENING       4  TCP    [::]:49152             [::]:0                 LISTENING       580  TCP    [::]:49153             [::]:0                 LISTENING       964  TCP    [::]:49154             [::]:0                 LISTENING       500  TCP    [::]:49155             [::]:0                 LISTENING       628  TCP    [::]:49156             [::]:0                 LISTENING       652  TCP    [::1]:49158            [::]:0                 LISTENING       1928  UDP    0.0.0.0:500            *:*                                    500  UDP    0.0.0.0:4500           *:*                                    500  UDP    0.0.0.0:5004           *:*                                    1032  UDP    0.0.0.0:5005           *:*                                    1032  UDP    0.0.0.0:5355           *:*                                    1228  UDP    0.0.0.0:62511          *:*                                    1620  UDP    127.0.0.1:1900         *:*                                    4652  UDP    127.0.0.1:56461        *:*                                    3644  UDP    127.0.0.1:59562        *:*                                    4652  UDP    169.254.202.6:137      *:*                                    4  UDP    169.254.202.6:138      *:*                                    4  UDP    169.254.202.6:1900     *:*                                    4652  UDP    169.254.202.6:5353     *:*                                    1620  UDP    169.254.202.6:59561    *:*                                    4652  UDP    219.77.4.127:1900      *:*                                    4652  UDP    219.77.4.127:59560     *:*                                    4652  UDP    [::]:500               *:*                                    500  UDP    [::]:4500              *:*                                    500  UDP    [::]:5004              *:*                                    1032  UDP    [::]:5005              *:*                                    1032  UDP    [::]:5355              *:*                                    1228  UDP    [::]:62512             *:*                                    1620  UDP    [::1]:1900             *:*                                    4652  UDP    [::1]:59559            *:*                                    4652  UDP    [fe80::94a8:db5:2904:ca06%12]:1900  *:*                                    4652  UDP    [fe80::94a8:db5:2904:ca06%12]:5353  *:*                                    1620  UDP    [fe80::94a8:db5:2904:ca06%12]:59558  *:*                                    4652

1:2:3:4:5:6:7:8:9:10:11:12:13:14:15:16:17:18:19:20:21:22:23:24:25:26:27:28:29:30:31:32:33:34:35:36:37:38:39:40:41:42:43:44:45:46:47:48:49:50:51:52:53:54:55:56:57:58:59:

Select All Code

Author: duncanb7 replied at 2024-02-27 03:01:43

Totally agree your comment. Thanks for your reply,

For my memo only:
-the issue in this thread is NOT related to Window 7 & or XP system
-Why my linux server can handle many http accesses with just only TCP/IP http port 80,
that is because apache linux server is multi-process that
mentioned on this link , http://en.wikipedia.org/wiki/Apache_HTTP_Server

Duncan

Author: duncanb7 replied at 2024-02-27 03:00:35

Now better understand after your comment and I can verfiy it from that
I go to check the client and server communication port on $_SERVER variable from
php code between my linux server and my window 7 computer

The php code report $_SERVER['REMOTE_PORT'] and $_SERVER['REMOTE_ADDR'] that is
matched to netstat command output on my window 7 computer.

In other words, when I try http://mylinuxsite.com/server.php on chrome browser , it will
go to my server port 80 since http or no http typing will be interpreted as access server TCP/IP port 80 on browser and https for 443.

The connection is between server 80 port and my computer dynamic port when
typing http on browser.

Why it use dynamic TCP port for browser that is I believe because it can use it for multi-thread tasking process so that we can create many instances or type browsers http accesses at the same time wihtout waiting

Duncan

Accepted Solution

Expert: Miftaul replied at 2024-02-27 02:39:10

250 points EXCELLENT

Google chrome browser uses your local dynamic port to establish a TCP session with google.com.

TCP session is established between your local port and the remote server port. Here the local port will be Dynamic Ports (49152-65535) and the remote server port is 80 for http webpages and 443 for https.

The remote server ports are actually well known port (0 - 1023), it the service that you are accessing will determine which remote port the session needs to be established.

Author: duncanb7 replied at 2024-02-27 02:24:58

So you mean google chrome browser don't use port 80, Right ?

And why chrome browser USE dynamic ports instead of static port ?

Expert: Miftaul replied at 2024-02-27 02:18:08

Yes, your computers dynamic port will establish a TCP session with the web-servers well known port (0-1023).

Port 80 is registered for http service and 443 for https. The device that providing these services will open these ports. and the host computers accessing the services will have their dynamic ports open.

Here is the list of ports - Link

Author: duncanb7 replied at 2024-02-27 02:06:41

In other words, google chrome browser will open TCP session to use dynamic port instead of 80. So the http TCP/IP is not just working on http port 80 only but also other port
such as 49000 to 66500. Right ? Why he is doing that way for dynamic port, for security ?

Assisted Solution

Expert: Miftaul replied at 2024-02-27 01:57:36

250 points EXCELLENT

When we are opening www.google.com your computer opens a TCP session on its local dynamic port with the web servers port 80 ()for http) and 443(for https).

The only time you might see port 80 open on your local computer is when your computer is providing some sort of http services.

新聞財經娛樂♬資訊 News Economy

About Us|Service|Pricing

Stock Index全球即時指數期貨:

&nbps;

News即時新聞:↓

News即時新聞:↑

On Balance Volume (OBV):

Youtube Video♬ Sharing by members:↓

Youtube Video♬ Sharing by members:↑

Ask Question Forum:

no port 80 on window7 with netstat -a -n -o

Your Information

Members/Profolio