I have been connecting successfully but today local App says the Classic is not available.
I can connect to the router, and it shows the classic as one of the connected devices.
I am also getting data on MyMidnite.
Any ideas?
BTW - it might assist some folks - I am using a Bell Netgeat cellular modem/router, and after trying to set it up using dynamic DNS, I arranged with Bell for a static IP address ( $10/mo) and it immediately connected and has been working nicely.
Quote from: Bob D on July 04, 2014, 03:27:24 PM
I have been connecting successfully but today local App says the Classic is not available.
I can connect to the router, and it shows the classic as one of the connected devices.
I am also getting data on MyMidnite.
Any ideas?
BTW - it might assist some folks - I am using a Bell Netgeat cellular modem/router, and after trying to set it up using dynamic DNS, I arranged with Bell for a static IP address ( $10/mo) and it immediately connected and has been working nicely.
How are you connected to the Classic ? Wireless, hard wired into a router, directly to a computer?is the Classic set to a static IP or DHCP?
This is a known lockup that require the Classic to be rebooted (power off and back on).
BTW For MYMidnite the dynamic DNS section in the manual is way out of date and is no longer required. Nor should a static IP from your ISP required to connect to MyMidnite. IFIRC the second entry for D2 in the Network section should be all zeros (0.0.0.0).
The connection from the Classic to the router is hard wired, with a static IP.
I am getting current data from mymidnite, so it seems that the classic is connected and is sending data.
The issue is that I cannot connect to the classic via the Local App running from a remote computer.
Quote from: Bob D on July 05, 2014, 03:50:36 PM
The connection from the Classic to the router is hard wired, with a static IP.
I am getting current data from mymidnite, so it seems that the classic is connected and is sending data.
The issue is that I cannot connect to the classic via the Local App running from a remote computer.
When the LA first comes up and does not connect try clicking on Applications and then Configuration menu and Remove the current entry and then add the static IP address of the Classic back in and make sure the port is set to 502.
If the LA still doesn't find the Classic turn the PV Breaker off and then the Classic Breaker off. Turn the Classic breaker back on and then the PV breaker back on after the Classic has finish waiting. Now restart the LA and see if it will connect.
BTW what are the firmware versions and dates for Classic, MNGP, and Network?
Thanks
I had already tried the delete/add, to no effect.
The firmware is up to date, although getting the version numbers, as well as resetting, will have to wait a few days until I visit the cottage again.
I am having a similar problem with W7.
I connect with the 2 classics and then try to connect to another router , \NO GO...
to trouble shooting and it tells me hat DHCP is not set, let troubleshooter fix it and away we go to the \net, but not back to the Static Classics. ?????
I am beggining to hate the static/DHCP issue....
I forgot to add that you have to reset again twice when you want to go back
Quote from: Westbranch on July 05, 2014, 08:27:32 PM
I am having a similar problem with W7.
I connect with the 2 classics and then try to connect to another router , \NO GO...
to trouble shooting and it tells me hat DHCP is not set, let troubleshooter fix it and away we go to the \net, but not back to the Static Classics. ?????
sorry WB but this does not make sense... are you moving a W7 laptop between two different networks?
Or have you two routers? one connected to internet and home LAN, the other to the 2 classics?
dgd
both are sort of correct
#2 is most accurate
t2 routers
DHCP satellite internet plus
2 Classics connected to a router set to static
Quote from: Bob D on July 05, 2014, 04:14:55 PM
Thanks
I had already tried the delete/add, to no effect.
The firmware is up to date, although getting the version numbers, as well as resetting, will have to wait a few days until I visit the cottage again.
Bob D,
Just to clarify, you are trying to connect using the Local App while on your local network at your cabin correct?
And Westbrabch is correct. According the Midnite ever time you change the IP configuration on the Classic it will require a reboot of the Classic.
Quote from: Westbranch on July 05, 2014, 10:48:52 PM
both are sort of correct
#2 is most accurate
t2 routers
DHCP satellite internet plus
2 Classics connected to a router set to static
just use one router with:
WAN port to satellite internet connection
two of the LAN ethernet wired ports to the Classics or if they far away use one cable and a small hub near classics (NOT a router BUT a hub)
wireless LAN talks to laptop
Set dhcp server in router to ON so it issues IPs to devices that need them and make sure wireless ethernet in laptop is on.
Set Classics for DHCP
Can you try this?
dgd
Quote from: Resthome on July 06, 2014, 12:34:02 AM
Quote from: Bob D on July 05, 2014, 04:14:55 PM
Thanks
I had already tried the delete/add, to no effect.
The firmware is up to date, although getting the version numbers, as well as resetting, will have to wait a few days until I visit the cottage again.
Bob D,
Just to clarify, you are trying to connect using the Local App while on your local network at your cabin correct?
And Westbrabch is correct. According the Midnite ever time you change the IP configuration on the Classic it will require a reboot of the Classic.
Resthome: No, I am trying to connect to the classic at the cottage remotely from home.
I can:
- connect from home to the cottage network, where I can log in and I see that the classic is connected
- Obtain data (from home) through mymidnite - I think this means the classic is connected to the cottage network and is passing information
But when I run LocalApp from home, it says the classic is not available
except for a couple of minutes ago, when the classic was found, and I have access.
No idea why.
But thanks for the suggestions, and sorry for wasting the bandwidth
<edit> after further checking, it looks like I didn't save the router configuration when I opened port 502.
I think things corrected themselves after I remotely set the router to open 502.
Quote from: Bob D on July 06, 2014, 09:59:30 AM
Quote from: Resthome on July 06, 2014, 12:34:02 AM
Quote from: Bob D on July 05, 2014, 04:14:55 PM
Thanks
I had already tried the delete/add, to no effect.
The firmware is up to date, although getting the version numbers, as well as resetting, will have to wait a few days until I visit the cottage again.
Bob D,
Just to clarify, you are trying to connect using the Local App while on your local network at your cabin correct?
And Westbrabch is correct. According the Midnite ever time you change the IP configuration on the Classic it will require a reboot of the Classic.
Resthome: No, I am trying to connect to the classic at the cottage remotely from home.
I can:
- connect from home to the cottage network, where I can log in and I see that the classic is connected
- Obtain data (from home) through mymidnite - I think this means the classic is connected to the cottage network and is passing information
But when I run LocalApp from home, it says the classic is not available
except for a couple of minutes ago, when the classic was found, and I have access.
No idea why.
But thanks for the suggestions, and sorry for wasting the bandwidth
<edit> after further checking, it looks like I didn't save the router configuration when I opened port 502.
I think things corrected themselves after I remotely set the router to open 502.
Yes, that would do it. Port 502 has to be open in both directions on the router or any firewall you have in place if you are using the local app across the internet. Glad you got it working. Just be aware the Classic only excepts one network connection plus the MyMidnight connection which is fixed and encrypted for security. The LA is not encrypted.