Can you try this from the client:
[1] cd /PATH/TO/HOBBIT/client/tmp
[2] cat msg.hostname.txt | bb --debug [IP_OF_SERVER] "@"
You will be seeing messages from it. Post the output message so we can help you out (if this works, it is probably a misconfigured client).
On Tue, Nov 4, 2008 at 9:15 AM, Brian Catlin <bcatlin at gmail.com> wrote:
I have similar issues on SuSE SLES 10 servers and vms. The processes are, no firewalls. This is a security server set, so a lot of services are turned off . I cant telnet on port 1984 just fine, coming back - there is no telnetd enabled... My question is = what, if any network services are required from the server to have hobbit communications work. I have had absolutely no difficulty with my sun servers, even coming through the firewall from the DMZ.
Anyone have this info please?
Thanks
lurch at inorbit.com -------Original Message-------
From: Everett, Vernon Date: 11/3/2008 10:17:35 AM To: hobbit at hswn.dk Subject: RE: [hobbit] Solaris clients don't report
Being able to run the BigBrother client has only negated the need to check step 7. Please continue, and perform check 5. and 6. As you have stated, you are running an RC version. It is possible you have stumbled upon a bug of some sort, unique to your build.
Use snoop to check the client is sending, and again on the server to ensure it is receiving.
Regards Vernon
From: Hanrahan, Kevin [mailto:Kevin.Hanrahan at elavon.com] Sent: Monday, 3 November 2008 10:19 AM To: 'hobbit at hswn.dk' Subject: RE: [hobbit] Solaris clients don't report <truncated thread due to length>