<![CDATA[LAVA: Forums - Serial Over IP]]>

<![CDATA[LAVA: Forums - Serial Over IP]]> https://forum.lavalink.com/ Thu, 30 Apr 2026 09:03:47 +0000 MyBB <![CDATA[Unable to open 1 com port on 2 port esl]]> https://forum.lavalink.com/showthread.php?tid=56937 Fri, 06 Jan 2023 00:08:09 +0000 sysimgrp]]> https://forum.lavalink.com/showthread.php?tid=56937 <![CDATA[Ethernet to 2 RS232]]> https://forum.lavalink.com/showthread.php?tid=51558 Wed, 28 Feb 2018 23:31:26 +0000 ve6aq]]> https://forum.lavalink.com/showthread.php?tid=51558
I have connected the device directly to my computer with a cross cable but nothing.
The power red light is on (12v) and one yellow light on the cat5 connector. I cannot ping the device on this setup.

I have looked on my router and it is not on there.
What else can I do?
Denis]]>
I have connected the device directly to my computer with a cross cable but nothing.
The power red light is on (12v) and one yellow light on the cat5 connector. I cannot ping the device on this setup.

I have looked on my router and it is not on there.
What else can I do?
Denis]]> <![CDATA[Connection Issue]]> https://forum.lavalink.com/showthread.php?tid=51319 Tue, 18 Apr 2017 11:52:42 +0000 cgafa]]> https://forum.lavalink.com/showthread.php?tid=51319
I am trying to use an ESL 4 port device using Windows10. The device manager looks fine, I am seeing all ports (green) and I can access the device from the browser as well. However I cannot access the ports. I tried to send data using code (simple application in c# that threw an exception when I tried to open the port) and also tried accessing the port using putty (again did not manage to open port).

Any ideas please?]]>
I am trying to use an ESL 4 port device using Windows10. The device manager looks fine, I am seeing all ports (green) and I can access the device from the browser as well. However I cannot access the ports. I tried to send data using code (simple application in c# that threw an exception when I tried to open the port) and also tried accessing the port using putty (again did not manage to open port).

Any ideas please?]]> <![CDATA[How to determine IRQ assignment in IP Extender]]> https://forum.lavalink.com/showthread.php?tid=49989 Tue, 29 Nov 2016 22:28:11 +0000 TAOlson]]> https://forum.lavalink.com/showthread.php?tid=49989
Minidump reports Interrupt storm as source of fatal.]]>
Minidump reports Interrupt storm as source of fatal.]]> <![CDATA[Trouble in Windows x64]]> https://forum.lavalink.com/showthread.php?tid=21225 Fri, 01 Apr 2016 19:30:38 +0000 Fry]]> https://forum.lavalink.com/showthread.php?tid=21225
First attempted upgrade was to Windows 10 x64 using the Windows 8 Lava ESL WESL 2015_01_13a setup. The CV-22 software works in Windows 10 x64 using the generic USB/RS-232 adapter, but we can not get it to work using the ESL4-DB9. When we try initiating communications the register sees the attempt and locks the keyboard, the lights flash a few times on the ESL4-DB9, and then we eventually get an error "4506 - Protocol or communication packet error" in the CV-22 software. We've tried every configuration and driver option we can find to no avail. The ports activate and install fine in Windows, communications start up, and then fail with the same error every time using the ESL4-DB9

We put a Hyper-V Windows XP virtual machine on the Windows 10 x64 computer, and installed the old manager/drivers and CV-22 software, and once again, everything works as expected inside the virtual machine.

We next tried Windows 7 x64 concluding that the Windows 8.1 drivers may not work for Windows 10. We get the same results in Windows 7 x64 as we do in Windows 10 x64. Communications are initiated, the register sees communications and locks the keyboard, we wait, we get the same error "4506 - Protocol or communication packet error".

Any ideas on getting the ESL4-DB9 to work in the CV-22 application on something newer than Windows XP? USB/RS-232 works fine, but we sometimes need access at longer distances than that will accommodate, and a virtual XP machine almost defeats the purpose of upgrading Windows.

