Ken:
Heya. It sounds as if your client as a low-end firewall
protecting their network of Win2K PC's. GoToMyPC is clever in
that it can easily circumvent low-end firewall appliances (the
tradeoff to the convenience is that all the data during a remote
control session goes thru GoToMyPC's severs), but VNC doesn't
work like that.
Once your successfully...err...GoToTheirPC, you can
startup VNC and move around the LAN, because that VNC connection
is "behind" your client's firewall.
Try this: one one of your client's PCs, start up a
web browser and go to: www.GoToMyVNC.com (no kidding). Run the
script there, and it will check to see if a firewall is getting
in the way.
Good luck!
-Scott
> Hello everyone,
>
> I'm having a VNC connection issue that I cannot seem to figure out. I have
> VNC server (running as a service) on several clients' servers, all Windows
> 2000 Server. I've never had any connection problems in the past. A client
> called today and asked me to remote in through VNC and examine an issue ...
> I pulled up my VNC client but couldn't connect. Further examination
> revealed that I couldn't connect to *any* of my clients' servers running
> VNC. My initial thought was that the issue is on my ISP end (Comcast), so I
> fired up a dial-up connection to EarthLink and that didn't work either. I
> can ping the IPs of all systems in question. Now here is the kicker ...
> other client, rather than using VNC, uses GoToMyPC ... so I connected to
> that system using GoToMyPC, then from there fired up a VNC client and
> attempted to connect to my clients' servers ... no problem at all, with each
> and every one I was able to connect without issue.
>
> Anyone have a clue on this one?
>
> Many thanks,
>
> Ken
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list
