On 12/10/10 17:16, Terry Coles wrote:
What we have decided to do is to install cygwin on a little used server on the internal network and use terminal services to get to it via VPN. The server isn't running a firewall and everything will be inside our secure netork, so we think it will work. That's tomorrow's task.
Great news. Sounds like a good plan to use the internal network server. Although I don't recommend using telnet to logon (unencrypted, password in clear text), it is great for diagnostics, like telnet ipaddress portnumber, to check you can actually get to the port ( use Ctrl ] to break out then type exit to quit). I've used cygwin a lot in the past where I was forced to use Windoz to get some sort of control back. OpenSSH is a great tool, particularly for securing traffic like X using tunnelling. Saved a lot of hassle where very restrictive firewall rules are applied as you just need SSH port 22 open.
Good luck fixing the script ;-) John. -- -------------------------------------------------------------- Discover Linux - Open Source Solutions to Business and Schools http://discoverlinux.co.uk -------------------------------------------------------------- -- Next meeting: Crown Hotel, Blandford Forum, Tuesday 2010-11-02 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ How to Report Bugs Effectively: http://goo.gl/4Xue
