Cannot access IP address from another subnet

[James Weatherall]

Javier,

VNC won't alter your network settings in any way, so the fact that your
ability to ping machines changed when you installed it is coincidence.

Ping isn't a definitive test - many firewalls will allow pings to be
ignored, so you should check to verify that that's not what's happened to
your problem systems.

Regards,

Wez @ RealVNC Ltd.
 

> -----Original Message-----
> From: vnc-list-admin "at" realvnc.com 
> [mailto:vnc-list-admin "at" realvnc.com] On Behalf Of Javier Sheh
> Sent: 22 January 2007 20:08
> To: lapidis666-vnc "at" yahoo.com; vnc-list "at" realvnc.com
> Subject: Re: Cannot access IP address from another subnet
> 
> All PCs are running Windows 2000.  I found out that PC B that 
> has the Server 
> was running 3.3.3 R9 while the Client in PC A was running 
> 4.1.1.  Could this 
> cause such a problem?  I re-installed the software on both PC 
> A and B to 
> 4.1.2 but still have the same problem with the IP addresses.
> 
> 
> >From: Seak <lapidis666-vnc "at" yahoo.com>
> >To: vnc-list "at" realvnc.com
> >Subject: Re: Cannot access IP address from another subnet
> >Date: Mon, 22 Jan 2007 19:00:31 +0100
> >
> >     This is very very odd.  What O/S is in your PC B?  
> Beside PC C can't
> >ping PC B, can PC C open a VNC connection to PC B (normally 
> the answer
> >should be No)?
> >
> >     Have you triggered some firewall by mistake in PC B?
> >
> >Javier Sheh wrote:
> > > Hello,
> > >
> > > I have 3 PC's in 3 different subnets in my intranet.  PC A has IP
> > > address 135.21.42.108, PC B has IP address 135.16.102.30, 
> PC C has IP
> > > address 135.91.108.36.  I loaded RealVNC Free Edition 
> 4.1.1 server on
> > > B.  I loaded RealVNC Free Edition 4.1.1 client on A.  No 
> RealVNC was
> > > on C.  Before loading RealVNC, I was able to ping from A 
> to B and from
> > > C to B.  I established RealVNC connection from A to B.  
> After this, I
> > > tried pinging from C to B, but could not get response 
> from B.  C could
> > > ping anything on B's subnet (e.g. 135.16.102.50, 
> 135.16.102.1) except
> > > B itself.  I rebooted PC A and PC B, but still could not 
> get to PC B
> > > through C.  I tried another PC on subnet same as C and 
> could not ping
> > > PC B either.  Is RealVNC establishing some kind of pipe 
> that prevents
> > > other subnets from accessing a specific server address?  
> What can be
> > > done to clear this problem?  Is there some kind of option I am
> > > overlooking?  Am I closing the connection improperly?
> > >
> > > I have noticed this with two other IP addresses that I 
> used RealVNC
> > > with.  These IP addresses cannot be pinged from a foreign subnet.
> > >
> > > Thanks,
> > > Javier
> >_______________________________________________
> >VNC-List mailing list
> >VNC-List "at" realvnc.com
> >To remove yourself from the list visit:
> >http://www.realvnc.com/mailman/listinfo/vnc-list
> 
> _________________________________________________________________
> The MSN Entertainment Guide to Golden Globes is here.  Get 
> all the scoop. 
> http://tv.msn.com/tv/globes2007/?icid=nctagline2
> _______________________________________________
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit:
> http://www.realvnc.com/mailman/listinfo/vnc-list