Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017 Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
<== Date ==> <== Thread ==>

Subject: RE: problem connecting serial device with moxa 5150A
From: Mark Rivers <rivers@cars.uchicago.edu>
To: "'Sunny Badkul'" <sunnybadkulji@gmail.com>
Cc: "tech-talk@aps.anl.gov" <tech-talk@aps.anl.gov>
Date: Fri, 27 Jan 2017 15:48:14 +0000

Hi Sunny,

 

What you have said makes no sense to me at all.

 

These are the IP settings on the Moxa box:

 

IP address                     : 192.168.127.254
Netmask                        : 255.255.255.0
Gateway                        :

These are the Windows IP settings when you boot Windows on the PC:

 

   Connection-specific DNS Suffix  . : cat.ernet.in<http://cat.ernet.in><http://cat.ernet.in>

   Link-local IPv6 Address . . . . . : fe80::f160:7b80:19a6:5bf2%11
   IPv4 Address. . . . . . . . . . . : 10.128.1.35
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 10.128.0.254

These are the Linux IP settings when you boot Linux on the PC:

 

eth0      Link encap:Ethernet  HWaddr D8:CB:8A:9C:61:96
          inet addr:192.168.127.0  Bcast:192.168.127.255  Mask:255.255.255.0
          inet6 addr: fe80::dacb:8aff:fe9c:6196/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1454 (1.4 Kb)  TX bytes:10799 (10.5 Kb)

eth1      Link encap:Ethernet  HWaddr 70:62:B8:B5:AE:FB
          inet addr:10.128.2.69  Bcast:10.128.255.255  Mask:255.255.0.0
          inet6 addr: fe80::7262:b8ff:feb5:aefb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:69794 errors:0 dropped:1 overruns:0 frame:0
          TX packets:16282 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:28074872 (26.7 Mb)  TX bytes:2245798 (2.1 Mb)

When you boot Linux you are connecting the Ethernet cable to the eth0 port, not the eth1 port as judged by the arp output, packet counters, and logic.

 

Notice that your Windows IP address and netmask are completely incorrect for the Moxa.  They have different subnet masks, and they are not on the same subnet.  But you say you can telnet to the Moxa OK from Windows.  That does not make sense to me.  I would actually expect that it would fail on Windows and succeed on Linux given these settings, but you are seeing the opposite.  Are you sure that you have actually connected the Moxa to that Ethernet interface and not another one?  When you change from Windows to Linux are you leaving the Ethernet cable plugged into the same port on the PC?

 

Please send the complete output of the following commands on Windows when it is connected OK to the Moxa

 

ipconfig /all

arp –a

 

Mark

 

 

 

From: Sunny Badkul [mailto:sunnybadkulji@gmail.com]
Sent: Friday, January 27, 2017 8:15 AM
To: Mark Rivers
Subject: RE: problem connecting serial device with moxa 5150A

 

Hello, 

   It is a dual boot machine in which 1 OS run at a time.. 

The moxa board is directly connected to the system with simple ethernet cable..

As u asked about power cycling when I swithch from windows to linux 

1} I turned off moxa board and turn it on when connected to linux.

2} I kept moxa board turned on when switching on the OS.

 

In both cindition result is same ( I did not press reset buttion in both condions).

 Thank you

 

On 27 Jan 2017 6:38 p.m., "Mark Rivers" <rivers@cars.uchicago.edu> wrote:

Please answer all the questions in my e-mail.  You did not not answer about power-cycling and about how the Moxa is physically connected to the machine.  Also, is this a dual boot machine, or are both OS running at the same time in a Virtual Machine?


Mark

________________________________
From: Sunny Badkul [sunnybadkulji@gmail.com]

Sent: Friday, January 27, 2017 7:02 AM

To: Mark Rivers
Subject: Re: problem connecting serial device with moxa 5150A

hi Mark,

outpot is same for ncat with port definition

ncat  192.168.127.254 4001
Ncat: Connection timed out.



> Ethernet adapter Local Area Connection 2:
>   IPv4 Address. . . . . . . . . . . : 10.128.1.35

this is the only Ethernet adapter which is connected to moxa in my machine, I left the second adapter disconnected when running ipconfig

