Re: Operation not permitted, very odd WO behaviour.

2008-06-02 Thread Klaus Berkling
In your log it says: Info: attempting to connect to server b on port 2018 Assuming you typed in 'server b' or 'server a' to substitute the real hosts. Is that the internal network IP address, your public IP address or a host name? Did you try to run the whole setup without a firewall?

Re: Operation not permitted, very odd WO behaviour.

2008-06-02 Thread Aristedes Maniatis
On 03/06/2008, at 9:19 AM, Klaus Berkling wrote: - Run only one JavaMonitor, if you use that. Hi Klaus How do you get away without running JavaMonitor? We'd love to do so, since it is such a buggy piece of software. Are their command line tools to achieve the equivalent? Cheers Ari

Re: Operation not permitted, very odd WO behaviour.

2008-06-02 Thread Klaus Berkling
On Jun 2, 2008, at 5:02 PM, Aristedes Maniatis wrote: How do you get away without running JavaMonitor? We'd love to do so, since it is such a buggy piece of software. Are their command line tools to achieve the equivalent? The source code for JavaMonitor is available and there is an

Re: Operation not permitted, very odd WO behaviour.

2008-06-02 Thread Aristedes Maniatis
On 03/06/2008, at 10:17 AM, Chuck Hill wrote: I am not sure that this is going to work with wotaskd and friends. What does hostname show on this machine? serverb.internal or something else? If something else, that is probably the name you want to be using. Unless it says .local,