Gentlemen,

I'm experimenting with communication using WebSocketClient() and 
WebSocketHandler(). All goes well when server and client run on one 
machine, but when I try to connect to the server from a different 
computer the oClient:connect() fails. The IP and port are correct. 
Stopping the firewall does not help either. Any ideas on how to find out 
what is wrong ?

Kind regards,
Jan Groenestein

Jan Groenestein wrote:

> Gentlemen,
> 
> I'm experimenting with communication using WebSocketClient() and 
> WebSocketHandler(). All goes well when server and client run on one 
> machine, but when I try to connect to the server from a different 
> computer the oClient:connect() fails. The IP and port are correct. 
> Stopping the firewall does not help either. Any ideas on how to find out 
> what is wrong ?

Are you sure the "server" socket is bound to the correct interface (not
localhost or 127.0.0.1)?

You can check with netstat /a on the commandline (or tcpview if you prefer
a graphical interface)

Thomas

Thomas Braun schreef op 14-10-2014 8:40:
> Jan Groenestein wrote:
>
>> Gentlemen,
>>
>> I'm experimenting with communication using WebSocketClient() and
>> WebSocketHandler(). All goes well when server and client run on one
>> machine, but when I try to connect to the server from a different
>> computer the oClient:connect() fails. The IP and port are correct.
>> Stopping the firewall does not help either. Any ideas on how to find out
>> what is wrong ?
>
> Are you sure the "server" socket is bound to the correct interface (not
> localhost or 127.0.0.1)?
>
> You can check with netstat /a on the commandline (or tcpview if you prefer
> a graphical interface)
>
> Thomas
>
Hi Thomas,
Thanks for the hint, I tried it and found that the server is listening 
on "local address 0.0.0.0 port 81". Netstat also shows an "external 
address" which is my PC's name :Groenestein=PC:0
So, I now know that the server is listening on port 81, but I have no 
idea what the "local address" or "external address" values mean.

Kind regards,
Jan Groenestein

Hi Jan,

I can confirm that the HttpEndpoint does not associate the socket on which 
it is listening with a name or an ip address. Tp verify your observation, 
can you reproduce the problem using the picture server sample? What are the 
operating systems involved on the server and on the client?

With my best regards,

  Andreas Herdt
  Alaska Software

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

Technical Support:      support@alaska-software.com

News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm

Fax European Office:    +49 (0) 61 96 - 77 99 99 23
Fax US Office:          +1 (646) 218 1281
--------------------------------------------------------------------

"Jan Groenestein" wrote in message 
news:2e4c36b4$5660a999$7782@news.alaska-software.com...
> Thomas Braun schreef op 14-10-2014 8:40:
>> Jan Groenestein wrote:
>>
>>> Gentlemen,
>>>
>>> I'm experimenting with communication using WebSocketClient() and
>>> WebSocketHandler(). All goes well when server and client run on one
>>> machine, but when I try to connect to the server from a different
>>> computer the oClient:connect() fails. The IP and port are correct.
>>> Stopping the firewall does not help either. Any ideas on how to find out
>>> what is wrong ?
>>
>> Are you sure the "server" socket is bound to the correct interface (not
>> localhost or 127.0.0.1)?
>>
>> You can check with netstat /a on the commandline (or tcpview if you 
>> prefer
>> a graphical interface)
>>
>> Thomas
>>
> Hi Thomas,
> Thanks for the hint, I tried it and found that the server is listening on 
> "local address 0.0.0.0 port 81". Netstat also shows an "external address" 
> which is my PC's name :Groenestein=PC:0
> So, I now know that the server is listening on port 81, but I have no idea 
> what the "local address" or "external address" values mean.
>
> Kind regards,
> Jan Groenestein

Hi Andreas,

Nice sample ! Works great when the browser runs on the same computer as 
the server. But accessing this server from a different computer does not 
work.
I wonder what purpose this all serves if you can only play around on one 
computer ? Is it a bug which causes this ? If so, will it get fixed ?

Kind regards,
Jan Groenestein

Andreas Herdt schreef op 15-10-2014 16:25:
> Hi Jan,
>
> I can confirm that the HttpEndpoint does not associate the socket on
> which it is listening with a name or an ip address. Tp verify your
> observation, can you reproduce the problem using the picture server
> sample? What are the operating systems involved on the server and on the
> client?
>
> With my best regards,
>

Hi Jan,

Please refer to my previous posting.

To sum up: For the time being I assume that the reason is the server
socket is not properly bound to the machine on which the server shall
run.

As you now confirm that with the pictureserver sample from the samples
multitier folder the same issue arises, shure this needs to be fixed.

For completeness, please inform us about your server client operating
system constellation.

  Andreas Herdt
  Alaska Software

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

Technical Support:      support@alaska-software.com

News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm

Fax European Office:    +49 (0) 61 96 - 77 99 99 23
Fax US Office:          +1 (646) 218 1281
--------------------------------------------------------------------

"Jan Groenestein" wrote in message 
news:41f4dc2e$5cdc59bd$13605@news.alaska-software.com...
> Hi Andreas,
>
> Nice sample ! Works great when the browser runs on the same computer as 
> the server. But accessing this server from a different computer does not 
> work.
> I wonder what purpose this all serves if you can only play around on one 
> computer ? Is it a bug which causes this ? If so, will it get fixed ?
>
> Kind regards,
> Jan Groenestein
>
> Andreas Herdt schreef op 15-10-2014 16:25:
>> Hi Jan,
>>
>> I can confirm that the HttpEndpoint does not associate the socket on
>> which it is listening with a name or an ip address. Tp verify your
>> observation, can you reproduce the problem using the picture server
>> sample? What are the operating systems involved on the server and on the
>> client?
>>
>> With my best regards,
>>
>

