Skip to main content
Submitted by vweinhardt on Tue, 04/25/2017 - 16:32

We have 2 DMC4040 controllers which are connected via Ethernet Hub to the local machine. At power on all controllers and corresponding IPs are visible, after connection it works for some time and then one of them (always the same) stops to work because Galil suite does not see it anymore. No error light on the controller itself, everything looks the same but connection to the designated IP address is not possible. Changing port of the Ethernet hub does not help, changing settings for Ethernet does not help, Windows Firewall the same issue. The only thing which helps is to power off and on it again.

any ideas how to figure out what is wrong?

Best wishes,

Venera

Comments 5

MattK on 05/01/2017 - 10:54

Hello Venera,

 

  All Galil controllers can be connected to using some of the standard Ethernet troubleshooting utilities provided with Windows, namely telnet and ping. If GalilSuite is no longer listing the IP Address, my first suggestion would be to ping the controller from the Windows Command line by issuing "ping [IP Address]" where [IP Addresss] is the IP that you previously assigned to the controller. If the controller can be successfully pinged, then the next step is to establish a telnet connection, issue "telnet [IP Address]" in the command line. Now you can send commands to the controller as you normally would, issue 'MG TIME' and press enter to get the response.

 

If you are able to perform both of these tasks while GalilSuite is not able to connect, then we should look at what GalilSuite version you are using and consider upgrading to more recent software like GDK.

vweinhardt on 05/31/2017 - 13:07

Dear Matt,

I am working again with this controller and had the same issue last two days. So in the end I can ping the IP address, but I can not establish telnet.
The transcript from cmd looks as:
ping [IP address]
Pinging [IP address] with 32 bytes of data:
Reply from [IP address]: bytes 32 time<1ms TTL=128
Reply from [IP address]: bytes 32 time<1ms TTL=128
Reply from [IP address]: bytes 32 time<1ms TTL=128
Reply from [IP address]: bytes 32 time<1ms TTL=128

Ping statistics for [IP address]:
Packets: Sent=4, Received=4, lost =0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum=0ms, Maximum=0ms, Average=0ms

telnet [IP address]
Connecting to [IP address]...Could not open connection to the host, on port 23: Connect failed

Any ideas what should I do?

vweinhardt on 05/31/2017 - 13:34

Add on to previous message:
I just physically plugged out the controller and plugged it in. Galil suite sees IP address again. Ping and telnet are working. Could issue MG TIME. Typically it would happen a few times per day sometime less sometime more. Only brutal power solution solves it.

MattK on 06/19/2017 - 11:58

Venera,

I would like to get some additional information on the hardware you are using, I'll need you to enter some commands to do so and relay the information to me. We should do this over email however. Please email me at mattk@galil.com to continue troubleshooting.

Cyberops on 02/16/2018 - 02:34

All Galil controllers can be connected to using some of the standard Ethernet troubleshooting utilities provided with Windows, namely telnet and ping. If GalilSuite is no longer listing the IP Address, my first suggestion would be to ping the controller from the Windows Command line by issuing "ping [IP Address]" where [IP Addresss] is the IP that you previously assigned to the controller. If the controller can be successfully pinged, then the next step is to establish a telnet connection, issue "telnet [IP Address]" in the command line. Now you can send commands to the controller as you normally would, issue 'MG TIME' and press enter to get the response.