simple yet finding it difficult to do question

Patrick,

I picked up a couple of tricks from your thread. In case someone can chime in... Here's what I've got going;

Actiontec 701WG DSL Modem (Qwest Provider (No blocked ports)
WAN: PPPoA
IP: 71.36.xx.xxx
Mask: 255.255.255.255
Gateway: 67.41.38.194
DNS #1: 205.171.3.65
DNS #2: 205.171.2.65
LAN
IP: 192.168.0.1
Mask: 255.255.255.0
DHCP: on

Port forwarding set as such;
100-100 tcp 192.168.0.5
80-80 tcp 192.168.0.5
100-100 udp 192.168.0.5 (Trying all combinations)
100-100 -GRE 192.168.0.5 (Trying all combinations)

AC3:
LAN
IP: 192.168.0.5
Mask: 255.255.255.0
Gate: 192.168.0.1
Port: 100

Using CanYouSeeMe: (Thanks for the tip)
Success: I can see your service on 71.36.XX.XXX on port (100)
Your ISP is not blocking port 100

I've pulled everything else out. Originally I had another wireless router hooked between the modem and computer and AC3. Now we simply have the modem going to a 10meg hub (it's what I had) with the computer and AC3 connected to the other ports.

I can hit the AC3 on the LAN and through Aquanotes all day long, I just can't get in from the outside to save me!!! Doing a direct attempt with http://71.36.xx.xxx:100 just gives me a "Cannot Display" webpage. I think I tried the dmz method and it didn't work, but I will give it another shot.

Until I just tried the CanYouSeeMe, I was assuming my modem wasn't forwarding anything. It might not be, but there has got to be something simple I'm overlooking.

Any thoughts anyone?

Thanks Patrick for letting me hijack your thread...
 
Last edited:
<a href=showthread.php?s=&postid=8000287#post8000287 target=_blank>Originally posted</a> by dougchambers

