Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.4.0f1
2017.4.29f1
2018.4.0f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1178646
Regression
No
An application listens on a random port when using an HttpListener on Windows Server 2012 SP2
How to reproduce:
1. Build and run the user attached project
2. Insert "http://127.0.0.1:12345/" into the text field
3. Click on "Start"
4. Find the port application is listening on using "netstat -aon | findstr [Application PID]"
Expected results: The application is listening on port 12345 (0.0.0.0:12345)
Actual results: The application is listening on a random port (0.0.0.0:[Random port])
Reproducible with: 2017.4.32f1, 2018.4.9f1, 2019.2.7f2, 2019.3.0b5, 2020.1.0a6
Additional notes:
1. Task Manager can show the PID of the application
2. The application listens on the port 12345 only locally
3. The issue does not reproduce on Windows 10 and Windows 8
4. Windows Server was running on a VirtualBox. It may have affected the results
5. Testing was done using .NET 3.5 and 4.x equivalents. On .NET 3.5 the application was listening on the chosen port, but a new random port was open too
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error ‘cannot use casts on l-values’ when a variable is assigned inside a second-level nested if statement before being used in a conversion
- "You cannot save to an invalid folder" warning dialog box is shown when canceling Tile Palette creation
- Global Volume visual details are blurred when Tonemapping mode is set to any other than 'ACES'
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
ashwinimurthy
Oct 21, 2019 15:45
I am sorry to say that will be not be fixing this particular issue because it only happens on Windows Server 2012 SP2 and has a very low vote count.