Can't figure out why you have the hub - router arrangement you have. But as
has already been noted your issues look to me to be router rather than VNC
related.

If your Internet connection is plugged to the hub and then the hub to the
router, it sounds like you have that (the hub) plugging into the WAN port on
the router (it would have to be or you wouldn't get your other PCs unto the
Internet via the router at all).  If that is the case then it is no wonder
the PC on the hub cannot see the other PCs (connected wired or wirelessly to
the router) as that lone PC is on the WAN side of your router and the
remainder are on the LAN side, thus separate subnets.

> As you might expect, when I pinged the uncooperative PC by  name the host
was unknown.
Correct (by the above scenario) - not in the sub-net.

> > And pinging other machines from that PC, either by name or IP address,
yielded no connectivity

Again correct (by the above scenario) - the lone PC is outside the NAT
router and thus to all intents and purposes it's "on the internet." Most of
these routers will block ping (as it would be regarded by the router as some
busy-body on the Internet trying to probe your LAN).

> when I connect all of the machines to the LAN ports in the wireless 
> router I can do ping all machines by name with no problems.  Any

Once again correct (by the above scenario). 
And if this is the case (that you can connect all of the machines to the LAN
ports in the wireless router) then why have the hub (and the lone PC) where
it is?

Unless you have a very good reason (and I can't think of one!) for having
the hub where it is I'd move the hub off the WAN port and unto the LAN side
of the router and plug the internet connection directly into the WAN port of
the router rather than via the hub. That should move you forward a bit.

Cheers,
Peter


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Behalf Of [EMAIL PROTECTED]
> Sent: 27 May 2004 12:00
> To: [EMAIL PROTECTED]
> Subject: VNC-List digest, Vol 1 #935 - 13 msgs
>
> 
> Message: 1
> Subject: RE: connection issues
> Date: Wed, 26 May 2004 13:19:56 +0200
> From: "Seak, Teng-Fong" <[EMAIL PROTECTED]>
> To: "vnc-list" <[EMAIL PROTECTED]>
> 
>       I don't quite get the "picture" of your network
> topology.  That's why I replied your mail to the 
> mailing-list.  Hope others see what it is.
> 
>       But, if I understood correctly, your witeless router is
> very probably not setup properly, or it's not supposed to 
> work like a real router or a switch.  I don't know if what 
> I'm going to say works, but let's see:
> if your wireless router is supposed inside your LAN, read the 
> doc to see if it could act as a real router, ie you could 
> setup route table inside it.
> you could also look if it could act like a switch, ie, it's 
> address as well as those managed devices' addresses are in 
> the same subnetwork.
> 
>       HTH
> 
> > -----Message d'origine-----
> > De : Ron Crummett [mailto:[EMAIL PROTECTED]
> > Envoyi : mardi 25 mai 2004 20:17
> > @ : Seak, Teng-Fong
> > Objet : RE: connection issues
> > 
> > As you might expect, when I pinged the uncooperative PC by
> name the host was unknown.
> > And pinging other machines from that PC, either by name or
> IP address, yielded no
> > connectivity.  We have an Internet connection running into
> a network hub.  The
> > uncooperative PC is plugged directly into this hub, as is a
> wireless router.  A second PC is
> > connected to the router via a LAN cable and I am connected
> wirelessly.  This setup is
> > generating all sorts of problems; however, when I connect
> all of the machines to the LAN
> > ports in the wireless router I can do ping all machines by
> name with no problems.  Any
> > ideas?
> > 
> > That's it from here.  More to come as the plot thickens...
> > 
> > Ron Crummett
> > CayNet Consulting
> > (208) 424-1228 office
> > (208) 850-6589 cell
> > http://www.caynetco.com
> > 
> > 
> > 
> > ---------- Original Message ----------------------------------
> > From: "Seak, Teng-Fong" <[EMAIL PROTECTED]>
> > Date:  Mon, 24 May 2004 16:36:21 +0200
> > 
> > >   Your first problem problem doesn't seem to have
> anything to do with VNC.  When
> > you type the command:
> > >ping name_of_PC
> > >do you get the result as "unknown host"?
> > >
> > >   If yes, it's a matter of DNS or network visibility or
> badly configured IP address.  But
> > it would be hard for us to tell you what to do exactly.
> You'd better contact your
> > network/system administrator about this issue.
> > >
> > >> -----Message d'origine-----
> > >> De : Ron Crummett [mailto:[EMAIL PROTECTED]
> > >> Envoyi : vendredi 21 mai 2004 01:15
> > >> @ : [EMAIL PROTECTED]
> > >> Objet : connection issues
> > >>
> > >> I'm not claiming to be an expert at the Internet or
> anything, but I have a scenario that
> > does
> > >> not seem to be right.
> > >>
> > >> I am learning about VNC and have it installed on three
> machines here at my office.  One
> > of
> > >> these machines is not cooperating at all.  The only way
> I can access this machine is by
> > using
> > >> the IP address - the computer name doesn't work.
> Moreover, I cannot access the two
> > other
> > >> computers from this machine.  Any ideas?
> > >>
> > >> That's it from here.  More to come as the plot thickens...
> > >>
> > >> Ron Crummett
> > >> CayNet Consulting
> > >> (208) 424-1228 office
> > >> (208) 850-6589 cell
> > >> http://www.caynetco.com 
> > >> _______________________________________________
> > >> VNC-List mailing list
> > >> [EMAIL PROTECTED]
> > >> To remove yourself from the list visit: 
> > >> http://www.realvnc.com/mailman/listinfo/vnc-list
> > >_______________________________________________
> > >VNC-List mailing list
> > >[EMAIL PROTECTED]
> > >To remove yourself from the list visit: 
> > >http://www.realvnc.com/mailman/listinfo/vnc-list
> 
> --__--__--
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
To remove yourself from the list visit:
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to