NEED HELP WITH VNC
tfseak "at" futurmaster.com
Mon Mar 22 11:48:00 2004
I agree with Bill. If things seem too much or too complicated for you to sort out, I don't think you should still consider it as a DIY stuff. Why don't you call a computer service and pay them some bucks to make things straight for you?
I'm sorry to tell you, but there's some limits in everything. Just as a car; when you can't repair it using your home hammer and spanner, you should take it to the garage.
> -----Message d'origine-----
> De : Bill Cassady [mailto:caersidi "at" freeshell.org]
> Envoyi : dimanche 21 mars 2004 17:18
> @ : First Name Last Name
> Cc : vnc-list "at" realvnc.com
> Objet : Re: NEED HELP WITH VNC
> On Sat, 20 Mar 2004, First Name Last Name wrote:
> > The chart below is what happens when I Ping from each machine.
> > 192.168.0.10 (W2K) 192.168.0.11 (XP) 192.168.0.12 (W95)
> > XP okay okay timed out
> > W2K okay timed out timed out
> > W95 okay timed out okay
> > I've attempted to VNC to/from all the machines and this is what I get.
> > XP----->W2K (I can sit at the XP and VNC into the W2K.)
> > W95-->W2K (I can sit at the W95 and VNC intot he W2K.)
> > No other combinations will work. I've tried to VNC from the XP to the W95
> > but it doesn't work. Also trying to VNC from the W2K to the W95 or XP will
> > not work.
> This is not the forum to debug Windows networking.
> That said, VNC won't work if the fundamental network is not
> straightened out first.
> Some suggestions:
> Work on 2 machines at a time. Get those communicating both ways.
> The one way W95->W2K leads me to suspect W95 doesn't have its LAN
> setup independent of DUN, or has incorrect DHCP, or gateway.
> Then do the same with W2K->XP
> When all machines can ping each other, then it will be fruitful to
> discuss VNC difficulties...if any.
> Hope this helps-
> caersidi "at" sdf.lonestar.org
> SDF Public Access UNIX System - http://sdf.lonestar.org
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: