Thanks for the welcome. I really hope I get to find a solution. I did not rehash my original message at the bottom of this, but the machines in question are:
H - my home machine B - machine on work network W - my work machine I would think, if there were a pathing issue, that H would not be able to connect to B OR W. As it stands, H can connect to B just fine with VNC. H cannot connect to W directly, but CAN connect to W by going through B first, i.e. connecting to the VNC server on B, then connecting to the VNC server on W through that VNC session. It is mighty slow, but it works. I can ping both B and W from H when connected through the VPN. I have tried telnet to the relevant ports on B and W, and have never gotten anything back from either one. I do not know if that is a red herring or if it is important. Thanks for any help/advice. I am unable to dial directly into the VPN or work network from H at this time. The DSL setup is all I have. -- Jonathan "Alex K. Angelopoulos" <[EMAIL PROTECTED]> wrote: >Welcome to the list, John! >This one is a little hard to call. I am guessing you might even >have an issue with MTU size that erratically appears; since S2 is >coming through another path this would explain why it can >connect and you can't, and also explain the frenetic network >activity. >If you have alternate access such as another ISP or a direct dialin >to your work network that you can use at least once or twice, you >can try connecting over that. The reason for this test is to see >whether there is a path-based problem. _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] http://www.realvnc.com/mailman/listinfo/vnc-list
