Network Resource Problem

[wrj0]

Hi.

 

I‘m experiencing a problem with a Network Resource entry in my ISY994i/IR PRO, ver 3.3.8.

 

This works fine from a browzer: "https://my.dyndns.org:443/rest/vars/set/1/99/1"

 

But, this Network Resource entry fails from the Network Resources Test or when called from an ISY program:

http://dl.dropbox.com/u/46376739/NetResErr.jpg

 

Network Resource returns: "Error: Request failed." and "N/A" in the Resource Response window.

Event Viewer, Level 3 returns: Net-Resource: Failed connecting to my.dyndns.org

Integer Variable #99 does not change from 0 to 1.

 

(Actual Host name and authorization have been changed above, but fail when the identical parameters are used successfully with the REST command. User/password has been verified to be identical to that used to log into the ISY.)

 

Suggestions on what I am doing wrong will be greatly appreciated. Thanks.

[LeeG]

Might try 127.0.0.1. The request from a browser is going from one IP address (PC) to a different IP address (ISY). When the ISY issues the network request it is trying to talk to itself. I am not a network expert by any means but it seems like 127.0.0.1 can be used when trying to communicate with one’s own IP address

[wrj0]

Thanks, Lee.

 

The intent is to use an external path to test Internet connectivity, per this post:

http://forum.universal-devices.com/viewtopic.php?f=26&t=9201&hilit=check+internet

[Xathros]

wrj0-

 

I just checked my setup again and it is still working. I see that I have an extra header in my resource that I don't see in yours that says: "Connection: close" Otherwise all is the same with the exception of Auth, Variable ID and dyndns name.

 

What do you have configured for DNS in the ISY? I'm using 8.8.8.8 but have tested with 4.2.2.2 and 4.2.2.1 which work for me as well.

 

-Xathros

[wrj0]

Thanks, Xanthos.

 

I've tried it both with and without the Connection Close header - same result. Can't seem to find a configuration that does work.

 

The DNS entry in my ISY points to my router which in turn uses the ISP's recommended DNS servers. Good idea, though - I'll do some more playing.

 

Curiously, this was working a day or so after your initial post on how to configure this setup. But, since then I've upgraded from an ISY-99 to an ISY-994, and upgraded revisions in both. So, I don't really know when the response quit working. I do appreciate your input.

[TJF1960]

Thanks, Xanthos.

 

I've tried it both with and without the Connection Close header - same result. Can't seem to find a configuration that does work.

 

The DNS entry in my ISY points to my router which in turn uses the ISP's recommended DNS servers. Good idea, though - I'll do some more playing.

 

Curiously, this was working a day or so after your initial post on how to configure this setup. But, since then I've upgraded from an ISY-99 to an ISY-994, and upgraded revisions in both. So, I don't really know when the response quit working. I do appreciate your input.

I have the same exact problem, was working on my ISY994 in the current rev at the time of the post (I believe it was 3.2.6), then the next rev it only worked sometimes, but most of the time it wouldn't. Since then with later revs it hasn't worked at all for me. I could never figure out why. If you figure it out please post back.

Thanks,

Tim

[Xathros]

Thanks, Xanthos.

 

I've tried it both with and without the Connection Close header - same result. Can't seem to find a configuration that does work.

 

The DNS entry in my ISY points to my router which in turn uses the ISP's recommended DNS servers. Good idea, though - I'll do some more playing.

 

Curiously, this was working a day or so after your initial post on how to configure this setup. But, since then I've upgraded from an ISY-99 to an ISY-994, and upgraded revisions in both. So, I don't really know when the response quit working. I do appreciate your input.

 

There is your problem! The trick here is to AVOID the router's DNS cache at all costs. Set the ISY with a static IP and DNS of 8.8.8.8 and I bet it will work. I bet your 99 was static addressed with external DNS and the 994 is DHCPd. This has worked without fail for me with each and every ISY firmware version 3.2.6 through 3.3.8

 

-Xathros

[wrj0]

Xanthros: I tried 8.8.8.8 with the same result. DNS was setup identically in both the old ISY-99 and the new ISY-994. And both are (were) set to the same static ip address.

Guess I'll keep playing with this occasionally as it is a nice to have function, but not critical.

 

TJF1960: Sure. If I manage to get it working again, I'll certainly post the changes made. I'd really like to find out exactly what changed to stop this from working.

 

Thanks for the ideas, guys!

[Xathros]

Xanthros: I tried 8.8.8.8 with the same result. DNS was setup identically in both the old ISY-99 and the new ISY-994. And both are (were) set to the same static ip address.

Guess I'll keep playing with this occasionally as it is a nice to have function, but not critical.

 

TJF1960: Sure. If I manage to get it working again, I'll certainly post the changes made. I'd really like to find out exactly what changed to stop this from working.

 

Thanks for the ideas, guys!

 

If I had to guess, I'd say something at the router changed. Have either of you upgraded router firmware or changed routers since you had this working?

 

-Xathros

[wrj0]

