I had this same error. I was connected to my desktop, no firewalls or
anything between my laptop and desktop. I ran windowsupdate remotely,
installed the 5 critical updates release today and upon my desktop coming
up, I tried remoting to it and got the same error immediately. I logged
into a VMWare virtual machine and it had the same problem remoting to the
host. I had the same 0.0.0.0 listening thing you did. I could ping, use
computer management, and file sharing on my desktop, logging in locally
worked as did fast user switching.
I rebooted again to no avail. Same error, sometimes another error claiming
network problems, but I could always remote to my laptop from the desktop.
I unchecked the "allow remote desktop" box in computer properties, applied
the settings and rechecked the box, nothing.
Finally, I ended the svchost that was running terminal services and manually
started the terminal services service, this worked. I rebooted to make sure
and it came back up. I hate errors, esp. the ones that are fixed by by
themselves and/or by changing or doing things that technically shouldn't
matter
I also wonder, does anyone know if it makes any kind of difference if I set
the Terminal Services service to automatic?