The ESL4-DB9 firmware is 6.1.0 2007/03/29]]>
First attempted upgrade was to Windows 10 x64 using the Windows 8 Lava ESL WESL 2015_01_13a setup. The CV-22 software works in Windows 10 x64 using the generic USB/RS-232 adapter, but we can not get it to work using the ESL4-DB9. When we try initiating communications the register sees the attempt and locks the keyboard, the lights flash a few times on the ESL4-DB9, and then we eventually get an error "4506 - Protocol or communication packet error" in the CV-22 software. We've tried every configuration and driver option we can find to no avail. The ports activate and install fine in Windows, communications start up, and then fail with the same error every time using the ESL4-DB9

We put a Hyper-V Windows XP virtual machine on the Windows 10 x64 computer, and installed the old manager/drivers and CV-22 software, and once again, everything works as expected inside the virtual machine.

We next tried Windows 7 x64 concluding that the Windows 8.1 drivers may not work for Windows 10. We get the same results in Windows 7 x64 as we do in Windows 10 x64. Communications are initiated, the register sees communications and locks the keyboard, we wait, we get the same error "4506 - Protocol or communication packet error".

Any ideas on getting the ESL4-DB9 to work in the CV-22 application on something newer than Windows XP? USB/RS-232 works fine, but we sometimes need access at longer distances than that will accommodate, and a virtual XP machine almost defeats the purpose of upgrading Windows.

The ESL4-DB9 firmware is 6.1.0 2007/03/29]]> <![CDATA[Firmware for Startech]]> https://forum.lavalink.com/showthread.php?tid=20978 Wed, 02 Dec 2015 03:12:32 +0000 mn32]]> https://forum.lavalink.com/showthread.php?tid=20978 <![CDATA[Device Manager cannot find ESL.]]> https://forum.lavalink.com/showthread.php?tid=20977 Fri, 27 Nov 2015 02:36:05 +0000 TheLastAlly]]> https://forum.lavalink.com/showthread.php?tid=20977
I am using a crossover cable connecting the RS-232 to my PC, a Windows 7 (x64 bit) computer, yet when I install the latest driver/firmware, and open the WIN7_2008_XP_2000 folder, then open setup.exe, it installs as supposed to, etc.

However when the install finishes and the software opens up, it does not show the RS232 under "Ether-Links near me", in fact, you cant even expand "Ether-links near me".

As to some solution I read that didn't work:
Disable your firewall: I have already done that, no significant results.

Please answer back onto some possible solutions.]]>
I am using a crossover cable connecting the RS-232 to my PC, a Windows 7 (x64 bit) computer, yet when I install the latest driver/firmware, and open the WIN7_2008_XP_2000 folder, then open setup.exe, it installs as supposed to, etc.

However when the install finishes and the software opens up, it does not show the RS232 under "Ether-Links near me", in fact, you cant even expand "Ether-links near me".

As to some solution I read that didn't work:
Disable your firewall: I have already done that, no significant results.