Hi Andreas,

The server runs on a Windows 7 professional. The client is run from a 
Windows 8.1 machine.

Regards,
Jan

Andreas Herdt schreef op 15-10-2014 23:20:
> Hi Jan,
>
> Please refer to my previous posting.
>
> To sum up: For the time being I assume that the reason is the server
> socket is not properly bound to the machine on which the server shall
> run.
>
> As you now confirm that with the pictureserver sample from the samples
> multitier folder the same issue arises, shure this needs to be fixed.
>
> For completeness, please inform us about your server client operating
> system constellation.
>

Andreas,

Is there any news on this subject ? I need to decide at some point what 
tools we will use for future development. I'd like to know if I will be 
able to work with the websocketClient().

Kind regards,
Jan Groenestein

Andreas Herdt schreef op 15-10-2014 23:20:
> Hi Jan,
>
> Please refer to my previous posting.
>
> To sum up: For the time being I assume that the reason is the server
> socket is not properly bound to the machine on which the server shall
> run.
>
> As you now confirm that with the pictureserver sample from the samples
> multitier folder the same issue arises, shure this needs to be fixed.
>
> For completeness, please inform us about your server client operating
> system constellation.
>

Hi Jan,

I have tried to reproduce the trouble you have and I failed. The
pictureserver is running on a Win7 machine, the webbrowser
is running on Win8.1. I was able to run the application with
http://AW05:81/pictureserver/start, where AW05 is the
computername of Win7.

I would like you to try this again. Of course in best case the
Firewall is switched off when doing the first steps. Please also
try the URL using the computername and additionally the
IP4 address of the machine where the server is running.

If this is to now awail then please try to contact a web server
which might be running on the Win7 Server machine. Also
try a sample from the ASInet sample collection. You find the
folder sockets there that implement a client and a server.
With those samples, is a connection possible?

With my best regards,

  Andreas Herdt
  Alaska Software

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

Technical Support:      support@alaska-software.com

News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm

Fax European Office:    +49 (0) 61 96 - 77 99 99 23
Fax US Office:          +1 (646) 218 1281
--------------------------------------------------------------------

"Jan Groenestein" wrote in message 
news:42e73e1d$704469b2$5d0c@news.alaska-software.com...
> Andreas,
>
> Is there any news on this subject ? I need to decide at some point what 
> tools we will use for future development. I'd like to know if I will be 
> able to work with the websocketClient().
>
> Kind regards,
> Jan Groenestein
>
> Andreas Herdt schreef op 15-10-2014 23:20:
>> Hi Jan,
>>
>> Please refer to my previous posting.
>>
>> To sum up: For the time being I assume that the reason is the server
>> socket is not properly bound to the machine on which the server shall
>> run.
>>
>> As you now confirm that with the pictureserver sample from the samples
>> multitier folder the same issue arises, shure this needs to be fixed.
>>
>> For completeness, please inform us about your server client operating
>> system constellation.
>>
>

Jan Groenestein wrote:

> Hi Thomas,
> Thanks for the hint, I tried it and found that the server is listening 
> on "local address 0.0.0.0 port 81".

0.0.0.0 = listen and accept requests on all interfaces

> address" which is my PC's name :Groenestein=PC:0
> So, I now know that the server is listening on port 81, but I have no 
> idea what the "local address" or "external address" values mean.

No idea - Groenenstein=PC might be the name of your machine...?

Thomas

Thomas Braun schreef op 16-10-2014 8:38:
> Jan Groenestein wrote:
>
>> Hi Thomas,
>> Thanks for the hint, I tried it and found that the server is listening
>> on "local address 0.0.0.0 port 81".
>
> 0.0.0.0 = listen and accept requests on all interfaces
>
>> address" which is my PC's name :Groenestein=PC:0
>> So, I now know that the server is listening on port 81, but I have no
>> idea what the "local address" or "external address" values mean.
>
> No idea - Groenenstein=PC might be the name of your machine...?
>
> Thomas
>

Hi Thomas,

Haha, you're funny. My point is : as I have little experience with the 
basic internet communication techniques. I don't know how to interpret 
this info. For instance, what does "external address" mean ? I was 
hoping someone could shed some light on the subject as I'm now sort of 
groping around in darkness.
Anyway, as I understand now I accidentally seem to have hit on a bug, 
according to Andreas. I trust that he will be the light shedder.

Regards,
Jan Groenestein

Jan Groenestein wrote:

> this info. For instance, what does "external address" mean ? 

There are two columns with addresses in netstat:

 Proto  Lokale Adresse         Remoteadresse          Status
 TCP    127.0.0.1:119          ELWS021:49682          HERGESTELLT
 TCP    127.0.0.1:119          ELWS021:49683          HERGESTELLT

The first one is the address and port on which the server process is
listening, the other one is the address and port of the client that is
connected to the server - in your case this is the "external address".

Thomas

Thomas Braun schreef op 17-10-2014 9:02:
> Jan Groenestein wrote:
>
>> this info. For instance, what does "external address" mean ?
>
> There are two columns with addresses in netstat:
>
>   Proto  Lokale Adresse         Remoteadresse          Status
>   TCP    127.0.0.1:119          ELWS021:49682          HERGESTELLT
>   TCP    127.0.0.1:119          ELWS021:49683          HERGESTELLT
>
> The first one is the address and port on which the server process is
> listening, the other one is the address and port of the client that is
> connected to the server - in your case this is the "external address".
>
> Thomas
>

Thomas,
Right, quite easy then. Thanks.

Regards,
Jan Groenestein