[GemStone-Smalltalk] Error with netldi, the connection to the repository is never made and the port becomes blocked

[brianstone via GemStone-Smalltalk]

Hi James,

First of all, thanks for helping me.

Ping and telnet (from MW) work with both connections direct and VPN

But if try now to login using Jade, then the the port becomes blocked or
something,  because I cannot connect anymore with Telnet.

I've made another test:

I detected that is not only problem with my MW, because I tested connection
from another pc with windows (connected using wire) and teh same error.

So, I started a session using vpn and one using direct connection, then I
check in the server for current connections to the port using "netstat
-putona | grep 50387".  50387 is the port of netldi.

I receive this result:

WITHOUT CONNECTIONS:

netstat -putona | grep 50387
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 :::50387                    :::*                       
LISTEN      9362/netldid   off (0.00/0/0)

WITH ONE CONNECTION FROM VPN:

 netstat -putona | grep 50387
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 :::50387                    :::*                       
LISTEN      9362/netldid   off (0.00/0/0)
tcp        0      0 ::ffff:133.94.1.30:50387    ::ffff:133.90.150.161:50546
ESTABLISHED 9397/gem            keepalive (6975.87/0/0)

/*Note that a gem process is assigned to the connection*/

WITH ONE CONNECTION FROM VPN AND ONE CONNECTION WITH NETWORK WIRE:

 netstat -putona | grep 50387
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 :::50387                    :::*                       
LISTEN      9362/netldid   off (0.00/0/0)
tcp        0      0 ::ffff:133.94.1.30:50387    ::ffff:133.90.150.161:50546
ESTABLISHED 9397/gem            keepalive (6975.87/0/0)
tcp      112      0 ::ffff:133.94.1.30:50387    ::ffff:133.94.1.11:54096   
ESTABLISHED 9362/netldid  keepalive (7194.97/0/0)

/* Now,instead of a gem process, the netldi process is assigned to the
connection from MW using network wire */

This is really strange. I have asked to network administrators and they said
that there is no firewall in the network and that the problem may be my ML.

But I don't have any rule to reject connections in ML and the port is open
too.

Thanks James.

Ezequiel




--
View this message in context: http://forum.world.st/Error-with-netldi-the-connection-to-the-repository-is-never-made-and-the-port-becomes-blocked-tp4939542p4939622.html
Sent from the Gemstone/S mailing list archive at Nabble.com.