Forum Widgets
Latest Discussions
Connection Refused at TCP/IP Level
Guys, i have a web application running on Windows 2025. Occasionally, the application experiences bursts of over 500 simultaneous connections. Even though, the server showing less than 10% CPU utilization and about 75% of RAM still available, I am encountering "connection refused" errors. I can see Windows Performance counter TCPv4 / Connection Failures change when this happens. There is no antivirus deployed during my test, and Windows defender is off. i have seen similar issues on Windows 2019 and 2022 also. I suspected SynAttack detection, but the TCP diagnostic counters for SynAttack detection dont know any values. It appears to me that there is some Windows OS limitation that causes this issue. Does anybody encounter this situation before?
About recommend hardware for the next version of windows in the future
I am a loyal Microsoft Windows user. Now, I have a small problem: I want to upgrade my computer to Windows 11 but my hardware does not meet the requirements; I need to upgrade the hardware for it. I am also a loyal AMD Threadripper Pro user. I see the minimum requirement is Ryzen Threadripper Pro 5945WX. I want to ask when Windows 12 is released, will it still be supported? And Win 13, Win 14 in the future. I do not have the conditions to change the hardware every time there is a new version of Windows. If it is not supported, I may have to learn to switch to another operating system. P/s: Don't ask me why it have to be Ryzen Threadripper Pro or Recommend another one, Just say I want to use Ryzen threadripper pro to experience playing Pikachu in 1080p mode more smoothly.Windows Research Kernel Bring it Back!
I think it is time to revive the Windows Research Kernel! We need the community to be able to understand what is going on without letting everything out of the bag. The last version available was v1.2 which was based off of the kernel for Windows XP and Windows Server 2003 SP2. We need a modern release for development, education, and security research. Who is with me?Invalid requesting-user-name value after system reboot (IPP Everywhere)
When I add a IPP Printer, it works fine until I restart OS, after system reboot the requesting-user-name contains WORKGROUP\VM132786998$ so it's domain\computerName$. And the user cannot be correctly recognized. Steps to reproduce it: 1. Add IPP printer 2. Print Test page 3. Restart system 4. Print Test page Current result if inspecting by Wireshark: at point 2. requesting-user-name contains correct "Administrator" value at point 4. requesting-user-name contains incorrect "workgroup\VM132786998$ Expected result: in both cases correct value Administrator must be present. Currently only restart print spooler or recreating printer solves the issue. (See attached wireshark captures before and after print spooler restart) Note: The issue is not reproducible in build 22H2 22621.3447. I'm able to reproduce it in 23H2 22635.4076. Same error is observed here (comment from Douglas Kosovic): https://learn.microsoft.com/en-us/answers/questions/1428508/ipp-everywhere-ipp-2-0-server-basic-authentication Attached screenshots from wireshark captures when it's happening and after restarting Print Spooler.
