ElkRPII wont connect to specific M1XEP

[Rossd]

I could use some fresh ideas.  I am stuck.
 
I have several M1's in my homes.  I have two working computers running identical versions of RPII.  One computer, Win7 can connect to all my M1's yet the second computer in a different state and different ISP can connect to all but one M1.  All  M1's are using a "dyndns.org" IP mask however I have also attempted to connect with the resolved IP.  Mind you the other machine works perfect.
This one machine will not connect, as soon as I select Network, Connect I either get an immediate failure or it takes a few seconds but I end up with:
Connection Error: Count Not Connect"
 
Port not forwarded or URL incorrect or Remote Site down.
 
Well none of those are possible as I can then just connect from the other instance.
 
I have recreated the account from scratch on the nonworking machine = Same error
I have uninstalled and reinstalled RPII= same error
 
This was working fine, I updated to all latest firmares just as an FYI.
 
Would anyone have an suggestions as to what to consider or know if RPII produces some logs somewhere that I can study and try to get to the bottom of this?
 
Really frustrated and any ideas are appreciated.

Ross

 

[elvisimprsntr]

Are you trying to connect to the insecure port or secure port?

When was the last time you upgraded the firmware of your M1, XEP, Keypads, etc?

What OS is on the second computer? A Windows 10 update removed support for older, lower bit depth encryption, thus you must use a older OS to upgrade the Elk firmware before attempting to connect on Windows 10.

 

[Rossd]

Elivis,
I am using secure primarily. However, I have of course tried non-secure port as well.  Both machines are Win 7 Pro. All firmware (per my original post) is current on the device.  Thanks.
Ross

 

[mikefamig]

I would double check the ip address and port number and then try a different dns server.
 
Google Public DNS operates recursive name servers for public use at the following IP addresses: 8.8.8.8 and 8.8.4.4 for IPv4 service, as well as 2001:4860:4860::8888 and 2001:4860:4860::8844, for IPv6 access.
 
Mike.

 

[Rossd]

Mike,
Just a reminder, I used the distinct IP as well as the DNS name of the Elk, both failed identically. That being said, the DNS server IP for all my PC's and XEP is 8.8.8.8 and the internal gateway as a secondary DNS (192.168.2.1).
 
Just a reminder again, one PC can connect to the account fine.  I have even exported the account out of PC #1 and imported it into the PC #2 and attempted to connect.  I get the same connection error. There is something about the account and PC #2 that makes this such a challenge.
 
Something else to note.,  On PC #2, when I try to connect using a non-secure port (2101), The Elk does attempt to "verifying system identity", feels like were about to connect but then eventually fails with "System did not respond, Connection may have been terminated" error box. However unlike the 2601, it felt like it was really trying to authenticate versus an immediate error.
 
Ross

 

[mikefamig]

Maybe an RP2 problem? Have you tried connecting using M1TOGO on the pc that is failing to connect using rp2? It may give a clue.

 

[Rossd]

Mike,
Thank you for the idea.  I tried the latest M1toGo.  As you now we can change the port number in the profile so:
I selected Use Secure Connection checkbox and tried both 2601 and 2101 (default) port. Both returned the same (and similar error to RP)  = "Could not authenticate SSL Connection! Check your profile settings.
 
I then unchecked the SSL box in the profile and tried to connect. No errors and normal connect and communication. I then go back to RP software, check "Connect Non-Secure" and select port 2101.  RP connects normally.
 
At least were getting closer.
 
I however still remain baffled over this as a 2601 connection can be established to other M1's from this PC and we know that PCI can still connect to this M1 as well. I have even gone as far as changing the user name used, making sure there are no spaces or invisible characters in names and ports, no idea still.
 
Ross

 

[Del91574]

AV or firewall an issue? I've had similar with Symantec on one of my machines before

 

[Rossd]

AV or firewall an issue? I've had similar with Symantec on one of my machines before

None at all.  Remember that this RP can connect to three other M1's via 2601, just not this one. It has to be something with the RP software.  I use EK ALarm as an App and that too can connect via 2601. 
 
Exhausting but I do appreciate all the ideas from you all. 

Is there any debugging logs for RP hidden somewhere?
 
Ross

 

[mikefamig]

Are you using the newest version of RP and the newest version of xep firmware?

 

[drvnbysound]

None at all.  Remember that this RP can connect to three other M1's via 2601, just not this one. It has to be something with the RP software.  I use EK ALarm as an App and that too can connect via 2601. 
 
Exhausting but I do appreciate all the ideas from you all. 

Is there any debugging logs for RP hidden somewhere?
 
Ross

I wouldn't suspect AV or FW on the computer that RP2 is on, but rather the FW on the side that the XEP is on.

You were able to connect via M1ToGo (non-secure, 2101), but not 2601. Are you sure that 2601 is open?

http://canyouseeme.org/

You should be able to use that from the the XEP site, entering the port(s) you want to check (specifically 2601). It should return "SUCCESS" if the port is open and being forwarded correctly.

 

[elvisimprsntr]

Try turning off windows firewall?

 

[mikefamig]

When you made changes to RP regarding using non secure port did you remember to send the changes to the panel?

 

[Rossd]

I wouldn't suspect AV or FW on the computer that RP2 is on, but rather the FW on the side that the XEP is on.

You were able to connect via M1ToGo (non-secure, 2101), but not 2601. Are you sure that 2601 is open?

http://canyouseeme.org/

You should be able to use that from the the XEP site, entering the port(s) you want to check (specifically 2601). It should return "SUCCESS" if the port is open and being forwarded correctly.

Because this is a remote M1 i did an external port scan to find 2601 Open, connected over 2601 PC#1 but i did not try a port survey from inside the home. ill report that back once I get an occupant to do that for me.
R

 

[Rossd]

When you made changes to RP regarding using non secure port did you remember to send the changes to the panel?

Yes. No conflicts. Did it multiple times as well.
Ross