Ugh, I am having the darndest time getting my M1 connected to the internet. My M1 is connected to the ELK-M1XEP and that is connected to my NetGear router. Since I use Verizon Fios, which has its own router (needed for VOD and Program Guide) I have the Verizon router acting as the DHCP server giving my Netgear an IP address. Every device I have plugged into my router has an IP, and I am able to access the M1XEP through the ELKRP software over the network. But when I try to use it so send emails, or even connect to the time server, it won't work. I have my Tivo connected to to the same router and it is able to make calls for program information, etc, but for the life of me I can not get my ELK to connect. This is driving me crazy. Any ideas?
Elk M1 Internet Connectivity Problem
- Thread starter dsabot
- Start date
I opened up the ports, and updated the M1 firmware as well as the M1EXP firmware to the latest versions. I am now able to connect to the time server and get a test passed. However I am still unable to send email. It shows that it tried to send the email, I used the same settings in outlook to ensure they work on the network but nothing. I am using Verizon Fios and have the latest firmware if that helps.
BraveSirRobbin
Moderator
Does your SMTP server require authentication? I know mine does and in Outlook I have to supply a username and password to send any Email out.
This might be related, but when I enter the IP address of the M1EXP I get the login for the web version of the security panel. However, the hourglass never disappears, I am unable to click any buttons, and only 2 of my 3 keypads are visible. Hitting refresh does nothing. I have upgraded to the latest version of java, and tried it on IE and Firefox to no luck. I also made sure my Globals were set correctly to enabled to transmit all changes.
These are how my ports are forwarded from the M1EXP
UDP Any -> 2101
TCP Any -> 2101
TCP Any -> 2601
TCP Any -> 26
TCP Any -> 80
TCP Any -> 26
These are how my ports are forwarded from the M1EXP
UDP Any -> 2101
TCP Any -> 2101
TCP Any -> 2601
TCP Any -> 26
TCP Any -> 80
TCP Any -> 26
Just an update, I think I managed to fry my ELK-M1XEP. Sometimes too much tinkering can be a bad thing. I accidentally rolled back the firm and bootware to an older version and now can't even see it on the network. Even before I did this, I think there was a problem with the unit and will likely get a new one to see if it fixes my issues.
v1rtu0s1ty
Senior Member
Hi David,
I want to share one tip for your next troubleshooting once you get it fixed. I always do this when I troubleshoot applications when data passes through our firewall or maybe even routers/switches with access lists enabled. I don't want to open up a ticket to engage our security folks(takes days), so I do this on my side first. However, this only works for TCP connections and not connectionless which is UDP. It does really work.
Just open up notepad and add these lines and save it as sniff.bat. You can save it under c:\temp or where you want it. I like it in c:\windows since it's in the PATH env variable.
:repeat
netstat -na|find "SYN"
goto repeat
Check out the script in action. Simple but tells me quickly the tcp session problem. If you look at the one on top, the script sniff.bat found that we are trying to connect to 192.168.1.50, however, it's not able to complete the TCP 3 WAY handshake. This is the reason why we are seeing tons of SYN being sent by my machine. If it was able to connect to that port, 6444, we won't see anything, it will just keep on running. However, it would show an ESTABLISHED when you do a netstat -na|find "6444".
Let say I was testing and I didn't find any SYN packets and my telnet message quickly disappeared and replaced by a blinking cursor, then it means that it was able to established a good connecton rather than TELNET showing the message "Connection to ....".
Hope this helps. Keep me posted!
I want to share one tip for your next troubleshooting once you get it fixed. I always do this when I troubleshoot applications when data passes through our firewall or maybe even routers/switches with access lists enabled. I don't want to open up a ticket to engage our security folks(takes days), so I do this on my side first. However, this only works for TCP connections and not connectionless which is UDP. It does really work.
Just open up notepad and add these lines and save it as sniff.bat. You can save it under c:\temp or where you want it. I like it in c:\windows since it's in the PATH env variable.
:repeat
netstat -na|find "SYN"
goto repeat
Check out the script in action. Simple but tells me quickly the tcp session problem. If you look at the one on top, the script sniff.bat found that we are trying to connect to 192.168.1.50, however, it's not able to complete the TCP 3 WAY handshake. This is the reason why we are seeing tons of SYN being sent by my machine. If it was able to connect to that port, 6444, we won't see anything, it will just keep on running. However, it would show an ESTABLISHED when you do a netstat -na|find "6444".
Let say I was testing and I didn't find any SYN packets and my telnet message quickly disappeared and replaced by a blinking cursor, then it means that it was able to established a good connecton rather than TELNET showing the message "Connection to ....".
Hope this helps. Keep me posted!
Similar threads
- Question
