| [Modem] Motorola 2210, Linksys WRT54GS and thermostat Let me begin by saying I know just enough to be dangerous when it comes to this networking stuff.
I have a network setup at a cabin so that I can control the thermostat via the internet from my home.
I have a static ip address provided by bellsouth, and a motorola 2210-02 modem connected to a wireless linksys router. I have port forwarding set up on the modem and router. I can access the modem and router remotely, no problem.
Access to the thermostat has been inconsistent /unreliable at best.
The modem is currently set up with a PPPoE, always-on connection. Should IP Passthrough to the router be enabled or would a "bridge" connection be more appropriate for this network. |
|
 heels_fan1.20.09 The start of SocialismPremium
join:2003-02-07
Columbia, TN
kudos:1 | said by markb8304 :
Let me begin by saying I know just enough to be dangerous when it comes to this networking stuff.
I have a network setup at a cabin so that I can control the thermostat via the internet from my home.
I have a static ip address provided by bellsouth, and a motorola 2210-02 modem connected to a wireless linksys router. I have port forwarding set up on the modem and router. I can access the modem and router remotely, no problem.
Access to the thermostat has been inconsistent /unreliable at best.
The modem is currently set up with a PPPoE, always-on connection. Should IP Passthrough to the router be enabled or would a "bridge" connection be more appropriate for this network.
yes bridge the modem, it is always the best when using a 3rd party router |
|
|
|
FAQFixerPremium
join:2004-06-28
Powder Springs, GA
kudos:1 | reply to markb8304
»AT&T Southeast Forum FAQ » How do I properly setup a Motorola 2210 with a Linksys wireless router? |
|
| Ok. Let's say I drove to the cabin, set up the modem and router just as described in the AT&T Southeast Forum FAQ link, and it works perfectly. I'm able to get to the router AND the thermostat with no problem at all. Life is good. 
Then I drive back home, about 90 minutes, and now I can still get to the router but NOT the thermostat. 
What now? |
|
FAQFixerPremium
join:2004-06-28
Powder Springs, GA
kudos:1 | Set up the 2210 to bridged, make sure the correct ports are forwarded on wireless router and you should be fine. It is the most probable issue and the only way to know for sure is try. |
|
| Yep, did that. It's still not working so I'm thinking there may be a more basic problem such as the cat5e connection.
I'm just grasping at straws here because according to everything else it should be working. |
|
 wayjacPremium,MVM
join:2001-12-22
Indy
kudos:1 | Using a dial up connection to trouble shoot the problem will eliminate the driving. |
|
| reply to FAQFixer
I should have said "I think I set up port forwarding correctly"...See the attached...Is it correct? Is there anything else I need to do? |
|
michaeloPremium
join:2002-12-14
Greenville, SC | reply to markb8304
My guess is the thermostat isn't listening on port 8081 that your port forward is going to or it requires for more ports to be open.
To help in troubleshooting the issue can you tell the brand/model number of the thermostat and what software you are using to control it? |
|
| The thermostat comes from a company called Proliphix. (»www.proliphix.com/NT-Basic.aspx) I have the NT10e model.
There's no additional software involved. I've had some support from them but it's been limited in scope (not very tolerant of neophytes) and I think tired of my persistence in trying to get this thing to work with a limited amount of knowledge. |
|
 NetFixerFreedom is NOT freePremium
join:2004-06-24
The 'Boro
 ·Vonage
 ·Cingular Wireless
 ·Comcast
 ·AT&T Southeast
