Windows 10: Port 8080 is occupied by file explorer

Discus and support Port 8080 is occupied by file explorer in Windows 10 Network and Sharing to solve the problem; My port 8080 is occupied by file explorer. It tries to connect from 127.0.0.1:5441 to 127.0.0.1:8080 so I can't use port 8080. I try to kill the... Discussion in 'Windows 10 Network and Sharing' started by mistymountain32, Nov 12, 2021.

  1. MISTYMOUNTAIN32
    mistymountain32 Win User

    Port 8080 is occupied by file explorer


    My port 8080 is occupied by file explorer. It tries to connect from 127.0.0.1:5441 to 127.0.0.1:8080 so I can't use port 8080. I try to kill the procedure but it isn't work. It will restart and still occupies port 8080.

    :)
     
    mistymountain32, Nov 12, 2021
    #1
  2. KINDERU81
    kinderu81 Win User

    opening port 8080

    I added rules to the firewall but the port is not open when I check from the power shell.

    CMD: netsh advfirewall firewall add rule name="8080_TCP" dir=in action=allow protocol=TCP localport=8080, for add rule in firewall

    Power Shell: Test-NetConnection -ComputerName 192.168.100.102 -Port 8080, for check the port

    Does anybody know why ?
     
    kinderu81, Nov 12, 2021
    #2
  3. BRO67
    bro67 Win User
    Can't open port 8080 through Windows Firewall


    &0 is notmal http requests. 8080 is normal https requests. You can find a list online of all of the ports and what they are used for with TCP and UDP.

    I always use some oddball port that something on my network or software does not use. This will show listening ports in Windows. How Can I Tell What is Listening on a TCP/IP Port in Windows?

    List of TCP and UDP port numbers - Wikipedia, the free encyclopedia
     
    bro67, Nov 12, 2021
    #3
  4. BRO67
    bro67 Win User

    Port 8080 is occupied by file explorer

    Can't open port 8080 through Windows Firewall


    Yes. Any equipment that you have on your network and want to use that port, you have to specify it in the hardware network menu. Only problem is, that it can foul up requests that come from a person web browsing, so it is always suggested to not use 80 or 8080 for anything else on the network.

    Even if the OP wants to stay with that port, they have to use the IP and the Port number (ie 192.168.1.100:80). Otherwise the router/gateway will think that you are doing an unauthorized request.

    I use a VPN to connect to my network when out and about. The Cisco RV-320 allows for PPTP VPN if you do not want to use say a OpenVPN server.

    Portforward.com is the best website when it comes to this area.
     
    bro67, Nov 12, 2021
    #4
Thema:

Port 8080 is occupied by file explorer

Loading...

  1. Port 8080 is occupied by file explorer - Similar Threads - Port 8080 occupied

  2. http://127.0.0.1:8080

    in Windows 10 Gaming
    http://127.0.0.1:8080: Thank you so much https://answers.microsoft.com/en-us/windows/forum/all/http1270018080/7fdfcbd6-d479-4970-8ddb-82a8cf5935d3

  3. http://127.0.0.1:8080

    in Windows 10 Software and Apps
    http://127.0.0.1:8080: Thank you so much https://answers.microsoft.com/en-us/windows/forum/all/http1270018080/7fdfcbd6-d479-4970-8ddb-82a8cf5935d3

  4. http://127.0.0.1:8080

    in Windows 10 Installation and Upgrade
    http://127.0.0.1:8080: Thank you so much https://answers.microsoft.com/en-us/windows/forum/all/http1270018080/7fdfcbd6-d479-4970-8ddb-82a8cf5935d3

  5. Port 8080 is occupied by file explorer

    in Windows 10 Gaming
    Port 8080 is occupied by file explorer: My port 8080 is occupied by file explorer. It tries to connect from 127.0.0.1:5441 to 127.0.0.1:8080 so I can't use port 8080. I try to kill the procedure but it isn't work. It will restart and still occupies port 8080....

  6. Port 8080 is occupied by file explorer

    in Windows 10 Software and Apps
    Port 8080 is occupied by file explorer: My port 8080 is occupied by file explorer. It tries to connect from 127.0.0.1:5441 to 127.0.0.1:8080 so I can't use port 8080. I try to kill the procedure but it isn't work. It will restart and still occupies port 8080....

  7. opening port 8080

    in Windows 10 Network and Sharing
    opening port 8080: I added rules to the firewall but the port is not open when I check from the power shell. CMD: netsh advfirewall firewall add rule name="8080_TCP" dir=in action=allow protocol=TCP localport=8080, for add rule in firewall Power Shell: Test-NetConnection -ComputerName...

  8. Unknown files occupying space

    in Windows 10 Network and Sharing
    Unknown files occupying space: My laptop has space issues. The SSD has 237 space capacity, using around 110gb of space, but there is/are unknown files occupying space. I have tried all possible solutions, deleted windows.old folder, deleted all system restore files, limited space usage by system restore,...

  9. USB PORTS NOT SEEN IN FILE EXPLORER

    in Windows 10 Drivers and Hardware
    USB PORTS NOT SEEN IN FILE EXPLORER: In WINDOWS 10 PRO, my USB ports were working/being recognized (with drive a drive letter) fine until I did a backup using Paragon Software from one external drive to another external drive. Now, neither of the two USB ports are being seen in Windows File Explorer. However,...

  10. Can't open port 8080 through Windows Firewall

    in Windows 10 Network and Sharing
    Can't open port 8080 through Windows Firewall: I have some home automation software (HomeSeer) running on a W10 machine on my network that has a web interface running on port 8080. I want to access this from other machines on the network. I couldn't access it by default so I created an inbound rule on Windows Firewall for...