Lavalink - Ether to Serial Remote Port

Hi,

We are trying to get a Lavalink ELS 1 Port RS232 DB9 device working on an
SBS2003 R2 Premium system. Lavalink support says that the standard windows
firewall will block access to this device, but lpnat.sys blocks access to the
windows firewall so I am assuming that since ISA and a VPN are running that
the Windows Firewall is not. The unit should appear in their management
software so that an IP address can be mapped to a virtual COM port. The
device uses port 4098 and I created an access rule in ISA for [TCP out] for
all protected networks, but the built-in rule called SBS Protected Networks
Access Rule runs instead and my rule is listed way before this one.
Also, the Lavalink says that the unit will broadcast to the network and
their management app will respond to it.
Is ISA blocking the broadcast and why doesn't my rule run for port 4098
activity?
Here is a link to the device: http://www.lavalink.com/dev/index.php?id=47

By the way in their management app you can choose an icon that creates what
they call "WAN activation". Note: This is different than if the device would
appear after the broadcast. WAN activation loads a driver and creates a
virtual COM port that seems to works about 80% of the time. The app we are
running to access this COM port times out with a TX error about 20% of the
time.
Even though my rule does not run it still needs to be there for this to work
as described. Also, unless I use DHCP it will not work either. Current I
created a reservation to maintain a constant IP address.

Sorry for the long question, any help will greatly appreciated.


--
Thanks,

Frank Stumpo
.

Relevant Pages

  • Re: Correction
    ... Normally to physically disconnect is just a matter of reaching for the ... >> I have an ADSL connection which polls my computer from time to time, ... > disallow each and every port with Windows Firewall? ...
    (microsoft.public.windowsxp.messenger)
  • Re: Correction
    ... > the connection to the ISP to enable removing QoS." ... >> disallow each and every port with Windows Firewall? ... Windows Firewall does not open TCP port 135 or ...
    (microsoft.public.windowsxp.messenger)
  • Re: How do I Restrict port access to single IP Address
    ... Uncheck port 445. ... Keep in mind that Windows Firewall has limitations. ... > But for TCP 445 I still seem to be able to ping the machine ... > because of the scope setting against TCP 445 in the exceptions. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Windows XP SP2 Firewall - Developer Implications IPv4 inbound connections for services
    ... We're using Windows XP SP2. ... Windows Firewall blocks inbound traffic (including app listeners running ... You can programmatically add the port exception so that the ...
    (microsoft.public.security)
  • Re: Windows XP SP2 Firewall - Developer Implications IPv4 inbound connections for services
    ... We're using Windows XP SP2. ... Windows Firewall blocks inbound traffic (including app listeners running ... You can programmatically add the port exception so that the ...
    (microsoft.public.windowsxp.security_admin)
Loading