Both the OS are running on same machine and I tried  both the methods power of the moxa when disconnecting to Linux and do no power off)

yes I tried to connect web interface both in linux and windows. its connected in windows and timed out in linux.





On Fri, Jan 27, 2017 at 5:13 PM, Mark Rivers <rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>> wrote:
Hi Sunny,

> ncat  192.168.127.254
> Ncat: Connection timed out.

You did not give the port 4001 in the ncat command.  It must be

ncat 192.168.127.254 4001

> Ethernet adapter Local Area Connection 2:
>   IPv4 Address. . . . . . . . . . . : 10.128.1.35

That is the wrong Ethernet adapter, it is not the one on the same subnet as device (192.168.127.*).  Send the information on the port connected to the Moxa.

>> When you switch to Linux do you power-cycle the Moxa?  You should to make sure it has forgotten about the Windows machine
> I cant properly understand what you mean by this sentences. Please elaborate it.

You said that you can telnet to the Moxa from Windows.  When you then try to telnet from Linux did you turn off the power to the Moxa before you tried to connect from Linux.  Are the Linux and Windows computers actually the same computer with dual boot, or is it 2 different computers?

Have you tried using the Web interface to the Moxa in both Windows and Linux?

How is the Moxa connected to the Windows and Linux machines?  Direct connect, or through a switch?

Mark




________________________________

From: Sunny Badkul [sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>]

Sent: Friday, January 27, 2017 2:27 AM
To: Mark Rivers
Subject: Re: problem connecting serial device with moxa 5150A

ncat  192.168.127.254
Ncat: Connection timed out.



Dear Mark,
 I tried All  five suggestions in your last mail

-          When you boot Windows what it the IP address of the Windows machine on that subnet?

Ethernet adapter Local Area Connection 2:

   Connection-specific DNS Suffix  . : cat.ernet.in<http://cat.ernet.in><http://cat.ernet.in>

   Link-local IPv6 Address . . . . . : fe80::f160:7b80:19a6:5bf2%11
   IPv4 Address. . . . . . . . . . . : 10.128.1.35
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 10.128.0.254

Tunnel adapter Teredo Tunneling Pseudo-Interface:

   Media State . . . . . . . . . . . : Media disconnected


-          If you telnet from Windows can you type a command to the device and get a reasonable response.

Yes I can cammand the device with telnet and can put/get Input/outpot and alter the device functions.
-          When you switch to Linux do you power-cycle the Moxa?  You should to make sure it has forgotten about the Windows machine

I cant properly understand what you mean by this sentences. Please elaborate it.

-          Try running ncat from Linux to the Moxa rather than telnet.  See if that will connect.

result is same as telnet

                      ncat  192.168.127.254
                       Ncat: Connection timed out.
-          Have you tried the Linux IOC again?  Perhaps some things we have done will have fixed it?
Yes I tried it continuously result is same.
I also disabled selinux prior it was permissive





following is the complete setting of moxa board with telnet in windows.

-----------------------------------------------------------------------------
Model name       : NPort 5150A
MAC address      : 00:90:E8:4E:6E:4E
Serial No.       : 5227
Firmware version : 1.2 Build 15041515
System uptime    : 0 days, 01h:17m:25s
-----------------------------------------------------------------------------
<< Main menu >>
  (1) Basic settings
  (2) Network settings
  (3) Serial settings
  (4) Operating settings
  (5) Accessible IP settings
  (6) Auto warning settings
  (7) Monitor
  (8) Ping
  (9) Change password
  (a) Load factory default
  (v) View settings
  (s) Save/Restart
  (q) Quit

Key in your selection: v

-----------------------------------------------------------------------------

Server name                    : NP5150A_5227
Web console                    : Enable
Telnet console                 : Enable
Reset button protect           : No

Press any key to continue...

-----------------------------------------------------------------------------

IP address                     : 192.168.127.254
Netmask                        : 255.255.255.0
Gateway                        :
IP configuration               : Static
DNS server 1                   :
DNS server 2                   :
SNMP                           : Disable
SNMP community name            : public
SNMP contact                   :
SNMP location                  :
Auto report to IP              : 4001
Auto report to UDP port        : 4002
Auto report period(seconds)    : 10

