Socket connection timeout...

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Socket connection timeout...

Elod Kironsky
Hi!

I am trying to connect to a server from Squeak 3.8.1#6747. It is the Robocup
Soccer Server that by default opens the UDP port 6000 for connections. So I
run the server and execute the following script in Workspace:

s:=Socket newUDP.
s disconnect.
s connectToHostNamed: 'localhost' port: 6000.

I get an exception telling me: "ConnectionTimedOut: Cannot connect to
127.0.0.1:6000". The strange thing is, that if I run some sample clients for
this server, they can all connect, so the port is surely opened (I checked
it also with a port scanner). If I do not disconnect the port before
connectiong, I get "InvalidSocketStatusException: Socket status must
Unconnected before opening a new connection" exception. I checked my
firewall settings, but neither adding UDP 6000 port to exceptions, nor
disabling my firewall helped. I am running Fedora Core 5 x64 on an AMD
Athlon 64 3200+ processor with 1GB RAM. Do you have any idea what can be the
problem? I tried SocketStream class also but I get the same exception.

Cheers,

Elod

Reply | Threaded
Open this post in threaded view
|

Re: Socket connection timeout...

Klaus D. Witzel
Hi Elod, try

((Socket newUDP)
        setPeer: (NetNameResolver addressForName: 'localhost')
        port: 6000) inspect

At the time of this writing I don't recall why (most likely because  
alternatives didn't work) but, this worked for me in 3.7 and 3.8.

HTH.

/Klaus

On Sun, 26 Nov 2006 21:22:59 +0100, you wrote:

> Hi! I am trying to connect to a server from Squeak 3.8.1#6747. It is the  
> Robocup Soccer Server that by default opens the UDP port 6000 for  
> connections. So I run the server and execute the following script in  
> Workspace: s:=Socket newUDP.
> s disconnect.
> s connectToHostNamed: 'localhost' port: 6000. I get an exception telling  
> me: "ConnectionTimedOut: Cannot connect to 127.0.0.1:6000". The strange  
> thing is, that if I run some sample clients for this server, they can  
> all connect, so the port is surely opened (I checked it also with a port  
> scanner). If I do not disconnect the port before connectiong, I get  
> "InvalidSocketStatusException: Socket status must Unconnected before  
> opening a new connection" exception. I checked my firewall settings, but  
> neither adding UDP 6000 port to exceptions, nor disabling my firewall  
> helped. I am running Fedora Core 5 x64 on an AMD Athlon 64  
> 3200+ processor with 1GB RAM. Do you have any idea what can be the  
> problem? I tried SocketStream class also but I get the same exception.  
> Cheers, Elod
>
>



Reply | Threaded
Open this post in threaded view
|

Re: Socket connection timeout...

Elod Kironsky
Thanks Klaus, this worked for me too.

Elod

> Hi Elod, try
>
> ((Socket newUDP)
> setPeer: (NetNameResolver addressForName: 'localhost')
> port: 6000) inspect
>
> At the time of this writing I don't recall why (most likely because  
> alternatives didn't work) but, this worked for me in 3.7 and 3.8.
>
> HTH.
>
> /Klaus
>
> On Sun, 26 Nov 2006 21:22:59 +0100, you wrote:
>
>> Hi! I am trying to connect to a server from Squeak 3.8.1#6747. It is the  
>> Robocup Soccer Server that by default opens the UDP port 6000 for  
>> connections. So I run the server and execute the following script in  
>> Workspace: s:=Socket newUDP.
>> s disconnect.
>> s connectToHostNamed: 'localhost' port: 6000. I get an exception telling  
>> me: "ConnectionTimedOut: Cannot connect to 127.0.0.1:6000". The strange  
>> thing is, that if I run some sample clients for this server, they can  
>> all connect, so the port is surely opened (I checked it also with a port  
>> scanner). If I do not disconnect the port before connectiong, I get  
>> "InvalidSocketStatusException: Socket status must Unconnected before  
>> opening a new connection" exception. I checked my firewall settings, but  
>> neither adding UDP 6000 port to exceptions, nor disabling my firewall  
>> helped. I am running Fedora Core 5 x64 on an AMD Athlon 64  3200+
>> processor with 1GB RAM. Do you have any idea what can be the  problem? I
>> tried SocketStream class also but I get the same exception.  Cheers, Elod
>>
>>
>  
>
>