Please answer back onto some possible solutions.]]> <![CDATA[[FAQ] My ESL isn't displayed in the LAVA Manager]]> https://forum.lavalink.com/showthread.php?tid=20962 Tue, 28 Jul 2015 16:13:50 +0000 LavaSupport]]> https://forum.lavalink.com/showthread.php?tid=20962 Question:
I have an ESL on my LAN that I can access (i.e. Ping and/or view the ESL's Embedded Webpage) however I am unable to see the ESL in the LAVA Manager. Is there some way to view the ESL?

Answer:
If you are able to verify network connectivity to your ESL's but are unable to see them in the LAVA Manager then you most likely are dealing with: a firewall issue; anti-virus issue; or network hardware issue.

In order for the LAVA Manager to display all the ESL's on your network it first needs to send out a Discovery Packet, also referred to as a Broadcast MAC Packet, to determine all the ESLs present on the network. This Discover Packet is ignored/discarded by all non-LAVA devices, however any LAVA device understands the importance of this packet and will respond to the LAVA Manager indicating that it is present.

Unfortunately certain applications (i.e. Firewalls, Anti-Virus) and network hardware (i.e. Intelligent Switches) see this Discovery Package as Network Interference and opt not to propagate the Discovery Packet to its intended target resulting in the LAVA Manager not being able to see any devices.

Solution:
One option to allow the discovery would be to temporarily disable either the Firewall, Anti-Virus application in order to allow the discovery the ESLs. If you are performing an occasional configuration of the ESL and/or a one time Activation this would actually be the simplest thing to do. Once the ESLs have been configured be sure to re-enable any security settings that you temporarily disabled.

LAVA does not recommend turning off a firewall as a long-term solution to enabling LAVA Ether-Link Manager access to a LAVA Ether-Serial Link.

Another far more secure option would be correctly configure the blocking application, or network hardware, to allow propagation of the Discovery Packets throughout the Network.

The LAVA Manager application uses the following protocols for communication:

UDP Port 4101 for detection of LAVA Ether-Serial Links
- broadcasts to a destination IP address (to the LAVA Ether-Serial Link)
- use of directed MAC addresses (again, to the LAVA Ether-Serial Link)

Applies to:
All ESL Devices- LAVA Support[/list]]]> Question:
I have an ESL on my LAN that I can access (i.e. Ping and/or view the ESL's Embedded Webpage) however I am unable to see the ESL in the LAVA Manager. Is there some way to view the ESL?

Answer:
If you are able to verify network connectivity to your ESL's but are unable to see them in the LAVA Manager then you most likely are dealing with: a firewall issue; anti-virus issue; or network hardware issue.

In order for the LAVA Manager to display all the ESL's on your network it first needs to send out a Discovery Packet, also referred to as a Broadcast MAC Packet, to determine all the ESLs present on the network. This Discover Packet is ignored/discarded by all non-LAVA devices, however any LAVA device understands the importance of this packet and will respond to the LAVA Manager indicating that it is present.

Unfortunately certain applications (i.e. Firewalls, Anti-Virus) and network hardware (i.e. Intelligent Switches) see this Discovery Package as Network Interference and opt not to propagate the Discovery Packet to its intended target resulting in the LAVA Manager not being able to see any devices.

Solution:
One option to allow the discovery would be to temporarily disable either the Firewall, Anti-Virus application in order to allow the discovery the ESLs. If you are performing an occasional configuration of the ESL and/or a one time Activation this would actually be the simplest thing to do. Once the ESLs have been configured be sure to re-enable any security settings that you temporarily disabled.

LAVA does not recommend turning off a firewall as a long-term solution to enabling LAVA Ether-Link Manager access to a LAVA Ether-Serial Link.

Another far more secure option would be correctly configure the blocking application, or network hardware, to allow propagation of the Discovery Packets throughout the Network.

The LAVA Manager application uses the following protocols for communication:

UDP Port 4101 for detection of LAVA Ether-Serial Links
- broadcasts to a destination IP address (to the LAVA Ether-Serial Link)
- use of directed MAC addresses (again, to the LAVA Ether-Serial Link)

Applies to:
All ESL Devices- LAVA Support[/list]]]> <![CDATA[[FAQ] What is the Default Password for my ESL?]]> https://forum.lavalink.com/showthread.php?tid=20961 Tue, 28 Jul 2015 15:00:57 +0000 LavaSupport]]> https://forum.lavalink.com/showthread.php?tid=20961 Question:
What is the default password for my ESL?

Answer:
For most ESLs the factory default passwords are:

Administrative Access = admin
Port Level Access = portN (where N is the logical port number .... i.e. Port 1 would be port1)

Administrative Access = admin
Port Level Access = portN (where N is the logical port number .... i.e. Port 1 would be port1)

With the Administrative Password have full access to all configuration settings on the ESL. This will allow you change in the Network Settings (eg IP Address, NETBIOS name, etc) in addition to being able to modify the Port Configurations (eg Port Mode, Port Settings and Access Restrictions) for all Ports on the ESL.

With the Port Level password you will be limited to the the viewing and modification of the appropriate Port's Configurations (eg Port Mode, Port Settings and Access Restrictions).

NOTE: Once a password has been modified by the end user then the factory default passwords will no longer be valid.

Therefore if you have an ESL that has been reconfigured to an unknown password then the best course of action would be to restore the ESL to its factory default settings.

[HOW TO] Reset an ESL to factory defaults

