Does any one know of a VNC viewer client that I can configure to use behind my schools proxy? I've already tried Tight and Ultra VNC but neither seem to have the option.
New: Kanri (Oct 09, 2024), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads November!, Please donate today
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
You need to tunnel out one of the ports allowed thru the proxy and/or firewall by using a more common port allowed to exit the LAN to the WAN (80 or 443 for example)
The more you try to do this the more you flag your account and computer and will likely get you snagged.
Cancer Survivors -- Remember the fight, celebrate the victory!
Help control the rugrat population -- have yourself spayed or neutered!
If you require a secure connection, then by all means use an SSH Protocol. When I did this at my school I used PortableApps to load putty and then routed my computers VNC port to a local port like 80. But if you are worried about getting caught, using RealVNC or UltraVNC, you can use their java applet. With a good host name in DynDNS and a common port, you won't get caught. Beware of screen monitors!! Many organizations are using monitoring software to view screens and what not. Specially if you are in a school. If you know which process runs the server, you can probably use a little programming to hijack the output and put a nice harmless screen instead. Nonetheless, BEWARE!!
-nickcaballero-
Have you tried using hamachi? I use that for my school to connect to my home network along with UltraVNC. o-o Good luck.
that often if you just set the program to use port 8080 it works. for example i have to set the http proxy in FF to dhisa:8080 in order to use FF portable.
Zoop
Use the following configurations
Create an SSH server on your target computer (ie: home computer) with CopSSH if under a Windows operating system.
-Modify the sshd.conf file to listen on port 443.
-Open the appropriate port (443) on your router/firewall, and set the NAT to point to your local IP address when accepting a connection from port 443 (ie: 192.168.0.101).
Connect to it using PuTTY Portable (ie: 204.120.95.235:443)
Tunnel remove VNC port (5900) to a local port (ie 5899)
-Go into Connection -> SSH -> Tunnel
-Source Port: 5899
-Destination: localhost:5900
-Click on Add
In the VNC Viewer, enter localhost:5899 and there you go.
You will be connecting to VNC through port 443 via an encrypted tunnel.
EDIT: Optionnally, use a free DNS provider (DynDNS, NoIP) to automatically sync your dynamic IP to a static hostname, ie: mypc.dyndns.org could like to 204.120.95.235. It's just a bit more convenient if you feel configuring it.
You might try logmein.com. It's all done through the browser and has built in encryption. I was using Tight without an SSH (dumb) and this was the easiest solution. It is put out by the same folks who put out Himachi as noted before.
LogMein is good but it doesn't support Linux and I dont like booting into Vista so I'm gonna play around with Himachi
Set up your home computer as a vpn server and you will be able to use the internet as if you were sitting at your own pc at home.
It is also very secure and noone at your school will have any way to know what you're doing. (by logging your activity at least)
I just need to get Hamachi portable working. Anyone know where I could find the Network Adapter Files ?
Hamachi requires you to have admin rights on the workstation to install it. A portable version won't be possible without an initial install, as it must run the virtual network adapter drivers at a system level.
If you plan to bypass a firewall on a restricted environment, the SSH tunnel is about your only workaround as it doesn't require any system level drivers but simply open a port in which you can tunnel SOCKS-compliant applications. LogMeIn is likely to be blocked in those environments.
I know this is a pain in the butt to configure, but once you've managed to learn it once, it's pretty easy to redo it again.
Actually Hamachi Portable (known as Buri) installs and removes the adapter on its own, But yes it does require admin rights. On that, Does anyone know a VPN program that can connect to a Hamachi VPN, has a portable version, and doesn't require Admin rights ?
I don't know any VPN clients that doesn't require admin rights, as all VPN clients require a system driver to be installed prior establishing a connection.
Ok so Ive been trying to use putty to connect to my Ubuntu computer at at home running OpenSSH but every time I try to connect it times out and fails to connect I know the IP is correct (my computers external IP right?) and the port is forwarded and that OpenSSH is running and can accept connections so what could be causing this ? I believe this to be a putty issue as I ca connect with regular CLI SSH no problem. Ive had this error on computers that are and are not behind a proxy.
Sometimes PuTTY tries to use the version 1 SSH and the host is restricted to 2, or vice versa (version 1 has some security problems). That can cause a mismatch. Check the radio button to tell PuTTY to use v2, and do the same with the sshd config.
If you are trying to connect to your computer's external IP from inside your LAN, it probably won't work (in other words, it's not worth spending time trying to fix). If you want to test your computer's external port, you need to be on the public or external side. (You probably knew that, but I thought I'd say the obvious anyway.)
In order to compare a CLI ssh to PuTTY, you would need to have both on the same machine outside your LAN (the public or external side). You should even make sure they are running in the same environment, e.g. you would need to use a Windows CLI ssh (e.g. cygwin) and Putty on the same machine that is outside the LAN. If you reboot into Linux to use ssh, you'd need to make sure it has the rest of the environment the same, e.g. local IP address, routing table, etc. before you can say they're the same.
I'd recommend testing from a machine outside your router that has relatively open permissions before going to the locked down machine. You'd want to use traceroute (tracert on Windows). You could use Nmap to see if the port is open on your external IP, use a CLI telnet client to connect to the SSH port (you should see a prompt like "SSH-2.0-OpenSSH_3.9p1" before it times out). Those things might be hard to do from the locked down machine.
You could have a friend test from outside while you are inside tweaking. Perhaps one of the people on the #portableapps IRC channel would test the connection with PuTTY. If they saw the login prompt, you'd know the port is open.
One way I test is to use ssh to connect to a linux machine out on the public 'Net, then ssh back to my external IP address and port. There are machines where you can get a free shell account if you don't have one. Most have Nmap and the other tools you'd need to make sure the port is open.
And of course on the Windows side it is possible to be running a firewall that restricts outgoing connections based on the application -- in fact, I'd expect a locked-down machine to be running that sort of firewall. (The Windows firewall mostly restricts what can open a listening port, and allows most programs to make outbound connections, but most other firewalls control outbound connections too.) If PuTTY isn't on the list of permitted applications with such a firewall, it won't be able to make an outbound connection. You can test this by using Putty to connect to other machines. (You wouldn't need an account on them, just look to see the login prompt.) The workaround there is to use a web applet running in the web browser; with a bit of luck the browser will be able to connect (at least on ports 80 and 443). There can be some sandbox issues (like the applet only connecting to the same machine unless it is "signed"), so that's not a sure thing either, but it can get you closer.
Good luck.
MC
FWIW, putty knows how to tunnel through http over many firewalls. In settings, chose Connection -> Proxy, then the HTTP radio button. If your proxy requires authentication, fill in the username and password fields. Some firewalls restrict the outbound ports they will connect to - no port 22 for you! If so, you can run open ssh on a different port (80 or 443), or have the remote firewall redirect 80 or 443 to your systems' port 22.
I have pretty good success getting to my home system and ssh.silenceisdefeat.org through a pretty restrictive firewall. I just wish putty understood https.
Are you connecting from the same computer via CLI? It could be that the IP address you have is not correct. If you can connect from the same system via CLI (or other ssh program such as Tunnelier), but not Putty, it's likely putty's fault. If you can't connect using any client, it's likely something else.
If it is putty, try upping the log settings. Select "omit session data".
http://the.earth.li/~sgtatham/putty/0.58/htmldoc/Chapter4.html#config-lo...
The Putty faq deals mainly with problems after a connection has been made.
http://www.chiark.greenend.org.uk/~sgtatham/putty/faq.html#faq-trouble
If it is not putty, here is what I do. Draw a block diagram of the system, then check for problems at each block.
Client ---> local firewall ---> Internet ----> remote firewall ----> server
Port forwarding on the remote firewall or proxy problems on the local firewall are common causes.
Here's some steps to try:
http://www.linuxforums.org/forum/suse-linux-help/82467-ssh-troubleshooti...