Another note for those interested... I found out something rather nasty about the HPC and a VNC connection.. The Cisco NIC that I'm using is in the CAM mode or Constantly always on... this is a major battery drain! I accidently drained my HPC of its battery over the weekend and thus, I had to re-install everything... One problem kept happening.... My VNC remote would fail each time I tried to connect.
Then it dawned on me that my device name had changed, so Win2K did not recognize the HPC's attempt to connect. Basically, VNC client does not 'sidestep' NT security - it seems to 'ride on it' instead. So, to make a long saga short here... Be sure your HPC has an account on your Win2k box or you will become frustrated with the the 'cannot connect' error msg that flashes very fast... Anyway, I'm nearly done with the documentation and I will post a link so you can all get to it Thanks !!! Will Olson Paragon Visual Solutions Inc. 810 East Indiana Spokane, WA 99207 (509) 482-3465 http://www.paravis.com [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, mail [EMAIL PROTECTED] with the line: 'unsubscribe vnc-list' in the message BODY See also: http://www.uk.research.att.com/vnc/intouch.html ---------------------------------------------------------------------