Press any key to continue...

-----------------------------------------------------------------------------

Port 1
Baud rate                      : 9600
Data bits                      : 8
Stop bits                      : 1
Parity                         : None
Flow control                   : RTS/CTS
FIFO                           : Disable
Interface                      : RS-232

Press any key to continue...

-----------------------------------------------------------------------------

Port 1                         : TCP Server Mode
TCP alive check time (0-99min) : 70
Inactivity time                : 0
Max connection                 : 1
Packing length                 : 0
Delimiter 1                    : (Disable) 0
Delimiter 2                    : (Disable) 0
Delimiter process              : Do Nothing
Force transmit                 : 0
Local TCP port                 : 4001
Command port                   : 966

Press any key to continue...

-----------------------------------------------------------------------------

Enable the accessible IP list  : Disable
1       Disable                         0.0.0.0
2       Disable                         0.0.0.0
3       Disable                         0.0.0.0
4       Disable                         0.0.0.0
5       Disable                         0.0.0.0
6       Disable                         0.0.0.0
7       Disable                         0.0.0.0
8       Disable                         0.0.0.0
9       Disable                         0.0.0.0
10      Disable                         0.0.0.0
11      Disable                         0.0.0.0
12      Disable                         0.0.0.0
13      Disable                         0.0.0.0
14      Disable                         0.0.0.0
15      Disable                         0.0.0.0
16      Disable                         0.0.0.0
Press any key to continue...

-----------------------------------------------------------------------------

Mail server                    :
My server requires authenticat : Disable
From account address           : NP5150A_5227@NP5150A
Email address 1                :
Email address 2                :
Email address 3                :
Email address 4                :
SNMP trap server IP or domain  :
Press any key to continue...

-----------------------------------------------------------------------------

                        Mail    Trap
Cold start              Disable Disable
Warm start              Disable Disable
Authentication failure  Disable Disable
IP address changed      Disable
Password changed        Disable
Press any key to continue...

-----------------------------------------------------------------------------

DCD changed
Port    Mail    Trap
 1      Disable Disable
Press any key to continue...

-----------------------------------------------------------------------------

DSR changed
Port    Mail    Trap
 1      Disable Disable
Press any key to continue...



On Tue, Jan 24, 2017 at 10:25 PM, Mark Rivers <rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>>> wrote:
Hi Sunny,

There have now been lots of suggestions on tech-talk.

Here are some questions and things to try:


-          When you boot Windows what it the IP address of the Windows machine on that subnet?

-          If you telnet from Windows can you type a command to the device and get a reasonable response.

-          When you switch to Linux do you power-cycle the Moxa?  You should to make sure it has forgotten about the Windows machine

-          Try running ncat from Linux to the Moxa rather than telnet.  See if that will connect.

-          Have you tried the Linux IOC again?  Perhaps some things we have done will have fixed it?

Mark


From: Mark Rivers
Sent: Tuesday, January 24, 2017 7:35 AM
To: Sunny Badkul
Subject: RE: problem connecting serial device with moxa 5150A

On the Linux box can you run a browser (Firefox, etc.) and connect to the Moxa?

________________________________

Sent: Tuesday, January 24, 2017 6:35 AM
To: Mark Rivers
Subject: Re: problem connecting serial device with moxa 5150A
sorry,
          But output is same for this command also.

 telnet 192.168.127.254 4001
Trying 192.168.127.254...
telnet: connect to address 192.168.127.254<http://192.168.127.254>: Connection timed out

cant get whats wrong..


Thanx

On Tue, Jan 24, 2017 at 5:41 PM, Mark Rivers <rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>>> wrote:
> after that I tried ping and telnet. it is same as before. When trying to telnet it tries for some
> time  and then time out. output for all commands is as follows..
> telnet 192.168.127.254
> Trying 192.168.127.254...
> telnet: connect to address 192.168.127.254<http://192.168.127.254>: Connection timed out.

But you are not using telnet to the correct port.  The command should be

telnet 192.168.127.254 4001

Mark

________________________________

Sent: Tuesday, January 24, 2017 12:27 AM
To: Mark Rivers
Subject: Re: problem connecting serial device with moxa 5150A

