SUCCESS........almost

Tom Knowlton tom "at" buyersfund.com
Sun Mar 28 08:15:01 2004


Guess what????


I have an open port!!!

GoToMyVNC says Display 1 is 

Checking you out at IP address "205.208.X.X"...

205.208.X.X is not responding on Display 0.

205.208.X.X is accepting connections on Display 1 (TCP port 5901). 

205.208.X.X is not responding on Display 2.

...
...
...

205.208.X.X is not responding on Display 9.

But.....my attempts to connect through the VNC Viewer hav not worked......hmmmmmmm.



BUT.....finally we have met with success!!!!!!!!!!


Tom





---Original Message-----
From: Glenn Lovitz [mailto:lovitzg "at" pogoproducing.com]
Sent: Saturday, March 27, 2004 2:34 PM
To: peter "at" coulter.ndo.co.uk; Tom Knowlton; vnc-list "at" realvnc.com
Subject: [SPAM] - RE: router config to work with VNC - Found word(s)
remove list XXX in the Text body.


This can cause problems on these little routers since they expect to be
routers.  At a minimum you would have to disable all possible NAT and DHCP
functionality.  Even then the switching performance could be seriously
degraded since you are trying to get an OSI layer 3 device to operate solely
on a layer 2 level on the WLAN to LAN network bridge segment (a wireless
access point would have been preferred).  I am also not sure how well DHCP
from the ActionTec would work using the D-Link as a switch -- you may end up
having to assign fixed IP addresses to all your internal PCs.

