Topic: Can't connect via TCP

By: Pete Olski

Posted on: Jul 13 2016 at 04:15:16 PM

I have a Moxa Ethernet / wireless to serial server set up. I can ping the IP address, I can bring up the Moxa web page console in Internet Explorer, so I'm communicating with the device through its IP address. I have selected TCP/IP in RemoDNC and entered the correct IP address and the port number. However, I always get a message box that RemoDNC can't communicate to this IP address. I can communicate with other items. What steps can I take? I want to present this program-loading solution to a customer this Friday. I appreciate your time and response.

By: Pete Olski

Posted on: Jul 13 2016 at 05:05:47 PM

I discovered that the Moxa device didn't have drivers for Windows 10. I was able to get everything functioning from a Windows 7 PC.

By: Guest

Posted on: Jul 14 2016 at 07:50:10 PM

A windows device driver wouldn't usually be necessary for a direct TCP connection to a remote device.

More likely your Windows 10 firewall was blocking outgoing connections to the port number. (the browser uses a different number not normally blocked by firewalls so that explains how the browser could open the moxa console but Remo couldn't connect to the moxa serial port)

Go to the windows firewall and select the option to open an outgoing port and enter the port number.

By: Guest

Posted on: Jul 25 2016 at 11:31:17 AM

RemoDNC is working through USB port in my laptop, but not through LAN port, gives alarm "could not connect to 127.0.0.1:0" .I even Switched OFF windows firewall. Any help please.

By: Guest

Posted on: Jul 25 2016 at 04:12:15 PM

Why would you want it to connect to 127.0.0.1

That IP address is the local loopback address - you're asking the computer to connect to itself.

I assume you're using a network or wifi RS232 device? In that case you need to enter the IP address of that device (Which can NOT be 127.0.0.1)

Topic: Can't connect via TCP

Reply to this topic