ElkRPII wont connect to specific M1XEP

[Rossd]

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

Yes

 

[giesen]

Is it possible the stored username/password is wrong for that one site in the one RP2 instance? That might explain everything.

Sent from my SM-N910W8 using Tapatalk

 

[Rossd]

Cocooner,
I tried your idea.  I went into the XEP and added a brand new user name and pw, "test/test", I then uploaded the change and rebooted the XEP.  In the RP, I disabled the non-secure and changed the Port to 2601>Same Fail
 
Went back to 2101 and it connected.
 
.....exhausting...
 
Thank you for the idea however,
Ross

 

[Del91574]

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.

I've had this problem happen on multiple machines with FW and AV being the culprit, including my own home.
 
If only one computer is doing it, it's not the network and not the port. I would turn the AV and FW off on the machine and try. We already know the port is exposed to the outside.

 

[Del91574]

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

This right here points to the problem existing in the box that the OP is attempting to use to connect.
 
Kill the AV and FW. Something with either of those or the image is causing the issue.

 

[Rossd]

This right here points to the problem existing in the box that the OP is attempting to use to connect.
 
Kill the AV and FW. Something with either of those or the image is causing the issue.

Del,
"Kinda", remember I can connect to 2601 on three other accounts from same machine, that being said, though I do not run a FW on the machine I am going to kill anything on the Actiontech router and Malware watcher on the problem machine to flush out your idea. I will report back
Thank you,
Ross

 

[Rossd]

No joy...

Please find attached screens RP1 unable to connect to the problem M1 at 2601 plus Systray and FW, of RP1 not running.   RP1 connecting to a different M1 on 2601 no problem, RP2 connection to problem M1 via 2601, no problem.
 
I was unable to upload images to this post.  I placed them in my gallery, hopefully they are viewable?:
 
http://cocoontech.com/forums/gallery/album/153-ross/?sort_order=asc&view_style=large

All ideas are appreciated.


Ross

 

[elvisimprsntr]

If you upgraded to the latest Elk and XEP firmware, I didn't think you could use RP1 to connect. I thought I read on the M1 owners downloads page or in the release notes you are now forced to use RP2

 

[drvnbysound]

I've had this problem happen on multiple machines with FW and AV being the culprit, including my own home.
 
If only one computer is doing it, it's not the network and not the port. I would turn the AV and FW off on the machine and try. We already know the port is exposed to the outside.

 
I missed the OPs post where he had used other machines to successfully connect via 2601 to this XEP; I only saw that he was able to make connection to the 3 other XEP's, and that 2101 on this one was working. That led me to think the secure port was being blocked (or not forwarded).
 
"Typically" once your computer initiates an outbound connection on a port, it's then opened for the return traffic... that's why I didn't suspect it would be the firewall on the local machine.

 

[TurboSam]

You said the "good" computer is Win7.  What is the "bad" computer running?
 
I would try two things.  
 
First, back up the whole RP directory on the "bad" computer.  Then in RP on that computer, open the account of the "bad" XEP, save it under a new name, and then try connecting under that new name.  It probably won't work, but is something I would try.  
 
A variation would be to also save one of the "good" XEP account configs on that computer to another name, change the dyndns/IP and login info as necessary and see if that cloned account info from a "good" XEP secure-port login works with the "bad" XEP.
 
More drastically, if still no luck, I would then try copying the whole RP directory from the "good" machine in one state to the "bad" machine in the other state (after, of course, backing up the whole directory in the second state) and see if you can get to the "bad" XEP using the config from the "good" machine that connects to that XEP.
 
Good luck!

 

[mikefamig]

Yes

You have mentioned RP1 in your posts but say that you have the newest RP2 software. Which version of RP are you using?

 

[Rossd]

I apologize for the confusion I caused with naming the RP's. All are RP'2's running on PC1 and PC2.

I will copy over the entire working application directory shortly and see what comes of it.

Regards,
Ross

 

[TurboSam]

I have a couple of other thoughts.
 
I can't help but think that, if it's not a problem in the RP software or its configuration, it's a problem with your configuration settings in a router--either on the XEP side or, less likely, something going outbound from PC2 with the other ISP.  
 
We know the 2601 port is open because PC1 can connect to the XEP that PC2 can't connect to on port 2601, but is there some setting that would, for example, limit the permissible range of outside IP's that can trigger that port to open (or is it open to the whole world)?  Is there any possibility that the external IP of PC2 changed and that the router for the "bad" XEP is balking at the change.  This is probably less of a potential problem if the "bad" XEP is in the same location as another "good" XEP behind the same router, but even if so, maybe the port forwarding configuration for 2601 is off...
 
Other things to consider: 
 
Any VLANs that could cause the hickup?  
 
Also, your OP said everything was working fine....but did you make any changes, updates, etc in the hardware or software configuration of PC2 or PR or any settings in the "bad" XEP's router that could have caused the problem?  Do you know if the ISP's external IP to your PC2 changed recently?

 

[Rossd]

TurboSam - No VLAN's, no changes of note other than to fully disable the FW on the XEP problem side.
Tonight I moved over from the working PC the following directories:
C:\Users\Ross\Desktop\ElkRP
C:\Users\Ross\Desktop\RP
 
I than ran the application and set the database paths to the local RP folder above.  I then loaded these databases and verified they were correct.  Loaded an account of a working XEP from PC2 and 2601 connected as normal.
 
I then loaded problem account.  Attempted connection and received the identical error as previous. 
 
So we took a fully working install, copied to another PC on another ISP and tried unsuccessfully to connect.
 
arghhhhhhhhh divot in hole on desk from head beating getting larger....
 
R

 

[giesen]

On the computer where ElkRP is not working for that specific site, do the following:
 
Open a command prompt, and type:
 
telnet XXX.dyndns.org 2601
 
and hit enter, where XXX is the real host name.
 
If you get "Connecting To XXX.dyndns.org...Could not open connection to the host, on port 2601: Connect failed", then the problem is not with RP2 but with either the system it's running on (Firewall/AV/etc), or the firewall or NAT rules at the remote site.
 
If instead it opens a connection (you'll just see a blank black box), you've at least verified you have network connectivity on the secure port to that site.