Connecting to Elk M1G using Ethernet?

RZajcew
Intermediate
Intermediate
Posts: 257
Joined: Mon Jul 21, 2008 6:31 pm
Contact:

Connecting to Elk M1G using Ethernet?

Postby RZajcew » Wed Nov 26, 2008 6:57 pm

I have my Elk M1G connected via Ethernet, and I have made sure that Port 2101 is enabled. The Elk RP software successfully communicates with the Elk M1G.

When the Mainlobby Server starts up, the Elk plugin log has a long set of sequences that look like this:

Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket Error #10061: Connection is forcefully rejected
Socket state [0]
Socket state [0]
Socket state [0]
Socket state [0]
Socket state [0]
Timeout trying to connect via TCP/IP
TCP/IP Sending [06zp0050]
Forced Timeout waiting for handshake
Got [ZD]
Opening connection via TCP/IP
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket Error #10061: Connection is forcefully rejected
Socket state [0]
Socket state [0]
Socket state [0]
Socket state [0]
Socket state [0]
Socket state [0]
Timeout trying to connect via TCP/IP
TCP/IP Sending [06zd005C]
Forced Timeout waiting for handshake
Got [ASR]
Opening connection via TCP/IP
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket Error #10061: Connection is forcefully rejected
Socket state [0]
Socket state [0]
Socket state [0]
Socket state [0]
Socket state [0]
Socket state [0]
Timeout trying to connect via TCP/IP
TCP/IP Sending [06as0066]
Forced Timeout waiting for handshake
Got [CS]
Opening connection via TCP/IP
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket state [6]
Socket Error #10061: Connection is forcefully rejected
Socket state [0]
Socket state [0]
Socket state [0]
Socket state [0]
Socket state [0]
Socket state [0]
Timeout trying to connect via TCP/IP
TCP/IP Sending [06cs0064]
Forced Timeout waiting for handshake
Got [SD~1~1]
Opening connection via TCP/IP

[No Elk server variables are created]

- Roman

User avatar
mcascio
Founder
Founder
Posts: 8270
Joined: Tue Jan 28, 2003 4:03 pm
Location: Kenosha, Wi
Contact:

Postby mcascio » Wed Nov 26, 2008 7:34 pm

Sounds like it's not getting any feedback from the ELk.

Make sure nothing else is using that port and/or a firewall is not blocking communication with that port.

Did you shutdown the ELK RP software before trying to communicate? I don't have a TCP connection with my personal ELKM1 so I'm not sure if it allows multiple applications to connect simultaneoously.
Mario Cascio
Cinemar, Inc.
http://www.cinemaronline.com

RZajcew
Intermediate
Intermediate
Posts: 257
Joined: Mon Jul 21, 2008 6:31 pm
Contact:

Postby RZajcew » Wed Nov 26, 2008 9:32 pm

I turned off the firewall on the server earlier today to see if that was a problem.

To test out the theory of whether this was some sort of interaction with the ElkRP software, I completely turned off the ElkM1G, the Ethernet controller, and the server, and then started everything up again (without using ElkRP).

The results were the same (the same style of log messages for the Elk plugin).

- Roman

User avatar
CinemarDave
Site Admin
Site Admin
Posts: 10535
Joined: Fri Feb 07, 2003 8:56 am
Location: Planet Earth
Contact:

Postby CinemarDave » Fri Nov 28, 2008 10:05 am

When connecting to the Elk you have to make sure you connect using the non-secure TCP port. The plugin does not support SSL traffic. Run EllRP and enable the alternate port and then see if you can connect.

RZajcew
Intermediate
Intermediate
Posts: 257
Joined: Mon Jul 21, 2008 6:31 pm
Contact:

Postby RZajcew » Fri Nov 28, 2008 1:19 pm

I should have mentioned this in my original post... Sorry... Originally I had set up the Elk and the Elk plugin to use the secure port (and SSL). However, after reading through other posts on the forum, I did note that secure communications was not supported, and I enabled the non-secure port on the Elk (and changed the plugin to us that port).

When using the secured port, the pattern of messages in the plugin log was quite different.

RZajcew
Intermediate
Intermediate
Posts: 257
Joined: Mon Jul 21, 2008 6:31 pm
Contact:

Postby RZajcew » Fri Nov 28, 2008 2:30 pm

Just to be totally thorough, I totally reset the Elk XEP (shorting jumper JP2) and then reconfigured the XEP. This time, for whatever reason, it worked. Thanks.

User avatar
Oronomus
Intermediate
Intermediate
Posts: 346
Joined: Mon Aug 14, 2006 1:18 pm
Location: Atlanta
Contact:

Re: Connecting to Elk M1G using Ethernet?

Postby Oronomus » Thu Jun 09, 2011 10:00 pm

Had a similar issue, where I had to reset the XEP to connect to the plugin. Remember that once you do the reset (after checking the enable non-secure port box), you have to reconfigure the XEP by 1) pushing "Find" in the M1XEP Setup to locate the XEP, then hitting "Send" from the M1XEP Setup and clicking to enable the XEP to reboot. After the reboot, test to make sure you can connect to the ELKRP. When that works, the XEP is rebooted. Then disconnect the software from the XEP, and exit the software. Then you can load the plugin and test the IP connection. I messed up the step of hitting send and then rebooting.


Return to “Elk Products”

Who is online

Users browsing this forum: No registered users and 1 guest