Looking at the ActionTec documentation
(http://www.actiontec.com/support/broadband/1524.pdf), it may be cleaner to
let the D-Link do it's job by making the ActionTec DSL gateway be just a
modem.  You can accomplish this by changing the settings so that the modem
does "transparent bridging" per instructions in Chapter 5 Advanced Setup, page
39.  This will bypass all routing/firewall functions on the ActionTec.
Technically DSL and cable modems are NOT modem (MOdulate DEModulate) devices
at all, but transparent bridges (the device connects 2 parts of a LAN but is
not seen by either side) with protocol conversion (i.e., aDSL to Ethernet)
that operate entirely in the digital domain.  Modems are analog to digital
devices -- hence MOdulate DEModulate.  But I digress...

Connect to the D-Link wan port as you originally did.  If your ISP uses DHCP
like mine, the external address on the D-Link should automatically be set from
your ISP after a power cycle, assuming you had already specified DHCP on the
D-Link to get an IP address from the ActionTec.  If your ISP uses PPPoE, you
will have to go through the D-Link WAN setup (Chapter 5, pp 15-18) and enter
the username, password, etc.  Now the router, rather than the modem, logs in.
Either way, you will have the equivalent of a standard DSL modem with all
networking controlled by your D-Link wireless gateway router.

NAT and port forwarding should all be handled by the D-Link.  VNC setup should
work fine!

Glenn Lovitz

>-----Original Message-----
>From: vnc-list-admin "at" realvnc.com [mailto:vnc-list-admin "at" realvnc.com]On
>Behalf Of Peter Coulter
>Sent: Friday, March 26, 2004 5:01 PM
>To: 'Tom Knowlton'; vnc-list "at" realvnc.com
>Subject: RE: router config to work with VNC
>
>
>The answer to that is yes ... plug the Actiontec not into the
>WAN port of
>the D-link but into one of the LAN ports! :-)
>Seems like a waste of good router though, but you are then
>literally using
>it as a plain switch!
>
>--------------------------------------------
>Peter Coulter
>--------------------------------------------
>
>
>> -----Original Message-----
>> From: Tom Knowlton [mailto:tom "at" buyersfund.com]
>> Sent: Friday, March 26, 2004 10:49 PM
>> To: peter "at" coulter.ndo.co.uk; vnc-list "at" realvnc.com
>> Subject: RE: router config to work with VNC
>>
>>
>> Isn't there anyway to sort of turn the DLink router into
>> something that behaves more like a hub or a switch??????
>>
>>
>> Tom
>>
>> -----Original Message-----
>> From: Peter Coulter [mailto:peter "at" coulter.ndo.co.uk]
>> Sent: Friday, March 26, 2004 3:39 PM
>> To: Tom Knowlton; vnc-list "at" realvnc.com
>> Subject: RE: router config to work with VNC
>>
>>
>> Tom:
>>
>> The ActionTec 1524R SU is a wireless broadband gateway
>> (modem/router). The Dlink 614+ is a wireless router. This
>> begs the quesiton why you need the D-link router at all?
>> Unless there is some other reason you haven't mentioned that
>> you need the D-link for?
>>
>> To connect to the internet via a DSL connection, and have a
>> home LAN sharing that connection, is fully within the scope
>> of the ActionTec alone (more than enough connectivity with 4
>> x LAN ports PLUS wireless).
>> In fact adding the D-link into the mix is just adding to your
>> configuration difficulties (connecting two NAT routers
>> back-to-back, each DHCP servers, each with wireless!!). For a
>> start you've having to set up port-forwarding in two places
>> when it really isn't necessary.
>>
>> I suggest using the ActionTec alone and see if you can get
>> GoToMyVNC.com to see Display 0 .. 9.
>>
>> --------------------------------------------
>> Peter Coulter
>> --------------------------------------------
>>
>>
>> > -----Original Message-----
>> > From: Tom Knowlton [mailto:tom "at" buyersfund.com]
>> > Sent: Friday, March 26, 2004 8:43 PM
>> > To: peter "at" coulter.ndo.co.uk; vnc-list "at" realvnc.com
>> > Subject: RE: router config to work with VNC
>> >
>> >
>> > Peter:
>> >
>> > I'm grateful for your help.
>> >
>> > A little more on the modem and router:
>> >
>> > Both have 4 ethernet ports.  DLink Router has a WAN port,
>> > which the ActionTec is plugging into right now (using one of
>> > the ethernet ports on the ActionTec).
>> >
>> > The ActionTec is a model 1524R SU.  It is a Wireless-ready
>> > (not being utilized by me) DSL broadband modem.
>> >
>> > ActionTec Vendor Home Page:
>> > http://www.actiontec.com/
>> >
>> > ActionTec Model specific:
>> > http://www.actiontec.com/products/broadband/wireless_ready_dsl
>> > _gateway/wireless_ready_dsl_gateway_specifications.html
>> >
>> >
>> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> >
>> > DLink Wireless Router is a DI 614+.  I need the DLink so I
>> > can transmit the Internet to our laptop, and daughter's
>> > computer upstairs.
>> >
>> > DLink router Vendor Home Page:
>> > http://www.dlink.com/
>> >
>> >
>> > DLink router Model specific:
>> > http://www.dlink.com/products/?pid=20
>> >
>> >
>> >
>> >
>> > =============================================
>> > =============================================
>> >
>> > To answer your other questions (best I can):
>> >
>> > Q:  Is the modem a DHCP server?
>> > A:  Yes.  I turned this OFF once with disasterous consequences.
>> >
>> > In fact, I think DHCP is turned on for both the ActionTec
>> > modem and the DLink router.  I think it is Dynamic DHCP
>> > assigned for both modem and router.
>> >
>> >
>> > IMPORTANT UPDATE on the DLink (LAN) subnet:
>> >
>> > I have changed the DLink router subnet over to 10.x.x.x.  I
>> > did this last night.
>> >
>> >
>> > Q:  I assume also that it is set to automatically acquire
>> > Default Gateway and DNS server information from the ISP
>> >
>> > A:  Not sure.  Seems right.
>> >
>> >
>> >
>> > <<<<<Looking forward to actually getting to the VNC bit!! ;-)>>>>>
>> >
>> > Me too!
>> >
>> >
>> > Right before I went to bed last night I ran the GoToMyVNC.com
>> > against my IP address (205.208.x.x) and Display 0 thru 9 were
>> > NOT OPEN.  :(
>> >
>> >
>> >
>> > Thanks,
>> >
>> >
>> > Tom
>> >
>> >
>> >
>> >
>> >
>> > -----Original Message-----
>> > From: Peter Coulter [mailto:peter "at" coulter.ndo.co.uk]
>> > Sent: Friday, March 26, 2004 1:21 PM
>> > To: Tom Knowlton; vnc-list "at" realvnc.com
>> > Subject: RE: router config to work with VNC
>> >
>> >
>> > Tom,
>> >
>> > You'd need to say a bit more about the ActionTec modem before
>> > I could answer questions on it. Even the model name would
>> > allow a manual to be dragged up online. But your modem must
>> > be slightly different to mine because if I type my external
>> > (dynamic) IP address into IE it doesn't take me to the modem;
>> > the only way I can access the modem via IE is using 192.168.0.1.
>> >
>> > Also, when it comes to mind: Is the modem a DHCP server? The
>> > D-link router will be a DHCP server by default and you cannot
>> > have two DHCP servers on the same subnet or they will likely
>> > be issuing clashing IP addresses. So if both devices are DHCP
>> > servers the facility would have to be disabled in one or
>> > other of them. To me it makes more sense to have the router
>> > as the DHCP sever and thus deactivate the facility in the
>> > modem (if such a facility exists there).
>> >
>> > It's rarely enough just to quote an IP address; usually at
>> > least the sub-net mask but also the default gateway are
>> > necessary to get the whole picture (although in most
>> > small/home LANs the former can be guessed with almost
>> > complete certainty and the latter with a fair degree of
>> > certainty!) So when you say that you have moved the D-link
>> > over to the IP address 192.168.0.2 I assume you mean you've
>> > set the router IP address in the LAN-side set-up pages. I
>> > assume also that it is set to automatically acquire Default
>> > Gateway and DNS server information from the ISP; that will be
>> > how the D-link directs traffic that is not bound for its own
>> > sub-net out onto the Internet, I don't think it really cares
>> > too much about the fact it is going through the modem, it
>> > just dumps stuff out the default gateway as its only known
>> > route to the outside world.
>> >
>> > I must say there are things that get me excited ... but
>> > routers ain't one of 'em! :-) Looking forward to actually
>> > getting to the VNC bit!! ;-)
>> >
>> > Peter
>> >
>> >
>> > > -----Original Message-----
>> > > From: Tom Knowlton [mailto:tom "at" buyersfund.com]
>> > > Sent: 26 March 2004 03:54
>> > > To: coulter; vnc-list "at" realvnc.com
>> > > Subject: RE: router config to work with VNC
>> > >
>> > >
>> > > UPDATE:
>> > >
>> > > 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,
>> > > P
>> > >
>> > > > --__--__--
>> > > >
>> > > > 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:
>http://www.realvnc.com/mailman/listinfo/vnc-list