Derek R. said: > > The Long... > > > > I don't know what your problem is, but can confirm > > that VNC works as you set it up (both sides natted). > > I use this extensively...
Ditto. > Just confirming: so you're definitely behind a router that is using > NAT when you're at work? Well, it's not a work, but I can say I've done it with both sides NATed. > This would seem to rule out EVERYTHING, so I can only conclude that > there's some behavior of vNC that isn't being reported. Is there a way > to get a fully-detailed debugging log from the client and/or server > side of vNC? If I could tell _exactly_ where it was falling on the > floor, I could probably figure it out; but the sparse entries in the > Event Log don't really give enough information. =/ I knew how to increase debugging, but I'm drawing a blank... Ah, here it is: winvnc4 --help [snip] -log <logname>:<destination>:<level> [snip] There's more info there as to the values. > > The only thing you did diferent than I is you redirected > > 5900 to 5900. I never do this since I often have a vncserver > > running on the same machine. Therefore I allways redirect > > another port usually something like this: > > I've messed around with changing the local ports, but it doesn't > change anything; same results whether I connect to "localhost", or > whether I forward 9876 to 5900 and connect to localhost::9876. Since I've seen wierder things... what happens if you use the hostname (instead of localhost) in the tunnel? Or forward to another machine? -- William Hooper _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
