apex wireless

[RussM]

I didn't want to run my "N" network as "G" just to make the Belkin product to work.

Not true! This is a case of transference from the days when 802.11g was new. 802.11b clients could cause a slowdown of an 802.11g WLAN (although the impact was seriously exaggerated by the media.) 802.11g and 802.11n both have protection mechanisms built-in to accommodate this, reducing the issue to near-insignificance. Basically, you've stated a myth

 

[wells284]

I ended up going with the wga54g. I found a friend who had one. thanks for everyone's input and ideas.

The next problem... I got everything hooked up and working last night. Took me about 3 hours and get the dang wga54g to work. It would have been about 2 hours if I would have reset the apex. that solved that problem immediately. I then set up an account at dyndns and programed that into my router.
I then went to http://apex and was able to see all my info and that was working. Then, I used my i-phone to pull up my host name site that I created on dyndns. This worked and I was thrilled that I finally got everything running. I even turned a couple actinics on in my tank to verify that it was working.

Sooo this afternoon I pull it up to show off and it will not load (on my iphone) The same address as last night and I get nothing. I even made it a home screen icon last night for a direct link to it, and it still doesn't work. It times out and says "safari could not open the page because the server stopped responding."

So why would it not work 10 hours later after it worked completely fine??

(sorry about the novel)

 

[goochesfish]

The IP address changed. Go to whatismyip.com
and I bet it's different than before.
I thought opening the dyndns.com account is supposed to help with that problem?

 

[rkelman]

How did you setup dyndns? Did you download the application to update your domain with the new ip as it changes or did you set it up in the router to do that? The problem is most likely in the updating process to dyndns.

 

[wells284]

How did you setup dyndns? Did you download the application to update your domain with the new ip as it changes or did you set it up in the router to do that? The problem is most likely in the updating process to dyndns.

When I created it, I set it to auto detect Ip address on dyndns. Then in my router, I put in my username, password and my host name for the site.

 

[wells284]

The IP address changed. Go to whatismyip.com
and I bet it's different than before.
I thought opening the dyndns.com account is supposed to help with that problem?

I checked that and it is still the same

 

[cediss]

Re: apex wireless

One thing to consider, where you accessing the Apex via the iPhone via your home wireless initially and then when "trying to show off" accessing off the home network? The remote access will be different from your LAN access address. Just a thought as this is easily overlooked mistake.


Sent from my iPhone using Tapatalk

 

[wells284]

One thing to consider, where you accessing the Apex via the iPhone via your home wireless initially and then when "trying to show off" accessing off the home network? The remote access will be different from your LAN access address. Just a thought as this is easily overlooked mistake.


Sent from my iPhone using Tapatalk

My iphone was not connected to my home network at the time. Anything that is connected to my home network can connect with the apex. It is just when I exit that network that it does not work. That is when I try to use my domain name at dyndns to connect, but it does not work.

 

[wells284]

I know it has to do with the Dyndns network setup, but I do not know for sure what it is

 

[wells284]

When I look at the router information under ddns, it has my username password and domain name correct. Then were it says status it says update success- no change. Shouldnt that say connected or something?

 

[cediss]

Re: apex wireless

I not sure how to solve your problem. Just wanted to be sure you knew that the address you access from home is different from the address you acces remotely. If your phone is set to connect to network it will be connected unless you disabled it. You probably already know this but it sounded like it could be your problem, and if not someone else reading this could benefit if they are having this issue. Good luck!


Sent from my iPhone using Tapatalk

 

[slief]

DynDNS has a piece of software called DYNDNS Updater that you load into one of your home systems. It will update the home IP to DYNDNS site hourly or at a regulated interval. Most DSL setups dont have static IP addresses. As such, your IP address can change daily or more or less. The app for the computer resolves that issue and updates the DYNDNS servers of any address changes on your network.

I am using DYNDNS as well but I also loaded the app on one of my home systems and all works perfectly.

Also, you mentioned iPhone. If you go to the appstore and search for Neptune or Aqua Notes, there is a free version of Aquanotes for the iPhone. It works great for monitoring your system from anywhere. You just give it your dyndns address and your done. The web interface is a bit combersome on the iphone.

One last thing. Make sure your router is set up to route port 80 to the IP address of the controller. I ended up setting my Aqua Controller to a static IP as well but did that after I had everything working.

That said, there are 2 things you need to look at:
First, the app that runs on one of your system to update the IP info. If you go to DynDNS and select the support tab, the download will be at the top right corner. It is a must unless your DSL is a Static one which is highly unlikely. You pay extra for that.

Second is the port forwarding in your DSL router. That is how you get to the controller through your firewall from the web. Both are essential and without addressing both, you will not get it working.

 

[wells284]

well I played with some settings today and was able to get access from an outside network, but now i cannot access it from my network. the ip address of 192.168.1.50 would not work so i changed the last 2 numbers to 3. With those last two numbers changed to three different numbers in my router and on the apex I am able to access it from an outside network via aquanotes and my dyndns account. I cannot access it home via the new ip address or http:// apex or via my dyndns account.

Also since I changed it, my apex controller has been freezing on different screens for 5-15 seconds. That is probably coincidence though. :worried2:

 

[cediss]

Re: apex wireless

You shouldn't have to do tis normally when connecting within your LAN, but this worked for me when I had a similiar problem. Add the :# (port #) to the address (eg: 192.168.1.50:80) in your browser. Make sure Auanotes has the right port number as well.


Sent from my iPhone using Tapatalk

 

[wells284]

You shouldn't have to do tis normally when connecting within your LAN, but this worked for me when I had a similiar problem. Add the :# (port #) to the address (eg: 192.168.1.50:80) in your browser. Make sure Auanotes has the right port number as well.


Sent from my iPhone using Tapatalk

I tried that and it did not work. My apex ip address is actually 192.168.1.XXX. It would not connect me from an outside network so I changed the address from .50 to xxx. After that I could access it from aqua notes and from my dyndns account when I was not on my own network. When I am on my network I cannot reach it from my dyndns account nor http://apex nor 192.168.1.xxx

 

[rkelman]

What do you have your gateway set to in the apex? You are restarting the apex after making network changes right?

 

[slief]

Sounds like you have an IP conflict with another device on your network. I hope you are just not telling the address of your apex and didnt use XXX instead of a number.

Your subnet should be 255.255.255.0

Set your Apex to DHCP. Restart it. Note the IP address that your router provided it. Then go back into the Apex and set your IP back to static using the same IP that it was using when set to DHCP. Restart the Apex. Then go into your router and modify the port fowarding so that it matches the IP address of the Apex.
That should resolve your internal network issue. Also, make sure your other computers are set to the same subnet mask on your internal network. Not all DSL routers are set using a 192.168.1.xxx IP range. Also, make sure the gateway on the Apex is that of your router. In DHCP mode, it should be.

 

[tamu]

Set your Apex to DHCP. Restart it. Note the IP address that your router provided it. Then go back into the Apex and set your IP back to static using the same IP that it was using when set to DHCP.

This might not be the best idea. Your router will more than likely give out that same IP address when the DHCP lease is up if another device that is DHCP is brought onto the network. The router will not have any idea that you have 'used' that IP on your own unless you make a DHCP reservation.

The best thing to do is look at the range of DHCP addresses in the router and go with one that is out of the range. So, if your DHCP range is 192.168.1.2 - 192.168.1.50 then go with 192.168.1.51 for your Apex.