On Thu, Dec 2, 2010 at 8:38 PM, <[email protected]> wrote: >> I was looking to see if anything was trying to connect to it. You could >> run on the server: >> >> tcpdump -ni eth0 port 1514 >> >> To see if you see the other systems trying to talk to the server. > > Okay, well, eth0 doesn't exist, but eth2 does. Nothing happened until I > restarted the windows agent, then I got this: > > [r...@ackbar logs]# tcpdump -ni eth2 port 1514 > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes > 20:33:55.826751 IP 10.21.4.112.53355 > 10.21.4.24.fujitsu-dtcns: UDP, length > 73 > 20:34:01.861538 IP 10.21.4.112.53355 > 10.21.4.24.fujitsu-dtcns: UDP, length > 73 > 20:34:05.870624 IP 10.21.4.112.53355 > 10.21.4.24.fujitsu-dtcns: UDP, length > 73 > 20:34:10.880076 IP 10.21.4.112.53355 > 10.21.4.24.fujitsu-dtcns: UDP, length > 73 > 20:34:16.885011 IP 10.21.4.112.53355 > 10.21.4.24.fujitsu-dtcns: UDP, length > 73 > 20:34:23.905515 IP 10.21.4.112.53356 > 10.21.4.24.fujitsu-dtcns: UDP, length > 73 > ^C > 16 packets captured > 24 packets received by filter > 0 packets dropped by kernel > >
Watch the manager's logs while restarting the agent's process. It might provide a clue. Also make sure the manager's processes were restarted after the client was added, and make sure the client was configured on the manager with a unique IP address.
