Is your **server** behind a router or is it directly connected
to a modem?

firewall of router is set via its webpage interface; firewall of
a linux server is set using iptable, not sure about windows.

Вт, 01 ноя 2016, Ian Shannon написал(а):
> More info
> 
> When I set the JHS application running on the **server** and doing
>    netstat -a -n
> 
> I get a very long listing.  I have kept lines before and after
> with ports  80, 8092  and  65001.
> 
> 80  ===>  active apache server
> 8092  ===>  Dyalog APL application written many years ago 
> 65001 ===>  JHS application.
> 
> Both Apache and the Dyalog APL application respond correctly for browsing to
> 
> localhost:port
> 127.0.0.1:port
> LIDCOAP30:port                host name of server
> 121.243.11.138:port   host IP4 address of server
> 
> ----
> 
> Whereas the setup for the apache server may have done special
> configuration that I didn't see, when I set up the dialog APL
> application is was just a matter of copying the encapsulated
> workspace and executable file with a few extra DLLs and data
> files to the server.  On start the DYALOG APL application just
> runs!
> 
> (Though I now prefer J to Dyalog APL for a well-defined language)
> 
> 
> Output of netstat -a -n
> =======================
> 
> Active Connections
> 
>   Proto  Local Address          Foreign Address        State
>   TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
> <snip>
>   TCP    0.0.0.0:8080           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:8092           0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:8561           0.0.0.0:0              LISTENING
> <snip>
>   TCP    0.0.0.0:61616          0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:65015          0.0.0.0:0              LISTENING
>   TCP    0.0.0.0:65021          0.0.0.0:0              LISTENING
> <snip>
>   TCP    0.0.0.0:65168          0.0.0.0:0              LISTENING
>   TCP    127.0.0.1:80           127.0.0.1:58517        TIME_WAIT
>   TCP    127.0.0.1:80           127.0.0.1:58518        TIME_WAIT
>   TCP    127.0.0.1:80           127.0.0.1:58520        TIME_WAIT
>   TCP    127.0.0.1:80           127.0.0.1:58521        TIME_WAIT
>   TCP    127.0.0.1:80           127.0.0.1:58522        TIME_WAIT
>   TCP    127.0.0.1:80           127.0.0.1:58523        TIME_WAIT
>   TCP    127.0.0.1:31000        127.0.0.1:32001        ESTABLISHED
> <snip>
>   TCP    127.0.0.1:61103        0.0.0.0:0              LISTENING
>   TCP    127.0.0.1:65001        0.0.0.0:0              LISTENING
>   TCP    127.0.0.1:65001        127.0.0.1:58527        TIME_WAIT
>   TCP    127.0.0.1:65001        127.0.0.1:58564        TIME_WAIT
>   TCP    127.0.0.1:65001        127.0.0.1:58565        TIME_WAIT
>   TCP    127.0.0.1:65001        127.0.0.1:58568        TIME_WAIT
>   TCP    127.0.0.1:65001        127.0.0.1:58569        FIN_WAIT_2
>   TCP    127.0.0.1:65001        127.0.0.1:58571        TIME_WAIT
>   TCP    127.0.0.1:65001        127.0.0.1:58572        FIN_WAIT_2
>   TCP    141.243.11.138:80      141.243.11.138:58566   ESTABLISHED
>   TCP    141.243.11.138:80      141.243.11.138:58567   TIME_WAIT
>   TCP    141.243.11.138:139     0.0.0.0:0              LISTENING
> <snip>
>   TCP    141.243.11.138:7443    141.243.11.138:58557   ESTABLISHED
>   TCP    141.243.11.138:8561    141.243.11.138:49229   ESTABLISHED
> <snip>
>   TCP    141.243.11.138:64623   141.243.11.10:59333    ESTABLISHED
>   TCP    [::]:80                [::]:0                 LISTENING
>   TCP    [::]:135               [::]:0                 LISTENING
> <snip>
>   TCP    [::]:7443              [::]:0                 LISTENING
>   TCP    [::]:8080              [::]:0                 LISTENING
>   TCP    [::]:8561              [::]:0                 LISTENING
> <snip>
>   TCP    [::]:61616             [::]:0                 LISTENING
>   TCP    [::]:65015             [::]:0                 LISTENING
> 
> ===========
> 
> Although port 80 (apache) occurs for IP4 address of
> 0.0.0.0
> 127.0.0.1
> 121.143.11.138
> 
> The Dyalog APL application only has port 8092 for IP4 address of
> 0.0.0.0
> 
> I am at a loss to make head or tail of what is going on!
> 
> 
> Ian 
> Ian Shannon
> Science Strategy Branch
> Science Division
> Office of Environment and Heritage
> PO Box A290
> Sydney South
> NSW      1232
> T: +61 2 99 955 490
> E: [email protected] 
> 
> “Hang on to your youthful enthusiasms -- you’ll be able to use them better 
> when you’re older.”
> ― Seneca
> 
> 
> -----Original Message-----
> From: General [mailto:[email protected]] On Behalf Of Ian 
> Shannon
> Sent: Tuesday, 1 November 2016 1:39 PM
> To: [email protected]
> Subject: [Jgeneral] JHS start for *any* client
> 
> Hi there,
> 
> Thanks for the interest in helping.
> 
> <snip>
> 
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
> This email is intended for the addressee(s) named and may contain 
> confidential and/or privileged information. 
> If you are not the intended recipient, please notify the sender and then 
> delete it immediately.
> Any views expressed in this email are those of the individual sender except 
> where the sender expressly and with authority states them to be the views of 
> the NSW Office of Environment and Heritage.
> 
> PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm

-- 
regards,
====================================================
GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to