1 edit | Are you using your thermostat in its default DHCP mode, or have you assigned it a static IP address as suggested in the Proliphix FAQs?
»www.proliphix.com/faq_detail.aspx?faq_id=12
Why do I need a DHCP server on my network?
The NT thermostat requires a DHCP server to be present on the network to provide the initial address resolution. Once the NT thermostat has an IP address you are able to access the unit by using your browser.
It is recommended that once you access the thermostat via the web pages, you should set your thermostat to a static IP address. This will ensure that your thermostat will always be at the same IP address when you try to access it.
»www.proliphix.com/faq_detail.aspx?faq_id=13
What else should I know about static addresses?
When your DHCP server gives you an IP address, it is from a pool of available addresses the DHCP server maintains. If you change your IP address method to static without changing the IP address to something outside the pool of available DHCP addresses, the DHCP server may assign another device the same address as your were given from the DHCP server. It is strongly recommended to set your static address outside the range of the DHCP pool. Here’s an example of this process:
If you have a Linksys router, you are most likely going to be given an IP address in the range of 192.168.1.100 to 192.168.1.150. This is because the default setting for Linksys is to have 50 addresses available to the DHCP pool. When you change the thermostat to static, you should set your IP address to something like 192.168.1.50 to 192.168.1.99, this way you will not end up with two devices that have the same address.
Of course, based on the router setup image you supplied, you should assign an IP address between 192.168.2.50 and 192.168.2.99 to your thermostat.
--
A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.
»portscan.dcs-net.net
»nature-pics.com |
|
| I did set the thermostat to a static ip address of 192.168.2.101
What have I done wrong and how do I fix it?
I can't get to the thermostat so is there something I can change in the router to make this work? |
|
NetFixerFreedom is NOT freePremium
join:2004-06-24
The 'Boro Reviews:
·Vonage
·Cingular Wireless
·Comcast
·AT&T Southeast
2 edits | said by markb8304 :
I did set the thermostat to a static ip address of 192.168.2.101
What have I done wrong and how do I fix it?
I can't get to the thermostat so is there something I can change in the router to make this work?
I can't guarantee that you can make it work, but assuming that you still have remote access to the Linksys router, you can do some troubleshooting to see if the thermostat is actually accessible by that IP address.
You can start by going to the Administration/Diagnostics page in the Linksys router and pinging IP address 192.168.2.101 as shown in the images below *. The next troubleshooting step will depend on the results of the ping test.
* I don't have access to that particular router model, and so my screen shots are from the on-line simulator. Therefore your real world screens and results may vary.
--
A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.
»portscan.dcs-net.net
»nature-pics.com |
|
michaeloPremium
join:2002-12-14
Greenville, SC | reply to markb8304
Based on the documentation it looks like the thermostat uses two ports for remote management, an inbound firewall port, port 8081 by default and a web interface port, port 80. Have you tried forwarding port 80 in addition to 8081 or setting both ports to the same value thru the web interface. |
|
| reply to NetFixer
Ping test timed out. |
|
| reply to michaelo
I tried forwarding port 80 and 8081 but no change.
The only way I can get to the web interface (and the thermostat) is to drive 90 minutes to the cabin and work on site. I'm trying to see if I can avoid another unnecessary drive and wasted day.
Even if I were physically there, I'm not sure what the problem is and/or how to fix it. I've been trying to get this thing to work correctly (over the internet) for over a year! Initially there were problems with the dsl line (AT&T was trying everything other than sending someone out to look at the installation); then I discovered I'd configured the modem incorrectly (it's now bridged) and now I'm just shooting in the dark.
I appreciate any/all constructive assistance.
Thanks. |
|
netboy34
join:2001-08-29
Kennesaw, GA
kudos:1 | have you tried putting the internal router config itself on a different port?
I've seen most do remote administration over 8080, but when forwarding 80 it causes issues with the internal interface. When you remote into the router, are you using IP or a domain name (wither registered or Dynamic DNS service) and do you have to put a port behind what you enter? for example mydomain.com:8080? |
|
| to "remote into" my Linksys WRT54GS router , I use my static IP address xx.x.xxx.xxx:8080 |
|
netboy34
join:2001-08-29
Kennesaw, GA
kudos:1 | What I would suggest for testing purposes only, put the thermostat in the DMZ to see if you can then pull up the web interface. try accessing it with just the IP and then with 8081, If it shows then there is an internal config issue, if not then it might be more complicated then it looks... |
|
| Not sure how to do that...
do I enable 192.168.2.101 as the DMZ Host IP Address?
Do I have to do anything else re: port forwarding? |
|
