Several M1XEP Issues

I am having several connectivity issues with the ELK-M1XEP Ethernet Interface.

1) Email does not work, 2) Time service does not work and 3) the Dynamic DNS does not work.

I have tried all three using the Test button with no success.

I am using dyndsn.com for the public IP Address.

I belive I should start by diagnosing the Dynamic DSN since the other two feature seem to use it.

Is the any logging that would provide any clues?

Any other suggestions would certainly be appreciated.

Thanks, Paul
 
I would check your network first.

Make sure the XEP is port forwarded for the appropriate ports through any firewall/router. You may be only viewing/accessing the XEP on the internal network segment and not getting the NAT and outside of the intranet and on the internet.
 
Do a search for all the associated problems with the XEP. Things such as you describe. I basically gave up on mine, is all I use it for is RP, and Premise.
 
Email and NTP don't rely on Dynamic DNS. They really are 3 independent things. So you need to troubleshoot them one at a time. They rely on DNS however (not the same as DynDNS) if you are putting in names instead of IP addresses.

Typically a firewall will allow outbound connections which all of these are, just not inbound which is what port forwards do.

Are you running DHCP or putting in an IP address manually? If using a static ip do you have a gateway configured, do you have DNS configured under TCP/IP settings? If using DHCP I would try a static configuration. The gateway would be your internal router IP address, the DNS would be the DNS servers provided by your ISP. (you can go to a PC on your network and type ipconfig /all to get that info).

For NTP, is time working ok on your PC's? Try using several NTP names us.pool.net.org, time.nist.gov, time.windows.com. If those don't work try an IP address instead 74.118.152.85.

Email can be caused by a lot of different issues. You could try to sign up for a free account and test with one of those (i.e. gmail). As mentioned above there are a lot of threads on Elk email issues, so I agree about searching and reading up on those and seeing if your ISP is listed.

Dynamic DNS may not really be needed, if your router is doing it for you, which is usually how it is done. Basically dynamic DNS is just a DNS provider, a client that knows your external IP registers it with the provider so you can hit it from outside your house by name. So if your router is updating for you, you don't need the Elk to do it too and can ignore that config on the Elk.
 
My installer and I had a weird issue similar.

Email, web interface, eKeypad (iPhone) was very intermittent.

M1XEP would loose connection when in RP. You know what it ended up being????




I put a (space) in front of the area name/display so that it was centered, I'm anal like that. So i had (space)(space)KWANDO'S HOUSE, deleted the two space characters and everything has been fine. We tired everything before finding out the issue, swapped M1XEP, tried different router/network settings, etc. So check to see if you have any spaces in front of your area name.
 
Hello Again,

I have tried several changes with no success in resolving my XEP connectivitiy issues.

.... I just felt the earthquake hear DC - Wow!!! ....

Here is a response to your questions and some other updates:

1. I have been able to successfully ping the XEP Interface (192.168.0.3)

2. I was trying to use the Dynamic DNS but have now removed it.

3. I changed the Time URL to time.hist.gov and got the following error: Test failed. The M1XEP could not resolve the server's URL or detected a bad IP Addreess.

4. I have not been able to successfully test Email, Dynamic DNS or Time.

5. I have tried both Static IP and DHCP with not success, current using DHCP.

6. The XEP Diagnostic utility produced the following during the Get DNS Address Test:
DHCPINFORM enter
sock=00000054
sendto returned: 00000100
UDP send to 2555.2555.2555.2555, port 2362, M1XEP
recvfrom returned: FFFFFFFF, Rcv Tomer=0
getErrno returned:0000000B
done
ReturnCode=02

7. Running ELKRP 2.0.10, M1G Firmware 5.2.4, XEP 1.3.26

Thanks in advance for any succestions/recommendations.

Regards, Paul
 
Hello Again,

I have tried several changes with no success in resolving my XEP connectivitiy issues.

.... I just felt the earthquake hear DC - Wow!!! ....

Here is a response to your questions and some other updates:

1. I have been able to successfully ping the XEP Interface (192.168.0.3)

2. I was trying to use the Dynamic DNS but have now removed it.

3. I changed the Time URL to time.hist.gov and got the following error: Test failed. The M1XEP could not resolve the server's URL or detected a bad IP Addreess.

4. I have not been able to successfully test Email, Dynamic DNS or Time.

5. I have tried both Static IP and DHCP with not success, current using DHCP.

6. The XEP Diagnostic utility produced the following during the Get DNS Address Test:
DHCPINFORM enter
sock=00000054
sendto returned: 00000100
UDP send to 2555.2555.2555.2555, port 2362, M1XEP
recvfrom returned: FFFFFFFF, Rcv Tomer=0
getErrno returned:0000000B
done
ReturnCode=02

7. Running ELKRP 2.0.10, M1G Firmware 5.2.4, XEP 1.3.26

Thanks in advance for any succestions/recommendations.

Regards, Paul

I really wish the XEP would get replaced with a newer version that did away with the Java applet and used an Ajaxy/HTML5 interface.
 
Also, During setup, I am unable to give the XEP a Device Name. I assumed this was because I only have 1 XEP. Or, could this be part of the problem?

Regards, Paul
 
I have good news to report. I now have my M1XEP connectivity issues resolved.

I placed a service call to LinkSys to check the setting on my router.

During discussing the issue with the Tech, we discovered that my Port Forwarding was pointed to 192.168.0.3 (a static address). So, I needed to use the static Address consistently in the setup (no DHCP).

I also needed to pick up the specific Pri/Sec DNS addresses from the router info coming from the ISP.

Now things work fine (email and time) and I can also name the XEP! Thinks are good! Thanks to LinkSys for their assistance!

Regards, Paul
 
Back
Top