hi Mark,
 I turned off the firewall and chacked the status with tha command

 systemctl status SuSEfirewall2.service

It reflects..

SuSEfirewall2 phase 2
   Loaded: loaded (/usr/lib/systemd/system/SuSEfirewall2.service; disabled)
   Active: inactive (dead)

after that I tried ping and telnet. it is same as before. When trying to telnet it tries for some time  and then time out. output for all commands is as follows..

telnet 192.168.127.254
Trying 192.168.127.254...
telnet: connect to address 192.168.127.254<http://192.168.127.254>: Connection timed out.




ping 192.168.127.254
PING 192.168.127.254 (192.168.127.254) 56(84) bytes of data.
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=1 ttl=255 time=1.69 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=2 ttl=255 time=0.797 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=3 ttl=255 time=0.753 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=4 ttl=255 time=0.724 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=5 ttl=255 time=0.804 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=6 ttl=255 time=0.795 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=7 ttl=255 time=0.713 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=8 ttl=255 time=0.769 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=9 ttl=255 time=0.810 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=10 ttl=255 time=0.770 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=11 ttl=255 time=0.692 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=12 ttl=255 time=0.849 ms
64 bytes from 192.168.127.254<http://192.168.127.254>: icmp_seq=13 ttl=255 time=0.739 ms
^C
--- 192.168.127.254 ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12000ms
rtt min/avg/max/mdev = 0.692/0.839/1.694/0.250 ms


/sbin/ifconfi


eth0      Link encap:Ethernet  HWaddr D8:CB:8A:9C:61:96
          inet addr:192.168.127.0  Bcast:192.168.127.255  Mask:255.255.255.0
          inet6 addr: fe80::dacb:8aff:fe9c:6196/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16 errors:0 dropped:0 overruns:0 frame:0
          TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1454 (1.4 Kb)  TX bytes:10799 (10.5 Kb)

eth1      Link encap:Ethernet  HWaddr 70:62:B8:B5:AE:FB
          inet addr:10.128.2.69  Bcast:10.128.255.255  Mask:255.255.0.0
          inet6 addr: fe80::7262:b8ff:feb5:aefb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:69794 errors:0 dropped:1 overruns:0 frame:0
          TX packets:16282 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:28074872 (26.7 Mb)  TX bytes:2245798 (2.1 Mb)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:128 errors:0 dropped:0 overruns:0 frame:0
          TX packets:128 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10432 (10.1 Kb)  TX bytes:10432 (10.1 Kb)





/sbin/arp

Address                  HWtype  HWaddress           Flags Mask            Iface
10.128.0.254             ether   00:00:5e:00:01:83   C                     eth1
10.128.0.99              ether   00:04:96:6d:67:7f   C                     eth1
10.128.0.253             ether   00:04:96:15:5e:70   C                     eth1
10.128.0.238             ether   00:04:96:27:50:63   C                     eth1
10.128.0.244             ether   00:04:96:34:ea:f2   C                     eth1
10.128.0.252             ether   00:04:96:28:24:ce   C                     eth1
10.128.0.237             ether   00:04:96:51:a8:8b   C                     eth1
192.168.127.254          ether   00:90:e8:4e:6e:4e   C                     eth0
10.128.0.251             ether   00:04:96:16:c7:50   C                     eth1
10.128.0.249             ether   00:04:96:05:7a:13   C                     eth1
10.128.0.247             ether   00:04:96:36:54:da   C                     eth1
10.128.0.246             ether   00:04:96:21:d6:10   C                     eth1

On Mon, Jan 23, 2017 at 6:33 PM, Mark Rivers <rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>>>> wrote:
With the firewall off and the Moxa running do the following:

- ping the Moxa from Linux
- Try to telnet to the Moxa

Then send the output of ifconfig and arp again.

Mark

________________________________

Sent: Monday, January 23, 2017 6:07 AM
To: Mark Rivers
Subject: Re: problem connecting serial device with moxa 5150A

Now I stopped firewall with following YaSt > firewall> stop running firewall. And tried telnet again it timed out.

On Mon, Jan 23, 2017 at 5:16 PM, Sunny Badkul <sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>>>>> wrote:
and this is the output for command /sbin/arp when connecting the moxa


