On 19 Nov 2008, at 15:59, Kyle Sluder wrote:
On Wed, Nov 19, 2008 at 12:08 AM, Gerriet M. Denkmann
<[EMAIL PROTECTED]> wrote:
In an other programm (doing Distributed Objects between computers)
I found
out that
int y = bind( newSocket, (struct sockaddr *)&serverAddress,
sizeof(serverAd
On Wed, Nov 19, 2008 at 12:08 AM, Gerriet M. Denkmann
<[EMAIL PROTECTED]> wrote:
> In an other programm (doing Distributed Objects between computers) I found
> out that
>int y = bind( newSocket, (struct sockaddr *)&serverAddress,
> sizeof(serverAddress) );
> wants to have the data in "truc
On 19 Nov 2008, at 01:00, "Michael Ash" <[EMAIL PROTECTED]> wrote:
On Tue, Nov 18, 2008 at 4:49 AM, Gerriet M. Denkmann
<[EMAIL PROTECTED]> wrote:
On 18 Nov 2008, at 15:27, Stefan Werner wrote:
Aren't port numbers 0-1023 privileged under Unix and therefore
only to
applications running as
On Tue, Nov 18, 2008 at 4:49 AM, Gerriet M. Denkmann
<[EMAIL PROTECTED]> wrote:
>
> On 18 Nov 2008, at 15:27, Stefan Werner wrote:
>
>> Aren't port numbers 0-1023 privileged under Unix and therefore only to
>> applications running as root? If you're running your application as a
>> regular user, it
Stabbing in the dark here...
Has the "some message" format now changed with Leopard? Any unused
fields that must now be zero? Any subtle changes to the protocol?
More things to try:
You can file a bug report with Apple.
As a last resort - buy an apple DTS incident. $200 and you have
Appl
On 18 Nov 2008, at 15:27, Stefan Werner wrote:
Aren't port numbers 0-1023 privileged under Unix and therefore only
to applications running as root? If you're running your application
as a regular user, it can't open a listening socket on port 123. It
should still be perfectly able to send
I seem to recall reading somewhere Apple recommending apps not using
low port numbers to maintain compatibility.
You may want to consider using a different port - unless you are
implementing a ntp.
At least test with a different (high range) port number. If it
works... well, OSX could (fi
On 17 Nov 2008, at 22:41, Derek Chesterfield wrote:
There shouldn't be anything to open.
The Leopard application firewall should automatically allow packets
that are responding to your query.
Could you suggest anything else to try?
Andrew Farmer wrote:
Do you have network time synchroniza
Aren't port numbers 0-1023 privileged under Unix and therefore only to
applications running as root? If you're running your application as a
regular user, it can't open a listening socket on port 123. It should
still be perfectly able to send requests to port 123 on other hosts
and receive
On 17 Nov 08, at 04:40, Gerriet M. Denkmann wrote:
I am trying to move a Cocoa app from Tiger to Leopard.
This program wants to send and receive on port 123 (Network Time
Protocoll) but it never gets no answers on Leopard.
Do you have network time synchronization turned on already (in the
D
There shouldn't be anything to open.
The Leopard application firewall should automatically allow packets
that are responding to your query.
On 17 Nov 2008, at 12:40, Gerriet M. Denkmann wrote:
I am trying to move a Cocoa app from Tiger to Leopard.
This program wants to send and receive on po
I am trying to move a Cocoa app from Tiger to Leopard.
This program wants to send and receive on port 123 (Network Time
Protocoll) but it never gets no answers on Leopard.
On TIger there was a firewall, where I could open port 123 in System
Preferences.
How can I do this in Leopard?
Kind r
12 matches
Mail list logo
