Please, Urgent: Need ideas/help to solve PR bin/51586

[mark tinguely]

It is interesting that your original problem report bin/51586 has
problem with the same port (623) that is giving problems in this
trace.:

machine1 trace:

14:13:08.046004 vscan1.623 > odie.961: S 3379784543:3379784543(0)
14:13:08.046030 odie.961 > vscan1.623: S 2648818122:2648818122(0) ack 3379784544
(missing tcpdump entry of a SYN from vscan?)
14:13:11.038115 odie.961 > vscan1.623: S 2648818122:2648818122(0) ack 3379784544
14:13:11.044130 vscan1.623 > odie.961: S 3379784543:3379784543(0)
14:13:11.044147 odie.961 > vscan1.623: S 2648818122:2648818122(0) ack 3379784544
14:13:14.244139 vscan1.623 > odie.961: S 3379784543:3379784543(0)
14:13:14.244163 odie.961 > vscan1.623: S 2648818122:2648818122(0) ack 3379784544
and so on
 
machine2 trace:
 
14:13:08.047366 vscan1623 > odie.961: S 3379784543:3379784543(0)
14:13:11.045502 vscan1623 > odie.961: S 3379784543:3379784543(0)
14:13:14.245542 vscan1623 > odie.961: S 3379784543:3379784543(0)
and so on


could there be something in your network that is eatting the port 623
packets? I would suggest crafting a connection from vscan1 port 623
to a port on odie and see if it can connect.

A network analyzer or tcpdump from machine on the networks that
vscan1 and odie are locate upon to see if the traffic made it over
the router/switch/hub that is between these two devices.

--Mark Tinguely.