10.128.0.252             ether   00:04:96:28:24:ce   C                     eth1
10.128.0.244             ether   00:04:96:34:ea:f2   C                     eth1
10.128.0.253             ether   00:04:96:15:5e:70   C                     eth1
10.128.0.237             ether   00:04:96:51:a8:8b   C                     eth1
10.128.0.254             ether   00:00:5e:00:01:83   C                     eth1
10.128.0.246             ether   00:04:96:21:d6:10   C                     eth1
10.128.0.238             ether   00:04:96:27:50:63   C                     eth1
10.128.0.247             ether   00:04:96:36:54:da   C                     eth1
10.128.0.99              ether   00:04:96:6d:67:7f   C                     eth1
192.168.127.254          ether   00:90:e8:4e:6e:4e   C                     eth0
10.128.0.249             ether   00:04:96:05:7a:13   C                     eth1
10.128.0.251             ether   00:04:96:16:c7:50   C                     eth1

On Mon, Jan 23, 2017 at 4:39 PM, Sunny Badkul <sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>>>>> wrote:
hello Mark,

following is the outputs of commands u asked.
Yes Firewall is runnibg on my machine
/sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr D8:CB:8A:9C:61:96
          inet addr:192.168.127.0  Bcast:192.168.127.255  Mask:255.255.255.0
          inet6 addr: fe80::dacb:8aff:fe9c:6196/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:8881 (8.6 Kb)

eth1      Link encap:Ethernet  HWaddr 70:62:B8:B5:AE:FB
          inet addr:10.128.2.69  Bcast:10.128.255.255  Mask:255.255.0.0
          inet6 addr: fe80::7262:b8ff:feb5:aefb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:15552 errors:0 dropped:1 overruns:0 frame:0
          TX packets:3653 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5579991 (5.3 Mb)  TX bytes:438187 (427.9 Kb)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:130 errors:0 dropped:0 overruns:0 frame:0
          TX packets:130 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:10628 (10.3 Kb)  TX bytes:10628 (10.3 Kb)



/sbin/arp
Address                  HWtype  HWaddress           Flags Mask            Iface
10.128.0.252             ether   00:04:96:28:24:ce   C                     eth1
10.128.0.244             ether   00:04:96:34:ea:f2   C                     eth1
10.128.0.253             ether   00:04:96:15:5e:70   C                     eth1
10.128.0.237             ether   00:04:96:51:a8:8b   C                     eth1
10.128.0.254             ether   00:00:5e:00:01:83   C                     eth1
10.128.0.246             ether   00:04:96:21:d6:10   C                     eth1
10.128.0.238             ether   00:04:96:27:50:63   C                     eth1
10.128.0.247             ether   00:04:96:36:54:da   C                     eth1
10.128.0.99              ether   00:04:96:6d:67:7f   C                     eth1
10.128.0.249             ether   00:04:96:05:7a:13   C                     eth1
10.128.0.251             ether   00:04:96:16:c7:50   C                     eth1



with Regards

Sunny

On Fri, Jan 20, 2017 at 6:05 PM, Mark Rivers <rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>>><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>>>>> wrote:
The Moxa snapshots look OK to me.

I apologize, I missed this part of your previous message:

> I am using two OS in my machine opensuse as well as windows
> when I telnet from windows
> telnet 192.168.127.254 4001
> It promts a blank screen and for other IP or ports like 192.168.127.254 5064, 192.168.127.34 4732 etc. it simply says host not available so I think port 4001 should be good.

I agree, that means port 4001 should be good.  It means the problem is probably on Linux.

> but when I run telnet 192.168.127.254 4001 or telnet 192.168.127.254 or telnet 192.168.127.254 5064 from linux it tries for some time and the times out.

Can you send the output of "/sbin/ifconfig" and /sbin/arp on your Linux machine.

Is your Linux machine running a firewall?

Mark

________________________________

Sent: Friday, January 20, 2017 1:04 AM
To: Mark Rivers
Subject: Re: problem connecting serial device with moxa 5150A

HIi Mark,
              these attachments  are snapshots for my moxa board with windows utility.

