Windows 10: Unable to use TCP ports above 49728

Discus and support Unable to use TCP ports above 49728 in Windows 10 Network and Sharing to solve the problem; Hi guys, I originally saw this issue within a Node.js app, but I've replicated it in a basic winsock TCP server example as well. Ever since the latest... Discussion in 'Windows 10 Network and Sharing' started by NicholasCrast, May 22, 2019.

  1. Unable to use TCP ports above 49728


    Hi guys,

    I originally saw this issue within a Node.js app, but I've replicated it in a basic winsock TCP server example as well. Ever since the latest Windows Update, I'm unable to use ports above 49728 in my applications. I get access denied errors when I try to bond.


    I've tried during all windows defender and firewall functionality off, but that seems to make no difference. I took a look through the release notes of the past few released, but couldn't find anything that seemed related to this.


    Has anyone experienced this? This has happened with two of my Windows machines (running Win10 Pro) after they restarted and received the latest update.


    -Nick

    :)
     
    NicholasCrast, May 22, 2019
    #1
  2. Nikhar_K Win User

    How to reset dynamic port for TCP/IP to default

    Hi,

    Thank you for writing to Microsoft Community Forums.

    Please reply to the following questions to help you further:

    • Which version of Windows is installed on the computer?
    • Is the computer connected to a domain network?

    I would suggest you to refer the article on
    The default dynamic port range for TCP/IP
    to know more about default dynamic range.

    However, if you have further queries related to this issue, you can post your query in

    TechNet forums
    , where we have support professionals who are well equipped with the knowledge on dynamic ports.

    Hope it helps.

    Please reply with the status of the issue, we will be glad to help you further.

    Nikhar Khare

    Microsoft Community - Moderator
     
    Nikhar_K, May 22, 2019
    #2
  3. Looking for IIS real time TCP viewer, Logger

    Can anyone suggest a free real time TCP viewer-logger?

    Later edit:
    Currently I have TCP view from microsoft. It would be nice if it was sort of the same thing with the IIS log files, mail, and ftp ports, etc. along with some parsing.
     
    greenhouse, May 22, 2019
    #3
  4. MrJezbo Win User

    Unable to use TCP ports above 49728

    Unable to enable Net BIOS over TCP/IP in PowerShell


    Hi Eagle51,

    When I try to change the value in the registry, it still shows as disabled.

    I ran the commands you suggested and still no luck. However, should the value be changed from 0 to 1 in the last command?


    Unable to use TCP ports above 49728 [​IMG]
     
    MrJezbo, May 22, 2019
    #4
Thema:

Unable to use TCP ports above 49728

Loading...
  1. Unable to use TCP ports above 49728 - Similar Threads - Unable TCP ports

  2. tcp connect to port 443 failed

    in Windows 10 Gaming
    tcp connect to port 443 failed: I have checked the port 443 by powershell in win 10 by the following command:"tnc hostname –port 443" mention hostname of the computerbut I got the “Fail” result how can I solve the problem that get the “True” result?I was created Inbound rule for tcp&udp 443 and also...
  3. tcp connect to port 443 failed

    in Windows 10 Software and Apps
    tcp connect to port 443 failed: I have checked the port 443 by powershell in win 10 by the following command:"tnc hostname –port 443" mention hostname of the computerbut I got the “Fail” result how can I solve the problem that get the “True” result?I was created Inbound rule for tcp&udp 443 and also...
  4. tcp connect to port 443 failed

    in Windows 10 Network and Sharing
    tcp connect to port 443 failed: I have checked the port 443 by powershell in win 10 by the following command:"tnc hostname –port 443" mention hostname of the computerbut I got the “Fail” result how can I solve the problem that get the “True” result?I was created Inbound rule for tcp&udp 443 and also...
  5. TCP and UDP port no used by homegroup computers

    in Windows 10 Gaming
    TCP and UDP port no used by homegroup computers: A. TCP 3587 UDP 3389B. TCP 3587 UDP 3540C. TCP 3389 UDP 3540D. TCP 80 UDP 3540 https://answers.microsoft.com/en-us/windows/forum/all/tcp-and-udp-port-no-used-by-homegroup-computers/47a6498a-4c37-43c1-9806-2f334441aa17
  6. TCP and UDP port no used by homegroup computers

    in Windows 10 Software and Apps
    TCP and UDP port no used by homegroup computers: A. TCP 3587 UDP 3389B. TCP 3587 UDP 3540C. TCP 3389 UDP 3540D. TCP 80 UDP 3540 https://answers.microsoft.com/en-us/windows/forum/all/tcp-and-udp-port-no-used-by-homegroup-computers/47a6498a-4c37-43c1-9806-2f334441aa17
  7. TCP and UDP port no used by homegroup computers

    in Windows 10 Network and Sharing
    TCP and UDP port no used by homegroup computers: A. TCP 3587 UDP 3389B. TCP 3587 UDP 3540C. TCP 3389 UDP 3540D. TCP 80 UDP 3540 https://answers.microsoft.com/en-us/windows/forum/all/tcp-and-udp-port-no-used-by-homegroup-computers/47a6498a-4c37-43c1-9806-2f334441aa17
  8. Unable to reset TCP port number to default settings

    in Windows 10 Network and Sharing
    Unable to reset TCP port number to default settings: Hi, I have changed default TCP port from 15100 to 15300 using regedit function. However now I want to revert back to default port settings. I deleted the registry entry however still it is using 15300 port. How to solve this. Thanks for your help. Regards...
  9. Block TCP Port 3389

    in Windows 10 Network and Sharing
    Block TCP Port 3389: How Block Port 3389 ? Thanks https://answers.microsoft.com/en-us/windows/forum/all/block-tcp-port-3389/de6fb848-5a1b-4c07-bc59-28f1ddb2341b
  10. TCP - Remote ports 80 and 443?

    in AntiVirus, Firewalls and System Security
    TCP - Remote ports 80 and 443?: Under resource monitor > TCP connections, I've noticed quite a bit of activity on remote ports 80 and 443. I decided to track several of these IP addresses and whilst some are expected (Microsoft, Amazon (Firefox)), there were a few which went to other mainly web hosting...