[hobbit] Solaris clients don't report

[Ward, Martin]

Hi Brian,
 
In this instance telnet is being used to see if a port is open, it does
not require the telnetd daemon to be running on any server.
 
If you telnet from your Hobbit client to your Hobbit server on port 1984
( $ telnet 10.0.0.1 1984 ) and you get an error like "connection
refused" then the client can probably reach the server but the Hobbit
daemon is not listening on port 1984 on that machine.
 
If you perform that same command and the connection times out after a
few minutes then the packets are usually being dropped at a firewall
somewhere.
 
If, however, you perform that command and you get something like
"Connected to ...
Escape character is '^'.
" then the network is set up fine, the remote Hobbit server is up and
running and your client is able to talk to it, so you need to start
looking at problems with the Hobbit configuration.
 
HTH
 
|\/|artin
 
 -----Original Message-----
From: Brian Catlin [mailto:bcatlin at gmail.com] 
Sent: 04 November 2008 01:16
To: hobbit at hswn.dk
Subject: RE: [hobbit] Solaris clients don't report



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 <mailto:Vernon.Everett at woodside.com.au> 
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>
		



*************************************************************************************
The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. 

The contents of this message and its attachments are confidential and may also be subject to legal privilege.  If you are not the named addressee and/or have received this message in error, please advise us by e-mailing security at colt.net and delete the message and any attachments without retaining any copies. 

Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. 

No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party.  

Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xymon.com/pipermail/xymon/attachments/20081104/0def2584/attachment.html>