Location: Home >> Support >>  Technical FAQs >> Question 988

 Technical FAQs

Add to My Favorite FAQs
Question I can ping and telnet the NPort , but why can't I open the tty port even after installing the npreal driver under Linux?
Question Type Application
Updated Aug 18,2005
Hits 4541
Products NPort Express DE-211, NPort Express DE-311, NPort Server Lite DE-301/302/304/331/332/334, , NPort DE-311M
 

Solution

Suggestions


[Description]

I have downloaded and installed npbc.tgz from your site. When starting the system, mxloadsvr creates a node for /dev/ttyr00. However I cannot execute an stty -a < /dev/ttyr00 on the device. The command hangs until I press ctrl C. The npreal2d.log gives the following :

07-14-2005 22:34:12 MOXA real TTY daemon program starting (Ver1.10 (4/22/2005))...
07-14-2005 22:34:12 Socket connect fail (201.1.1.122,TCP port 950) !

I can ping the de-311 and telnet to it.


[Possibilities]

One possibility is that the IP address of the PC was not in the access control table of the NPort. This could be the case if you’ve installed the NPort in any other Windows system.

Normally, the NPort window driver will add the IP address of host PC into the access control table automatically while you install it. Since then, only the PC with IP address in this table can access the NPort. However, if you move the NPort to another PC running Linux, the Linux driver will not follow the same procedure as the Windows driver, so the new PC still cannot access the NPort.

[Solution]

The solution is to use the Configurator in the Windows system to add the IP address of the new PC, or clear all IP addresses in the access control table of NPort. Then, the new PC running Linux will be able open the tty port.

 

Related Questions

I am unable to change the IP address or other server properties.

You would like to allow one more host to access your NPort Server Pro, but are unable to reach the Access Control page.

After installing NPort Server Pro, the NPort Pro Manager program indicates "'Un-authorized" status for some of the ports.

While running NPort Pro Manager, a question mark (?) shows up on top of the server icon, I am unable to enter server properties.

You cannot find the server after rebooting your Windows NT/95/98 server.

How do I to extend the distance between two RS-232 devices?

When using NPort Express, what should I do when the Win32 COMM API functions return fail, or the PComm Pro library functions return the Fail code SIO_WIN32FAIL?

Why I can Ping and Telnet an NPort Server from a PC connected to the same LAN, but NPort Server Manager and Firmware Utility fail to find the NPort Server?

How to shorten the "Open Port Timeout" if the remote NPort (Host based/Driver mode) is not on-line?

I've installed NPort/NE series Driver properly, but why can not my application program (AP) open ports successfully?

I can PING and Telnet NPort, but why can not my own TCP Client program successfully connect with NPort?

I can PING & Telnet NPort, but why can not NPort connect with my own TCP Server program properly?

When I install NPort Real COM driver, I see a "Fast Flush" option, what does it mean?

I can PING & Telnet NPort. Why can not my own UDP program Rx/Tx data via NPort properly?

When I install NPort Real COM driver, I discovered native COM port performance is faster than NPort, is that normal? And how to improve it?

What are the characteristics of the reset button?

What are the characteristics of the reset button for NPort Pro/Lite and Async Server?

I installed NPort Management Suite to my windows but why can't I see any COM ports in the "Device Manager"?

After I installed and started NPort Management Suite on windows 95, I notice that the library WS2_32.dll is missing. What is the problem?

Why can't my NPort connect to Cisco Catalyst 6500 series Ethernet Switch (Link LED Off)?

Provide Feedback

Quality of this article
Poor 1 2 3 4 5 Excellent

| Products | Applications | Support | News & Events | Where to Buy | About Moxa | My Moxa | Contact Moxa | Sitemap |