Actiontec 701WG DSL Modem (Qwest Provider (No blocked ports)
WAN: PPPoA
IP: 71.36.xx.xxx
Mask: 255.255.255.255
Gateway: 67.41.38.194
DNS #1: 205.171.3.65
DNS #2: 205.171.2.65
LAN
IP: 192.168.0.1
Mask: 255.255.255.0
DHCP: on

Port forwarding set as such;
100-100 tcp 192.168.0.5
80-80 tcp 192.168.0.5
100-100 udp 192.168.0.5 (Trying all combinations)
100-100 -GRE 192.168.0.5 (Trying all combinations)

AC3:
LAN
IP: 192.168.0.5
Mask: 255.255.255.0
Gate: 192.168.0.1
Port: 100

Doug,

I'm just a noob in the networking field but it appears your mask on the WAN side is a bit screwy. I would think your subnet mask should be 255.255.255.252 (or something other then 255 for the last octet). Your default gateway is out of the range as well.

As far as the AC3 goes.. the default port is 80 (for http) traffic. I'm not sure what is running on 100 but you shouldn't need port 100 from what I have seen so far.

Which router are you using?

ISP -> Actiontec 701WG -> Router -> AC3 / Computer(s)

Joshua
 
Joshua,

I'll double check the WAN side, but it's defined by Qwest so I don't really have much I can change on that side.

I changed the port on the AC3 to 100 just to get out of the 80 range in case I was getting port blocking. Qwest assures me that they don't port block anything so I can change it back. I know I tried it as the default and it still didn't help.

I pulled the router completely out of the equation to try and minimize "opportunities" for setting things wrong. If I could get anything through, I'd like to put the router back in, but KISS is the name of the game for now.

Here is the path;

ISP -> ActionTec DSL Modem -> Hub -> Computer (192.168.0.2)
-> AC3 (192.168.0.5:100)

In another thread I found on a Gamer site, they mentioned that Cisco VPN clients could cause problems even when they weren't running. I checked my VPN and it's by Novel. I looked through the menus and didn't see anything about running in the background or blocking. Really it shouldn't matter if I'm forwarding right out of the modem into the AC3?

Thanks,

Doug
 
Doug,

Here is the issue. right now you don't have anything to allow your data to flow from the DSL line to the AC3. Also your setup is a bit off.

DSL > Router > AC3 (The wired has four ports as well so you want to plug in the Computer into one of the remaining ports.

I would suggest BEFSR41 $50.00 at Best buy or most eletronic stores or WRT54GS $50-$70 if you want Wireless.

The router is what does all of your "Routing" of ports and IP addresses. With the hub in place you cannot get to your AC3 from the outside because it has no idea how to get outside using the hub. Put in one of the linksys routers and I'm sure that explorer364 can post his final config.

I wish I had better news but that explains why you haven't had any luck so far.

Joshua
 
Joshua,

Thanks, but we tried the router method and had the same exact results. I started with a Netgear and even picked up a Linksys WRT54GS just in case there was something else going on with the Netgear.

Here was my original setup with the Netgear and Linksys solution. I thought the problem was associated to the subnets or a DHCP conflict between the router and modem, but never could get it to resolve. Hence we tried pulling the router out of the equation.

Modem
LAN IP: 192.168.0.1
Mask: 255.255.255.0
DHCP - Sees the Router as 192.168.0.2
Port Forward set as 80/80-TCP 192.168.1.1

Router:
LAN IP: 192.168.1.1
Mask: 255.255.255.0
Gate: 192.168.1.1
Port Forward set as 80/80-TCP 192.168.1.5

Computer:
LAN IP: 192.168.1.2

AC3:
LAN IP: 192.168.1.5
Mask: 255.255.255.0
Gate: 192.168.1.1
DNS #1: 192.168.1.1
Port: 80

An interesting note what that when I setup the dynDNS in the router and had it update the server, it would always update with the IP of the Router and not the WAN IP.

For the sake of trying to get this figured out, let's assume I know nothing about networking and I'll try just about anything at this point.

Here were some original threads,

http://www.reefcentral.com/forums/showthread.php?s=&threadid=906352

http://www.reefcentral.com/forums/showthread.php?s=&threadid=905533
 
Doug,

Alright Lets try this.

Reset your LinkSys to Factory Settings.

Once you plug it back in it should be at 192.168.1.1 (I believe is default). Plug your computer into it and you should pull 192.168.1.100 (or 101).

If your DSL Line is setup to use PPPoE you will need to setup the settings on your LinkSys (or possible upgrade the firmware to the latest version).

Your DSL "Modem" shouldn't have an IP address. It should pass thru your internet address (http://www.ipchicken.com).

External (Internet IP Adddress)
IP Address: xxx.xxx.xxx.xxx
Subnet Mask: 255.255.252 (or possible 248 depending on how many IP Addresses your ISP provided you)
Default Gateway should be a few numbers off of your IP Address... Gateway could be 12.3.4.5 and your internet IP address would be 12.3.4.6 (Just as an example)

Internal (Home/Private Address)
Router: 192.168.1.1
Subnet Mask: 255.255.255.0
Default Gateway 192.168.1.1

You need to change the IP Address of AquaController to fall into the 192.168.1.2-254 range if you changed it from Default. DHCP is enabled by default on the Router so you will want to choose something .2 - .99 so it doesn't conflict with another address.

AC: 192.168.1.50 (Default on the AquaController)
Subnet 255.255.255.0
Default Gateway 192.168.1.1

Computer (DHCP) Should pull 192.168.1.100 (or 101)
Subnet Mask 255.255.255.0
Default Gateway 192.168.1.1

Once you are at a "Basic" config we can work on getting you working. At that point you should be able to access the internet as you normally does.

I'm wondering why you have two IP Ranges.. 192.168.0.x and 192.168.1.x I haven't done the research on the DSL Modem you are using but if it has DHCP and any other features you might want to disable them and let the LinkSys router do everything.

by default the DSL Modem won't know how to route from 192.168.0.x to 192.168.1.x. If I get time tonight I will check out the info on yours or one of the guys from Neptune Systems will chime in.

Joshua
 
<a href=showthread.php?s=&postid=8003463#post8003463 target=_blank>Originally posted</a> by dougchambers

Modem
LAN IP: 192.168.0.1
Mask: 255.255.255.0
DHCP - Sees the Router as 192.168.0.2
Port Forward set as 80/80-TCP 192.168.1.1

The modem should be forwarding to 192.168.0.2 (the router's WAN IP on the modem's LAN), not 192.168.1.1
 
Lauren,

I've tried so many things, but if I recall, I setup a port forward in the router to port 80 or 100 (tried both) and then tried hitting the AC3 direct with the following 192.168.0.2:80 (or :100) and it didn't see the AC3. Shouldn't the router have picked up the port forward or would it have been looking for it to come from the modem side?

Joshua,

The modem is setup for PPPoA.

As soon as I turn off the DHCP on the modem, I loose all contact with the modem GUI. I'll see if there is a way to turn the routing off on the modem and let the router assign it an IP.

I'm wondering why you have two IP Ranges.. 192.168.0.x and 192.168.1.x I haven't done the research on the DSL Modem you are using but if it has DHCP and any other features you might want to disable them and let the LinkSys router do everything.

by default the DSL Modem won't know how to route from 192.168.0.x to 192.168.1.x. If I get time tonight I will check out the info on yours or one of the guys from Neptune Systems will chime in.

By default the modem wants to be on the 192.168.0.X sub, but all of the routers want to be on the 192.168.1.X. I tried changing the modem over to the .1.X sub, but it didn't like talking to anything which might have been the DHCPs conflicting. I thought if I created a port forward in the modem from the external IP to the router IP and then from the router to the AC3 it would all work. Evidently it doesn't.

-Doug
 
It sounds like your DSL modem has a few things built in. I was call the provider and see if you can get a basic no extras DSL modem.
 
doug's dsl modem, has a built in router... hence the hub. When he plugs in another router i.e. the linksys or the netgear.. the dhcp of the two units conflict. the netgear wants to be on 192.168.1.1 and doesn't want to change to 192.168.0.X. The actiontec modem/router shuts down all router functionality when dhcp is turned off, and that might be doug's solution. Turn it all off, set either the netgear or linksys in behind it, and see what happens. In effect hobble the actiontec to only be a modem.. however, the actiontec is the problem for port 80, when you try and http to doug's address the actiontec picks it off and drops you right in the gui for it. In the setup for the modem/router, you can turn off remote management, but that didn't stop it from letting us in via http outside of the lan.
 
<a href=showthread.php?s=&postid=8004395#post8004395 target=_blank>Originally posted</a> by jleichtman
It sounds like your DSL modem has a few things built in. I was call the provider and see if you can get a basic no extras DSL modem.
I may be stopping and picking up a Motorola SurfBoard and converting to Cable tonight... The Actiontec is the ONLY option from Qwest that I'm aware of...
 
Now we may be getting somewhere!

Tonight I came home and put the modem into transparent mode with DHCP disabled. Installed my Netgear router (Linksys still available) and ran through the setup routine on the router again.

This time the router tagged the modem as PPPoE so I entered the login and password information. I can talk to the computer, internet, and AC3, but still haven't gotten through to the AC3 from external. It feels like I'm closer, but not quite there. What do I need to look at next???

Here are the details;

NetGear
Internet Port
IP: 168.103.XXX.XXX
DHCP: PPPoE
Mask: 255.255.255.255
DNS: 205.171.3.65 and 205.171.2.65

Lan Port
IP: 192.168.1.1
DHCP: On
Mask: 255.255.255.0
DHCP: Enabled 192.168.1.2-192.168.1.51

Port Forward
Service Name: HTTP
Start Port: 80
End Port: 80
Server IP Address: 192.168.1.55

Computer
IP: 192.168.1.2

AC3
IP: 192.168.1.55
Mask: 255.255.255.0
Gate: 192.168.1.1
DNS: 192.168.1.1 and 205.171.3.65
Port: 80

www.canyouseeme.com can see port 80 when I have port forwarding turned on. It doesn't when I have forwarding turned off.

Can anyone throw me a bone to get this last part worked out? As a worst case, I picked up a cable modem on the way home and can start from scratch, but I'm thinking that now with the DSL in transparent mode, it would look pretty much the same to the router.

Thanks everyone!

Doug
 
It could be that your ISP is blocking port 80. Try port forwarding tcp port 23 to the AquaController's port 23. You should then be able to telnet into the controller remotely. You can't have AquaNotes running if you do this.
Also upgrade to the beta version 3.1 of the AC3 firmware - available on the www.neptunesys.com/manuals.htm. Then map port WAN port 2000 to the AquaControllers IP port 2000, and setup the AquaControllers web server port port 2000.

Curt
 
Viola!!!!! We are in!

Curt - I had already updated the firmware and Aquanotes versions over the weekend. After trying everything I could think of with my NetGear router, on a whim I threw in the new LinkSYS I picked up over the weekend. While it should work the same, there is something about the port forwarding section that is working now where the NetGear wouldn't. I even took the LinkSYS back out and loaded the NetGear with the same settings and it still didn't work. For some reason, obviously my own, I couldn't get the NetGear to roll over the forwarding. Technically, it wouldn't hit the HTTP 80 direct.

Final configuration;

Actiontec DSL Modem:
- Mode: Transparent
- DHCP: Disabled
- Port forwarding: None

LinkSYS Router:
- Mode: PPPoE
- Port Forward: HTTP 80/80 to 192.168.1.55
- DHCP: Enabled

Computer:
- Auto

AC3:
- IP: 192.168.1.55
- Mask: 255.255.255.0
- Gate: 192.168.1.1
- DNS: 192.168.1.1
- Port: 80

Now to talk to David about his website and return a new Motorola Surfboard cable modem...

Thanks again everyone and if you are interested in a NetGear wireless Router, let me know!

-Doug
 
Doug,

Very happy to hear it is working. I have to say I have had nothing but trouble with NetGear stuff.. hence why I switched to LinkSys many moons ago.

I'm getting ready to move down to Tampa on the weekend of September 8th and hopefully will be able to setup my new tank soon.

I think its almost time ot order the AC3Pro :D

Joshua
 
Back
Top