No router changes on my side.

I did try a couple of other DNS servers in the ISY, but with the same result.

Thanks again for your thoughts.

[Xathros]

Could you try an "nslookup my.dyndnsname.tld" from the command line on your computer and see what the answer is. That may give us a clue.

 

-Xathros

[wrj0]

From both the local PC connected to my ISY-994, and from a remote PC on another network, nslookup resolves the TLD for my dyndns name to the DHCP ip address assigned by my ISP.

[Xathros]

From both the local PC connected to my ISY-994, and from a remote PC on another network, nslookup resolves the TLD for my dyndns name to the DHCP ip address assigned by my ISP.

 

The local PC is the one I'm interested in and what we need to know is where nslookup got it's answer from. Was it the remote DNS server or your gateway address?

 

-Xathros

[wrj0]

The ISP's DNS server: dns-comm-cac-lb-02.southeast.rr.com

[Xathros]

Well that would seem to indicate that the lookup is going outside as we want rather than being cached by your router. Now we just need to figure out why the ISY is not getting through. What do you have for a router?

 

-Xathros

[TJF1960]

I have tried everything I could think of and still cannot get the network resource to get thru.

I just reverted back to 3.2.6 and it works perfectly every time. Then upgraded to 3.3.1 which was the next firmware update and the network resource no longer works. Something changed between the two versions. Could it have anything to do with security certificates?

[wrj0]

OK, thanks. The router is a Linksys WRT160Nv2 that's worked well for the past few years - no changes to it during the time period when the Internet connection test quit working. Port forwarding is in use to connect to the ISY, and both UDP & TCP are enabled for that rule.

 

From a remote PC, this works fine: "https://my.dyndns.org:443/rest/vars/set/1/99/1"

(Also works fine from the local PC)

So, wouldn't that indicate the router is doing it's job properly?

 

Wonder if the way I have configured the Client Certificate on the ISY could be an issue? Generation of the required SSL certificate for the 994 is the only related change that I can find in my notes during the period when this problem started. I used the same procedure described in the Network Security Configuration Guide to create a self signed certificate for both the Server and Client.

Regardless of the Authorization parameters used in the Network Resource (correct user/pw, wrong user/pw, no user/pw), the response is the same.

Network Resource Test returns: "Error: Request failed." And "N/A" in the Resource Response window.

Event Viewer, Level 3 returns: "Net-Resource: Failed connecting to my.dyndns.org"

 

Thanks again for your input, Xanthos.

 

Edit: posted while TJF1960 was posting - seems we both came to a similar conclusion.

[Michel Kohanim]

Hello wrj0,

 

It's quite possible that the server is returning 2xx and ISY considers it a failure since it's not 200. This is a bug in ISY: it has to consider anything in the 200 range as success.

 

With kind regards,

Michel

[wrj0]

Thank you, Michel.

Anything I can do to capture the 2xx response?

[bsobel]

Saw this on another thread and thought of this one, could this be related?

 

"edit: after careful examination of the Dashboard Network settings, my tired old eyes noticed a faint, grey check in the HTTPS Verify checkbox. After UNchecking that box and rebooting the ISY994, all is well now - Prowl is working fine once again."

[wrj0]

Those were my tired old eyes. Prowl's still working fine, thanks.

[Michel Kohanim]

Hello wrj0,

 

You can try Wireshark but since the traffic is between ISY and the network resource, I am not sure how much traffic you can capture. The most important thing is to see what you get back.

 

What you can try is:

1. Clear your Error Log

2. Go to Event Viewer, change the level to 3, run the test

3. Copy/paste the contents of the error log and Event Viewer

 

With kind regards,

Michel

[wrj0]

Thanks again, Michel. Here's the result of the test and Error Log, after clearing the Error Log.

 

Running Test on the Network Resources entry returns a pop up window: "Error: Request Failed."

Resource Window displays: "N/A"

Event Viewer, Level 3 returns: Net-Resource: Failed connecting to my.dyndns.org

Error Log shows:

User: System

Code: -170001

Message: [TCP-Conn] -3/-140002, Net Module Rule: 73

(The Network Resource being tested is ID: 73)

 

I'll try to play with Wireshark when I get some additional time.

[Michel Kohanim]

Hello wrj0,

 

Thank you. 140002 means: Connection timeout (http://wiki.universal-devices.com/index ... r_Messages ).

 

You might want to try increasing the timeout. But, I think something else is blocking ISY from connecting to your server.

 

With kind regards,

Michel

[wrj0]

Thanks, Michel.

I've bumped timeout to 9000 with the same result.

 

At some point prior to my upgrading to the 994 and to rev 3.3.8, this was working. Also, this command still works fine from a browser: "https://my.dyndns.org:443/rest/vars/set/1/99/1" (actual domain name modified for this post)

Wouldn't that imply a proper response from the dyndns server? If so, I'm curious what else may have changed.

 

It seems like both TJF1960 and I started having a similar issue sometime after rev 3.2.6; please refer to his post above in this thread.