Applies to:
All ESL Devices

- LAVA Support]]> <![CDATA[ESL 2-port DB9 - activation issue]]> https://forum.lavalink.com/showthread.php?tid=20957 Mon, 27 Jul 2015 18:37:33 +0000 mundyj]]> https://forum.lavalink.com/showthread.php?tid=20957 In a nut shell I am unable to initiate communications through either of the serial ports.

To the box itself, the Ethernet connection works well, I am able to communicate via a telnet client, access and control the device through the browser and the Lave Device Manager.  The single exception that the "activate all" option is not enabled.

Any help pointing me in the right direction would be greatly appreciated.]]> In a nut shell I am unable to initiate communications through either of the serial ports.

To the box itself, the Ethernet connection works well, I am able to communicate via a telnet client, access and control the device through the browser and the Lave Device Manager.  The single exception that the "activate all" option is not enabled.

Any help pointing me in the right direction would be greatly appreciated.]]> <![CDATA[[HOW TO] Reset an ESL to factory defaults]]> https://forum.lavalink.com/showthread.php?tid=20954 Fri, 24 Jul 2015 20:14:39 +0000 LavaSupport]]> https://forum.lavalink.com/showthread.php?tid=20954
There are a variety of reasons why this may be desirable:

the Administrative password to the device is not known
the device is locked up and cannot be successfully restarted by cycling its power
you've configured the ESL incorrectly and would simply like to return it to its original settings

There are two different methods for resetting an ESL: Software Reset and Hardware Reset. Both methods have the same result, the only difference being that depending on your situation one method may not be a option. That being said regardless of the method resetting an ESL to its factory defaults will remove all user-configured settings, including port/network settings, access restrictions, and passwords.

Software Reset:

A Software reset is by far the simplest method for restoring an ESL to its default settings, it has the additional benefit of being able to be performed remotely (via the LAVA Ether-Link Manager or the ESLs Webpage).

The one drawback though is that you need the ESLs Administrative Password in addition to the ability to communicated with the ESL. So if you're experiencing any communication issues and/or you don't know the Administrative Password for the ESL then a Software Reset may not be an option.

Hardware Reset:

A Hardware reset, on the other hand, is far more common. Its gives you the ability to recover from larger issues such as a forgotten Administrative Password or a lockup issue.

The benefit to this method is that it avoids the need to communicate directly with the ESL, however for hardware reset you must be able to open up the ESLs enclosure in order to perform the reset.

Performing a Software Reset:

A Software Reset can be perform via the LAVA Ether-Link Manager or through the ESLs Embedded Webpage. Regardless of which method you choose you will need the ESLs Administrative Password.

To reset the ESL via the Embedded Webpage:

Open your web browser.
In the address bar enter the current IP Address of the ESL (eg http://192.168.2.2) and press enter.
Once the webpage has loaded type the Administrative Password into the "Enter Password:" field.
Click Configure.
Click on "Network Settings" from the "Administrative Menu".
Once the "Network Settings" page has loaded up click on "Restore factory defaults and reboot device".
Your ESL should now be reset to its factory defaults.

To reset the ESL via the Ether-Link Manager:

Open the LAVA Ether-Link Manager.
In the right hand pane, under Ether-Links Near Me, the ESL to be reset should be displayed.
Right click on the ESL and select Advanced > Restore Defaults
Note: If Restore Defaults has been greyed out then you will need to unlock the ESL
- To Unlock the ESL right click on the ESL, select "Unlock", enter the Administrative Password and press return.
You will be asked to verify that you do want to Restore Defaults, Click Yes.
Your ESL should now be reset to its factory defaults.

Performing a Hardware Reset:

As previously stated a hardware reset does the same thing as the software reset and is useful when the password to the device is not known or the device is locked up and cannot be successfully restarted by cycling its power.

To reset the ESL:

Disconnect power from the device.
Remove the four black screws on the bottom of the ESL and remove the lid.
On the main board of the device, locate the jumper marked "J15".
NOTE: Do not use the jumper pair identified as "RST".
- On 1, 2, and 4 port ESLs these jumper pairs are slightly separate and separately identified.
- On the 8 and 16 port ESLs J15 and RST are located together but are separately identified.
  
  J15_sm (1).png (Size: 313.68 KB / Downloads: 0)
  J15 with jumper_sm.png (Size: 305.58 KB / Downloads: 0)
Short the two pins of J15 with either a jumper, a screwdriver, or other metallic conductor.
Leaving the pins shorted, power up the device. Allow 20 seconds for a full power-up cycle.
Disconnect power from the device.
Remove the jumper from J15.
Replace the lid and reinsert the four screws.
Power up the device.
Your ESL should now be reset to its factory defaults.

Factory Default Settings:
Once restored to its factory default settings your ESLs settings should reflect the main settings below.

Device settings:

Admin Password: admin
IP Address: 192.168.0.35

Port 1:

Port Password: port1
TCP Port: 4098
Default Mode: Driver Mode

Port 2 (if available):

Port Password: port2
TCP Port: 4097
Default Mode: Driver Mode

With each additional port the default port password reflects the port number and the TCP port decreases by one.]]>
There are a variety of reasons why this may be desirable:

