Tom, On reflection after my initial suggestion on Friday evening about using the ActionTec purely as a modem (transparent bridging) and the D-link in it's normal mode I think, if it was me, I would have liked to continue using both devices in their intended default guises, i.e as a modem/router and router respectively. In other words running a sub-net off each (but effectively, in your case, only using the D-link router wireless LAN and ignoring the ActionTec sub-net). But that would entail port-forwarding on both devices which is certainly not the simpliest way to go.
Anyway it looks like it's cracked now. Good luck. -------------------------------------------- Peter Coulter -------------------------------------------- > -----Original Message----- > From: Glenn Lovitz [mailto:[EMAIL PROTECTED] > Sent: Sunday, March 28, 2004 8:25 AM > To: 'Tom Knowlton'; 'Glenn Lovitz'; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: RE: [SPAM] - RE: router config to work with VNC > > > Tom, > > Since you changed to transparent bridge the only way to get back into > ActionTec config will be direct Ethernet connect and 192.168.0.1. > Since you set this option there really is nothing else to do on the > ActionTec side as it is no longer routing, providing DHCP, etc. > 192.168.0.1 will not and should not work through the D-Link. BTW, to > get back into it you will also need to set the PC you are using with a > fixed IP address of 192.168.0.xxx (where xxx=2-254) and specify the > gateway as 192.168.0.1. > > Now you need to complete the D-Link configuration. This also requires > that you use a fixed IP address(es) for the VNC target computer(s). I > have a Netgear, but from your routers docs page 20, looks like you > need to set up what D-Link calls virtual servers. In your case for > VNC, you need 1 per machine for web access and 1 per machine for > viewer access. > Setup for 2 machines as follows: > > Virtual Server 1: Name = VNC5800 > Private IP = 10.10.10.xxx (where > xxx=target machine) > Protocol = TCP > Private Port = 5800 > Public Port = 5800 > Schedule = Always > > Virtual Server 2: Name = VNC5900 > Private IP = 10.10.10.xxx (where > xxx=target machine) > Protocol = TCP > Private Port = 5900 > Public Port = 5900 > Schedule = Always > > Virtual Server 3: Name = VNC5801 > Private IP = 10.10.10.xxx (where > xxx=target machine) > Protocol = TCP > Private Port = 5800 > Public Port = 5801 > Schedule = Always > > Virtual Server 4: Name = VNC5901 > Private IP = 10.10.10.xxx (where > xxx=target machine) > Protocol = TCP > Private Port = 5900 > Public Port = 5901 > Schedule = Always > > Note that since your router does both port forwarding and translation > (re-direction) you specify all your internal ports as 5800 & 5900 > respectively. Connecting to the correct external port should connect > properly internally. Try the first 2 on one computer and see if you > can get to the VNC ports. Also you are using the 205.208.x.x external > address yes? > > I will be really surprised if you are not up and running after this. > > Regards, > > Glenn Lovitz > > >-----Original Message----- > >From: Tom Knowlton [mailto:[EMAIL PROTECTED] > >Sent: Sunday, March 28, 2004 12:02 AM > >To: Glenn Lovitz; [EMAIL PROTECTED]; [EMAIL PROTECTED] > >Subject: RE: [SPAM] - RE: router config to work with VNC - Found > >word(s) remove list XXX in the Text body. > > > > > >Glenn: > > > >I was able to activate Transparent Bridging on my ActionTec, per page > >39 of ActionTec manual (PDF). > > > >So, that is working now...the internet is STILL working (after I > >power-cycled the DLink router, things seemed to clear-up). > > > >A few new problems: > > > > > >1) 10.10.10.2 takes me to my DLink router config (this is okay) > >2) 205.208.X.X (my ISP-assigned static IP address) which used to > >take me to the ActionTec config.....no longer does so. In fact, now > >I have no idea how to get to the ActionTec config short of connecting > >my ethernet cable from the NIC on my PC directly to the ActionTec and > >then perhaps trying the 192.168.0.1 default IP. 192.168.0.1 does not > >work right now with my DLink in the mix...and may not work even after > >I take the DLink out of the loop (which I will not be doing until I > >have a chance to talk to you and Peter C.) > >3) GoToMyVNC still says no Displays are open for VNC. > > > > > >So, I feel progress is being made....just need a little more help. > > > > > >Tom _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