please check it and help me to resolve this.

thank you

On Thu, Jan 19, 2017 at 6:28 PM, Mark Rivers <rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>>><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>>>><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>>><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu><mailto:rivers@cars.uchicago.edu<mailto:rivers@cars.uchicago.edu>>>>>> wrote:
Hi Sunny,

I don't know how to interpret this information because I don't know what operating mode 10 is, for example.

[Operating Mode]
Port1=10

[Operating Mode Option 2]
Port1=16,0x00,0x00,0,0

[Operating Mode Option 1]
Port1=0,7,1,4001,966,0,0

It does seem like port 4001 is correct.

Can you send a screen shot showing the Moxa configuration screen with operating mode, etc.

Mark

________________________________

From: Sunny Badkul [sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>>>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com><mailto:sunnybadkulji@gmail.com<mailto:sunnybadkulji@gmail.com>>>>>]

Sent: Thursday, January 19, 2017 1:18 AM
To: Mark Rivers
Subject: Re: problem connecting serial device with moxa 5150A

hi Mark.

this is the configuration setting for my moxa board.

[NPort Configuration File]
CheckCode=cfg2

[Basic Information (not changeable)]
APID=0x80015100
HWID=0x515A
Serial No=5227
MAC Address=00:90:E8:4E:6E:4E
Firmware version=0x1020000

[Basic Settings]
Server Name=NP5150A_5227
Time Zone=0
Time Zone index=0
Date_Year=100
Date_Month=11
Date_Day=30
Time_Hour=0
Time_Minute=44
Time_Second=1
Time_Milliseconds=0
Time Server=
Console Enabled=3

[Network Settings]
IP Address=192.168.127.254
Netmask=255.255.255.0
Gateway=
IP Configuration=0
DNS Server 1=
DNS Server 2=

[SNMP]
Enable SNMP=0
Community=public
Location=
Contact=
Trap=

[Mail]
Mail Server=
Mail Server Login=0
User Name=
Password=
From Address=NP5150A_5227@NP5150A
To Address1=
To Address2=
To Address3=
To Address4=

[Accessible IP List]
Enabled=0
Rule1=0,,
Rule2=0,,
Rule3=0,,
Rule4=0,,
Rule5=0,,
Rule6=0,,
Rule7=0,,
Rule8=0,,
Rule9=0,,
Rule10=0,,
Rule11=0,,
Rule12=0,,
Rule13=0,,
Rule14=0,,
Rule15=0,,
Rule16=0,,

[Serial]
Port1=9600,3,1,1,0,

[Operating Mode]
Port1=10

[Operating Mode Option 2]
Port1=16,0x00,0x00,0,0

[Operating Mode Option 1]
Port1=0,7,1,4001,966,0,0

[Auto Warning]
Mail=0x0
Trap=0x0

[Port Auto Warning]
Port1=0x00,0x00

[IP Address Report]
Server=
Port=4002
Period=10

[Password]
Password=
LCM & Reset Protect=0


 I am using two OS in my machine opensuse as well as windows
when I telnet from windows
telnet 192.168.127.254 4001
It promts a blank screen and for other IP or ports like 192.168.127.254 5064, 192.168.127.34 4732 etc. it simply says host not available so I think port 4001 should be good.
but when I run telnet 192.168.127.254 4001 or telnet 192.168.127.254 or telnet 192.168.127.254 5064 from linux it tries for some time and the times out.
 help me please.
 Thanks

Sunny






 


References:
problem connecting serial device with moxa 5150A Sunny Badkul
RE: problem connecting serial device with moxa 5150A Mark Rivers
Re: problem connecting serial device with moxa 5150A Sunny Badkul
RE: problem connecting serial device with moxa 5150A Mark Rivers
RE: problem connecting serial device with moxa 5150A Mark Rivers

Navigate by Date:
Prev: RE: Questions about set parameters to device by using epics Mark Rivers
Next: monitor subscription in areaDetector Pearson, Matthew R.
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
Navigate by Thread:
Prev: RE: problem connecting serial device with moxa 5150A Mark Rivers
Next: Re: problem connecting serial device with moxa 5150A Priller, John
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017
ANJ, 14 Feb 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·