the Administrative password to the device is not known
the device is locked up and cannot be successfully restarted by cycling its power
you've configured the ESL incorrectly and would simply like to return it to its original settings

Open your web browser.
In the address bar enter the current IP Address of the ESL (eg http://192.168.2.2) and press enter.
Once the webpage has loaded type the Administrative Password into the "Enter Password:" field.
Click Configure.
Click on "Network Settings" from the "Administrative Menu".
Once the "Network Settings" page has loaded up click on "Restore factory defaults and reboot device".
Your ESL should now be reset to its factory defaults.

To reset the ESL via the Ether-Link Manager:

Open the LAVA Ether-Link Manager.
In the right hand pane, under Ether-Links Near Me, the ESL to be reset should be displayed.
Right click on the ESL and select Advanced > Restore Defaults
Note: If Restore Defaults has been greyed out then you will need to unlock the ESL
- To Unlock the ESL right click on the ESL, select "Unlock", enter the Administrative Password and press return.
You will be asked to verify that you do want to Restore Defaults, Click Yes.
Your ESL should now be reset to its factory defaults.

Disconnect power from the device.
Remove the four black screws on the bottom of the ESL and remove the lid.
On the main board of the device, locate the jumper marked "J15".
NOTE: Do not use the jumper pair identified as "RST".
- On 1, 2, and 4 port ESLs these jumper pairs are slightly separate and separately identified.
- On the 8 and 16 port ESLs J15 and RST are located together but are separately identified.
  
  J15_sm (1).png (Size: 313.68 KB / Downloads: 0)
  J15 with jumper_sm.png (Size: 305.58 KB / Downloads: 0)
Short the two pins of J15 with either a jumper, a screwdriver, or other metallic conductor.
Leaving the pins shorted, power up the device. Allow 20 seconds for a full power-up cycle.
Disconnect power from the device.
Remove the jumper from J15.
Replace the lid and reinsert the four screws.
Power up the device.
Your ESL should now be reset to its factory defaults.

Factory Default Settings:
Once restored to its factory default settings your ESLs settings should reflect the main settings below.

Device settings:

Admin Password: admin
IP Address: 192.168.0.35

Port 1:

Port Password: port1
TCP Port: 4098
Default Mode: Driver Mode

Port 2 (if available):

Port Password: port2
TCP Port: 4097
Default Mode: Driver Mode

With each additional port the default port password reflects the port number and the TCP port decreases by one.]]> <![CDATA[Serial 2 TCPIP portserver question]]> https://forum.lavalink.com/showthread.php?tid=20952 Fri, 24 Jul 2015 13:54:16 +0000 roetman]]> https://forum.lavalink.com/showthread.php?tid=20952 [font='Helvetica Neue', Helvetica, Arial, sans-serif]Please provide the following information:
[/font]

If the LLbox is to be configured behind a firewall, Which ports should be excluded in order to get the LL to work?

[font='Helvetica Neue', Helvetica, Arial, sans-serif]Thanks,[/font]]]> [font='Helvetica Neue', Helvetica, Arial, sans-serif]Please provide the following information:
[/font]

