At least I tried....

[jmcoreymv]

I'm running Windows XP on my computer and I loaded up Ubuntu 6.06 on Virtual PC 2004. Then I installed TightVNC server on my XP machine, and the VNC client on the Ubuntu Virtual PC. I then tried to VNC into my host computer through the Virtual PC interface. It loaded but it had that effect of standing between two parallel mirrors, and seeing the reflections inside each other. And then it crashed.

 

[spyordie007]

Yup that's a fairly effective way to launch a denial of service against yourself.

 

[jmcoreymv]

Originally posted by: spyordie007
Yup that's a fairly effective way to launch a denial of service against yourself.

I just wanted to make sure I setup my VNC server right, and I only had one computer 🙂

 

[Brazen]

Originally posted by: jmcoreymv

Originally posted by: spyordie007
Yup that's a fairly effective way to launch a denial of service against yourself.

I just wanted to make sure I setup my VNC server right, and I only had one computer 🙂

BWAHAHAHA. Try setting up a second virtual machine as the VNC server next time.

 

[kamper]

Ah yes, vnc is usually smart enough to stop you from connecting to yourself but that's kinda funny. I'm curious why it crashed though, considering that it's just an image it's displaying. Was there any spike in cpu or memory usage before the end?

 

[jmcoreymv]

Originally posted by: kamper
Ah yes, vnc is usually smart enough to stop you from connecting to yourself but that's kinda funny. I'm curious why it crashed though, considering that it's just an image it's displaying. Was there any spike in cpu or memory usage before the end?

I wouldnt say it outright crashed, the vnc display got all messed up and i could see like 20 windows inside itself and nothing worked and when I closed out of the window, a big error msg popped up.

 

[nweaver]

Originally posted by: kamper
Ah yes, vnc is usually smart enough to stop you from connecting to yourself but that's kinda funny. I'm curious why it crashed though, considering that it's just an image it's displaying. Was there any spike in cpu or memory usage before the end?

it wasn't connecting to "itself" it was connecting to the host machine from the guest OS.


not to mention, VNC allows connections to localhost (and damn good thing, too) because I use it when tunneling traffic through an ssh tunnel.

 

[SunnyD]

You've torn a hole in the space-time continuum. All your base are belong to us.

 

[Genx87]

Done this a couple of times by mistake. Right as I get done typing in the password a little thing in the back of my brain goes "what are you doing?". But it is too late and the endless disply of windows starts up 😀

 

[kamper]

Originally posted by: nweaver

Originally posted by: kamper
Ah yes, vnc is usually smart enough to stop you from connecting to yourself but that's kinda funny. I'm curious why it crashed though, considering that it's just an image it's displaying. Was there any spike in cpu or memory usage before the end?

it wasn't connecting to "itself" it was connecting to the host machine from the guest OS.

I know, I was just making sort of a side point.

not to mention, VNC allows connections to localhost (and damn good thing, too) because I use it when tunneling traffic through an ssh tunnel.

Good point, I've done that too. But I do also remember trying to do the recursive thing on one machine (for fun) and it refused. How does it know the difference?