Tag Archive for 'TightVNC'

Considering The SOHO

When not scraping, sanding, painting, and generally following orders from Management, my time is backfilled and my bank account is padded by doing help desk work on the side, usually cleaning up Windows boxes that have been neglected and abused as well as the occasional hardware upgrade for the tech phobic, but the best work are the small offices that I maintain as these are the places where the dollars need to be stretched for the greatest return.

At the moment I have one client with a very small office that when set up was configured like a home network with an emphasis on ease of use over security. The result is two Windows 2000 PCs and one Windows XP laptop joined by a password free Workgroup and connected to a cable modem through an aging Linksys router. The PCs themselves are getting long in the tooth having been purchased some six years ago and to add insult to injury he has been battling virus outbreaks with increasing regularity. I make sure that he stays on top of definitions and patches but the network itself is inherently insecure and added to that both machines are logged into as local admins.

Current Configuration
Plain vanilla SOHO

He has given me a list of things he would like to see implemented when or if he proceeds with upgrading or reconfiguring the existing network including somethings I would file under necessity: automated backup plan, network firewall solution, and centralized and secure file sharing. While 2000 is still a serviceable OS, I’m leaning towards recommending that he purchase two machines to replace those boxes and to go with XP Professional, skipping Vista for now. Surprisingly, I’m not recommending he deploy Ubuntu, SUSE, or Fedora for the simple fact that it might be too much change for him and his employees and XP, when configured properly, is a fairly rock-solid OS.

The first possible configuration maintains the general layout of the network but would allow for remote administrative access as well as centralized file sharing and automated backups by redeploying one box to act as an SSH and file server.

Configuration One
Slightly more complicated…

The purple lines represent an SSH tunnel, the red is vnc, and the blue for file sharing and backups, and you can plainly see what my choice for the server OS. This configuration is most likely the one he will sign off on as the topology closely resembles what he has grown accustomed to but I do have a second configuration in mind to further enhance security.

Configuration Two
Just a little more complicated…

The inclusion of the Smoothwall appliance will go a long way in enhancing security, particularly if I shift tactics and push that they log into their PCs as regular users and reserve the admin account for special cases. The Smoothwall appliance can also be deployed on the remaining 2000 PC to make better use of the hardware with the only cost being replacing the router with a switch.

All things considered, I think that the two options make the best use of his money and could go a long way in enhancing the security of his network as well as functionality. We’ll see what he goes with.

TightVNC, SSH, PuTTY, and You!

So this morning I was in a bind, I’m sitting at work and wanted to listen to my music collection at home but my player was telling my that the share didn’t exist, to fix it I needed to reboot the box. Since the collection is served up by Media Jukebox it is housed on a Windows box which further complicates matters because I have no real command line tools at my disposal, the only way I can interact with the box is through TightVNC. Now, TightVNC is running on all the boxes but when I installed the new router I made the conscious decision not to punch the ports for it so I’m back to square one. Enter PuTTY and SSH.

While at work I use PuTTY to connect to my server at home, it is all command line which is fine for nearly 99.9% of the tasks I perform but when I have to administer that one lone Windows PC I’m out of luck. So to work on that box I’ll either need to punch holes or set up a tunnel using SSH and PuTTY. I opted for the latter which proved to be so easy I was surprised. The University of Stockholm has a well written tutorial on it that I used to get things rolling in under five minutes.

The key point to remember is that the tunnel needs to be configured from the perspective of the host machine so the default TightVNC settings would be localhost:5900.

PuTTY Tunnel

Then all you need to do is setup the session like you normally would, connect, log in, then launch TightVNC and point it towards localhost and viola! Now I just need to think of other applications where tunneling would be handy–secure surfing at Internet cafes come to mind.





Creative Commons Attribution-NonCommercial-ShareAlike 3.0 United States
Creative Commons Attribution-NonCommercial-ShareAlike 3.0 United States