If the LLbox is to be configured behind a firewall, Which ports should be excluded in order to get the LL to work?

[font='Helvetica Neue', Helvetica, Arial, sans-serif]Thanks,[/font]]]> <![CDATA[ESL Firmware DOwngrade]]> https://forum.lavalink.com/showthread.php?tid=20951 Fri, 24 Jul 2015 13:03:39 +0000 byeo.douyee]]> https://forum.lavalink.com/showthread.php?tid=20951 Hi we bought a lot od Lavalink dual rs232 to Lan adaptor, the are all runing the LAVA_ESL_1_2_42007_0325a
the last unit we bought last year is runing on LAVA_ESL_WESL_2013_07_22a we try to down grade the unit but the upgrade software for the 2007 cannot detect the new unit. the old lavalink manager also cannot detect the New unit. We decide to downgrade but the software gap is too big. CAn he get the older version , version in between the 2013 and 2007; so that we can try to do Progessive downgrading of the firmware.

Pls let me know if this is possible]]> Hi we bought a lot od Lavalink dual rs232 to Lan adaptor, the are all runing the LAVA_ESL_1_2_42007_0325a
the last unit we bought last year is runing on LAVA_ESL_WESL_2013_07_22a we try to down grade the unit but the upgrade software for the 2007 cannot detect the new unit. the old lavalink manager also cannot detect the New unit. We decide to downgrade but the software gap is too big. CAn he get the older version , version in between the 2013 and 2007; so that we can try to do Progessive downgrading of the firmware.

Pls let me know if this is possible]]> <![CDATA[ESL Connectivity]]> https://forum.lavalink.com/showthread.php?tid=20944 Thu, 23 Jul 2015 14:48:16 +0000 kemper-vt]]> https://forum.lavalink.com/showthread.php?tid=20944
Is there a work around for this? also when logged into the lava manager we can no longer see the adapter but can connect to the device using the computer that setup the adapter.

is there a network setting that is not enable that would allow us to connect into anywhere we might be in our network and see the adapter with the manager?]]>
Is there a work around for this? also when logged into the lava manager we can no longer see the adapter but can connect to the device using the computer that setup the adapter.

is there a network setting that is not enable that would allow us to connect into anywhere we might be in our network and see the adapter with the manager?]]> <![CDATA[ESL-1-DB9 COM-Port Activation not possible]]> https://forum.lavalink.com/showthread.php?tid=20941 Wed, 22 Jul 2015 16:43:18 +0000 oli_jan]]> https://forum.lavalink.com/showthread.php?tid=20941 Today I tried several hours to get my Lava Ether-Serial-Link to work under Win7 x64 SP1 an all available updates...

I Installed the latest Ether-Link-Device-Manager V5.11.0...

The ESL is shown under "Ether Links near me", the Web-Page is accessible and the Port 1 is "inactive"...

I tried to activate Port Nr. 1 and get an incomplete Message "The acitvation was successful. Port 1 on Lava Ether-Serial-Link 1-DB9 (....) has been activated for use as on this Computer".

The Number of the COM-Port is not displayed in the message. The Port of the ESL is not displayed under "My Computer" and there is no item in the Device-Manager..

I had a look to your FAQ's, but couldn't find a helpful Topic..

The most interesting Topic "Cannot open COM-Port on the Ether Serial Link" ends where my Problem starts...

Thank you very much for your answer!!]]> Today I tried several hours to get my Lava Ether-Serial-Link to work under Win7 x64 SP1 an all available updates...

I Installed the latest Ether-Link-Device-Manager V5.11.0...

The ESL is shown under "Ether Links near me", the Web-Page is accessible and the Port 1 is "inactive"...

I tried to activate Port Nr. 1 and get an incomplete Message "The acitvation was successful. Port 1 on Lava Ether-Serial-Link 1-DB9 (....) has been activated for use as on this Computer".

The Number of the COM-Port is not displayed in the message. The Port of the ESL is not displayed under "My Computer" and there is no item in the Device-Manager..

I had a look to your FAQ's, but couldn't find a helpful Topic..

The most interesting Topic "Cannot open COM-Port on the Ether Serial Link" ends where my Problem starts...

Thank you very much for your answer!!]]>