router config to work with VNC
tfseak "at" futurmaster.com
Fri Mar 26 14:23:00 2004
I'm afraid you misunderstood what he meant. Since your Dlink device is a router, not a switch, the network segments on both side of it should have different addresses.
In other words:
* the segment between modem and the router has an address of, for example, 192.168.0.0/255.255.255.0
Actually, I think 192.168.0.x is assigned by the modem because in this segment, the modem acts as a DHCP server while the WAN port of the router acts as a DHCP client.
* the segment between the router and the PC's has an address of, for example, 192.168.1.0/255.255.255.0
In this segment, the router is DHCP server while your PC's the client.
Then configure your modem as well as your router and you should make it work.
> -----Message d'origine-----
> De : Tom Knowlton [mailto:tom "at" buyersfund.com]
> Envoyi : vendredi 26 mars 2004 04:54
> @ : coulter; vnc-list "at" realvnc.com
> Objet : RE: router config to work with VNC
> I moved my DLink router IP over to 192.168.0.2
> Now when I type 192.168.0.2 it takes me to the DLink Router config (as expected)
> When I type in my static IP address (205.208.XXX.XXX) it takes me to my ActionTec
> broadband modem config....is that right?
> Now, there is still another IP address, isn't there? The one that my DLink is using to
> connect to my ActionTec modem. That is the part I am not sure about.
> So I need an answer to that part, plus I still need to get VNC working.
> But the good news is that for the FIRST TIME....I can get to the firewall config for both my
> DLink Router and my ActionTec broadband modem WITHOUT having to disconnect any
> cables. I'm so excited.
> -----Original Message-----
> From: coulter [mailto:coulter "at" coulter.ndo.co.uk]
> Sent: Thursday, March 25, 2004 6:36 AM
> To: vnc-list "at" realvnc.com
> Cc: Tom Knowlton
> Subject: RE: router config to work with VNC
> As noted by other posters your diagram is incomplete.
> However what if does tell me is that you have two devices - namely the Actiontec modem
> and the D-link router - with the same IP address namely 192.168.0.1 (you say it in words in
> some of the supporting text but it is not shown in the diagrams).
> First you can't have two devices with the same IP address and not expect problems.
> Plus your Dlink must be getting very confused -- it's supposed to be a router, by definition a
> router routes! Usually between different sub-nets!! :-)
> But as it is seeing the same IP address 192.168.0.1 on each of its port (both WAN-side and
> LAN-side) it's likely not a happy bunny.
> For me the easiest way to solve this is to put the modem and the router on different sub-nets
> as follows:
> leave the modem on 192.168.0.1 (the 192.168.0.0/255.255.255.0 sub-net) and put the
> router on a completely different sub-net. So that it is very clear which is which make them
> very different, thus I suggest putting the router on the 10.0.0.0 / 255.255.255.0 (although
> really anything other than 192.168.0.x will do). The router being the DHCP server then
> dishes out LAN IP address to this revised sub-net. The very first consequence of this will be
> that you can access both devices via IE using their now different IP addresses without
> having to be disconnect the devices every now and again! ;-)
> Once you get this difficulty between modem and router sorted you may be able to progress
> with VNC issues. Set up port-forwarding on each device now as appropriate.
> Good luck,
> > --__--__--
> > Message: 14
> > Subject: RE: router config to work with VNC
> > Date: Wed, 24 Mar 2004 17:13:21 -0700
> > From: "Tom Knowlton" <tom "at" buyersfund.com>
> > To: "Scott C. Best" <sbest "at" best.com>, <vnc-list "at" realvnc.com>
> > Does this diagram help any? (until I can get Kaboodle up and running)
> > http://www.knowltonfamily.com/config_port_forward.gif
> VNC-List mailing list
> VNC-List "at" realvnc.com
> To remove yourself from the list visit: