Maybe this tools can help you.
http://www.tglmicro.com/Inet2Com.htm
http://www.esei.com/electrocomm/
good luck.
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7i=29906t=29826
--
FAQ, list archives, and subscription info:
obvious solution would be setting up *nix, or else try the VNC
(client/server), simple to set up, very compact, has basic security
features,works like a charm from as lite as dialups (obviously very little
overhead). I use it to access lab setup in my office (from home) to save the
costs of
Thanks Nick. I used VNC quite a bit in my previous job, but I was hoping
not to have to use it again. Seems a shame to use it for a character based
app like telnet. Oh well, it does work and you're right, not a bad little
app. Did a port scan and found that it uses 5800 and 5900 ports in case
I have myself been hesitant to use VNC, but what with the localized nature
of MSWINXXX, it seems to interpret the instruction on the local machine,
rather than transferring requests between source and target machines.
In fact, I had been trapped in a similar issue, similar platform (and Exceed
4 matches
Mail list logo
