Hungryherman writes:
>ICS! That may be it. Good idea. I'll try configuring the VNC server to
>use ports under 1024, or map 5800 & 5900 through ICS (per
>http://support.microsoft.com/support/kb/articles/Q231/1/62.ASP)
Yesterday I re-posted some registry entries which will open up ICS to listen
on 5800 and 5900, this might be of some help.
>I run telnet from the "Run" dialog. When the connection fails, it snaps
>window closed.
I would suggest that if you want to see what is going on then you open up a
DOS box (or command prompt as NT/2000 insists on calling it) and enter your
commands from there. The Run dialogue is for those who do not want
diagnostic output...
-------------------------------------------------------------
Seth Kneller
[EMAIL PROTECTED]
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS d- s: a20 C+++ UL+ P+ L++ E---- W+ N+ o? K? w O- M+ V? PS
PE- Y+ PGP+ t- 5- X- R- tv+ b+ DI+++ D G e h+ r-- y--
-----END GEEK CODE BLOCK-----
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
