| View previous topic :: View next topic |
| Author |
Message |
hotrod EVDO Fledgling
Joined: 22 Oct 2007 Posts: 24
|
Posted: Sat Jan 12, 2008 9:12 am Post subject: CTR350 and real VNC (remote control software) |
|
|
Maybe someone can help me out with this one...
I recently added the CTR350 graduating from ICS (love it). I use real VNC to access the home PC's remotely. Everything worked fine prior to adding the CTR350. Here's the setup.
595U in CTR350
CTR350 feeding connection to Linksys WRT54G
WRT54G and an additional Linksys switch for LAN
I changed the CTR350 to port 8081 for remote admin since port 80 is blocked by Sprint. I changed the WRT54G to 8082 for remote admin. I can remotely access the CTR350 on port 8081, but I can't get any further than that. I can't access the WRT54G on 8082 and I can't access any PC's with VNC. I turned the CTR350 firewall off to make sure that wasn't the problem. Still no luck.
Any ideas?
Thanks! |
|
| Back to top |
|
 |
Michael Site Admin
Joined: 13 Jan 2005 Posts: 5132 Location: Cary, IL
|
Posted: Sat Jan 12, 2008 11:23 am Post subject: |
|
|
If you purchased your CTR350 from 3Gstore, give our tech support department a call, they can help. It takes a little extra configuration getting a double NAT or going through 2 routers. _________________ EVDO :: EVDO News :: EVDO Antennas :: Buy Verizon :: Buy Sprint :: EVDO Amplifier |
|
| Back to top |
|
 |
hotrod EVDO Fledgling
Joined: 22 Oct 2007 Posts: 24
|
Posted: Sat Jan 12, 2008 4:46 pm Post subject: |
|
|
I did purchase the CTR350 from 3Gstore. I may just have to try to call them next week to work it out.
Thanks! |
|
| Back to top |
|
 |
hotrod EVDO Fledgling
Joined: 22 Oct 2007 Posts: 24
|
Posted: Mon Jan 14, 2008 4:47 pm Post subject: |
|
|
I'm still trying to get this worked out. If anyone has any suggestions let me know.
I called 3Gstore and tech support tried to help, but this is beyond the scope of what they are willing to support. So, I'm back to relying on the guru's here on the forum.
CTR350 is 192.168.0.1
Linksys is 192.168.1.1
Tech support suggested putting the Linksys on the DMZ. However, the Cradlepoint won't allow anything other than the 192.168.0 subnet.
How can I get the Cradlepoint to forward to port 590X on the 192.168.1 subnet? Any ideas?
Thanks! |
|
| Back to top |
|
 |
visortgw EVDO User
Joined: 28 Oct 2005 Posts: 67
|
Posted: Mon Jan 14, 2008 8:41 pm Post subject: |
|
|
You need to force the CTR350 to forward the appropriate ports to the WRT54G, which I assume is already configured to forward to the individual client machines. To do this, configure the CTR350 as follows:
1) On the Basic / DHCP page, add a DHCP reservation for the WRT54G to lock the WAN IP address that the CTR350 provides to the WRT54G -- this will be on the 192.168.0.x subnet, but within the DHCP IP address range of the CTR350 (e.g., 192.168.0.101, given that my DHCP IP address range is 192.168.0.100 to 192.168.0.199). You will need the MAC address of the WRT54G.
2) On the Advanced / Virtual Server page, add a virtual server for each port that you want to forward from the CTR350 to the WRT54G. For example, you will forward port 8082 for remote admin to 192.168.0.101 (i.e., the WRT54G). Add additional virtual servers for each VNC port that you use, forwarding each to 192.168.0.101.
Try this, and let me know if it works...
EDIT: I have since verified that this works as described with my CTR350 and ASUS router. You might also want to configure the firewall on your VNC nodes to restrict access. |
|
| Back to top |
|
 |
deparson EVDO Junkie
Joined: 30 Aug 2006 Posts: 248
|
Posted: Tue Jan 15, 2008 11:10 am Post subject: |
|
|
I am not a networking guru but why not put either hte CTR or Linksys on a totally different IP address space to avoid confusion/issues.
e.g. set your CRT to run on 10. and your Linksys to serve up 192. addresses. This should allow you to put the Linksys in the CTR's DMZ and insure that all ports are open. If that works you can remove the DMZ and open specific ports to the CRT and see how that goes.
-D
| hotrod wrote: | I'm still trying to get this worked out. If anyone has any suggestions let me know.
I called 3Gstore and tech support tried to help, but this is beyond the scope of what they are willing to support. So, I'm back to relying on the guru's here on the forum.
CTR350 is 192.168.0.1
Linksys is 192.168.1.1
Tech support suggested putting the Linksys on the DMZ. However, the Cradlepoint won't allow anything other than the 192.168.0 subnet.
How can I get the Cradlepoint to forward to port 590X on the 192.168.1 subnet? Any ideas?
Thanks! |
|
|
| Back to top |
|
 |
hotrod EVDO Fledgling
Joined: 22 Oct 2007 Posts: 24
|
Posted: Tue Jan 15, 2008 7:27 pm Post subject: SOLVED!! |
|
|
Everything is now working. Here's the solution (or at least A solution).
See above posts for port information. I guess port 80 (default for CTR350) and 8080 (default for Linksys) are/may be blocked by Sprint.
CTR350 is on 192.168.0.1
Linksys is on 192.168.1.1
CTR350 gives the Linksys an IP address on the 192.168.0.0 subnet. On the CTR350, go to BASIC tab then DHCP and reserve the IP for the Linksys. (Thanks Tom! That was the key.)
On the CTR350 go to ADVANCED tab then FIREWALL. The Linksys MUST be placed in the DMZ. (Thanks deparson!)
Go to ADVANCED tab then ROUTING. Enter the following:
IP address of the local machine hosting VNC. 192.168.1.101
Netmask of 255.255.255.255
Gateway of 0.0.0.0
Interfac LAN (will ultimately be listed as static WAN in the routes list)
Metric 1
Of course, on the Linksys, all port forwarding needs to be entered as well to hit the appropriate local machine.
Hope this helps others.
Thanks everyone,
Hotrod |
|
| Back to top |
|
 |
|