Just to clarify, since there seems to be a tidbit of confusion here:
I'm aware that RDP is stateful - as I recall all I did was hit the drop-down and choose remote desktop and allowed the router to auto-fill. Lazy > aware.
However, whether it uses TCP only (as it does) or uses both TCP/UDP, or even if this were an entirely different protocol which ran UDP, the "both" option should work. The issue wasn't actually whether the port forward worked - I could verify that RDP was indeed active through the firewall to the desired machine. The issue was that it caused random restarts. and it actually did so based on which lines in the form were filled rather than protocol. I was able to produce this with RDP, FTP, SSH, and several other valid ports plugged in several ways.
So why the interest in this particular bug in the first place? Well, not every virtual would necessarily be something you'd want up all the time. Perhaps you have a service here or there that you only want up when you're home. Perhaps you have something configured which eats your upstream and you're about to go jump into your favorite FPS with all the aimbotters and LPB's. Or maybe you set up a virtual as a back door while you're at work and you don't want it or need it online during the weekends when you're home. It'd be nice to be able to just uncheck, hit save, and move on. But this particular bug would make that a tad difficult, and nearly impossible to fix from remote.
I have not tried upgrading to the latest betas since this post, so I have no idea whether this is something that's been corrected, something they were able to reproduce successfully in the lab or not, etc.
Author
Topic: Virtual Server setting causes instability (Read 12554 times)