Bug 1804692 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
I think this might be related to an issue I'm having - mochitests not working on Windows 10. It started today:
```
Revision 1 by
on 
I think this might be related to an issue I'm having - mochitests not working on Windows 10. It started today
Revision 2 by
on 
I think this might be related to an issue I'm having - mochitests not working on Windows 10. It started today

EDIT: My mochitest issue was unrelated to the log spam. If anyone else sees this issue and does the same search I did, here's how I resolved it. I figured the port was blocked so I just restarted my PC, but then it happened again so I assumed it must not be the port. Apparently hyper-V reserves a random range of ports, and I guess that just coincidentally included 2828 both times. Running this basically clears the port exclusion:
```
reg add HKLM\SYSTEM\CurrentControlSet\Services\hns\State /v EnableExcludedPortRange /d 0 /f
netsh int ipv[46] set dynamic tcp start=49152 num=16384
net stop winnat
net start winnat
```
Revision 3 by
on 
I think this might be related to an issue I'm having - mochitests not working on Windows 10. It started today

EDIT: My mochitest issue was unrelated to the log spam. If anyone else sees this issue and does the same search I did, here's how I resolved it. I figured the port was blocked so I just restarted my PC, but then it happened again so I assumed it must not be the port. Apparently hyper-V reserves a random range of ports, and I guess that just coincidentally included 2828 both times. Running this basically clears the port exclusion:

reg add HKLM\SYSTEM\CurrentControlSet\Services\hns\State /v EnableExcludedPortRange /d 0 /f
netsh int ipv[46] set dynamic tcp start=49152 num=16384
net stop winnat
net start winnat

Back to Bug 1804692 Comment 2