I have two comps, a desktop and a laptop. Both have VNC server on it because I tend to also do alot of remote work outside the house. Anyways because of problems with the pors on the new router, could never control the VNC on my laptop outisde the local network.
Then yesterday I decided to take out the password authentication of my laptop's VNC so that I can just immediatly access it from my desktop (easier than havin 2 mouses and 2 keyboards sometimes).
Anyways a few hours later, someone manged to access my laptop. At first I though hey could be someone friendly. Then I saw the guy first shut off my antivirus and firewall. Started to Run->Cmd and iPconfig (only got the local ip address though) and was about to download an exe from some dubious website when I pulled the plug.
Lucky break there.
(continuation)
It's funny how some hacker managed to access my laptops VNC when I myself couldn't ;p
Its a good thing I was actually looking at my laptop when it happened.
Please understand that I say the following with all due respect, but... duh.
>>3 signed.
Welcome to the New Internet where seeing hackers/worms/zombies/AIDS isn't just something you hear about.
Speaking of AIDS, I think we've gone from something like the AIDS situation in the west to Sub-Saharan Africa over the course of the last years - on the net, it's no longer if but when you get owned if you're doing something stupid.
>>3
the key thing is that I thought acceesing the VNC remotely outside the local network wasnt working on my laptop because I had tried numerous times and never got a succeful connection.
Now might be a good time to get in touch with the would-be hacker and ask how he/she did it. :-)
>>2-3
Hey, look, it's the troll crew. Can't tell the two of you apart.
what
>>5
Perhaps your machine is already pwnd to forward packets on some port.
Windows includes a feature that will route packets from lan1 on nic1 to lan2 on nic2 without you configuring anything! I discovered this in X-Setup teaking program by casual looking. It cannot be disabled in the basic Windows GUI (afaik) and is enabled by default on any BFU-friendly version of Windows (such as XP, but not Server 2003).
The said (mis)feature is not a full-featured Bridge nor a NAT. It's supposed to work only if those two are private networks. It won't share the Internet connection as it is. It's purpose is not to disappoint a lamer who wires a bunch o'comps for a lanparty.
>>7
Neither can I. Maybe we are the same person actualy