Paul McGuire wrote:
> I would investigate Windows security settings as a likely culprit. My
> guess is that you are running WinXP SP2 with the default security
> policies, which are likely to prohibit such promiscuous behavior.
>
> Here's a URL that may shed some light, it seems surprisingly
> i
On Apr 10, 3:30 pm, Irmen de Jong <[EMAIL PROTECTED]> wrote:
> > Hendrik van Rooyen wrote:
> >> I am not sure if this is at all relevant - but I seem to recall seeing
> >> something once that had a list of socket numbers, splitting them
> >> between UDP & TCP - can the socket actually rx UDP?
> Yea
> Hendrik van Rooyen wrote:
>> I am not sure if this is at all relevant - but I seem to recall seeing
>> something once that had a list of socket numbers, splitting them
>> between UDP & TCP - can the socket actually rx UDP?
Yeah, as I wrote: when I'm sending UDP packets to the port directly
on t
Hendrik van Rooyen wrote:
> "Irmen de Jong" <[EMAIL PROTECTED]> wrote:
>
>
>> Gabriel Genellina wrote:
>>
>>> Try running the service impersonating another user (not LOCAL_SERVICE,
>>> the default).
>>> You can change that from the service control panel.
>> Alas, that didn't change anything.
>>
"Irmen de Jong" <[EMAIL PROTECTED]> wrote:
> Gabriel Genellina wrote:
>
> > Try running the service impersonating another user (not LOCAL_SERVICE,
> > the default).
> > You can change that from the service control panel.
>
> Alas, that didn't change anything.
> I made it run as a user account
Gabriel Genellina wrote:
> Ouch, no more ideas from me. You'll surely get more answers from a
> Windows networking group - this appears not to be related to Python anyway.
Yeah I know that... That's what I mentioned in my original post...
But I'm a noob on that type of thing, no idea where to ge
En Mon, 09 Apr 2007 13:08:03 -0300, Irmen de Jong <[EMAIL PROTECTED]>
escribió:
> Gabriel Genellina wrote:
>
>> Try running the service impersonating another user (not LOCAL_SERVICE,
>> the default).
>> You can change that from the service control panel.
>
> Alas, that didn't change anything.
>
Gabriel Genellina wrote:
> Try running the service impersonating another user (not LOCAL_SERVICE,
> the default).
> You can change that from the service control panel.
Alas, that didn't change anything.
I made it run as a user account that has admin privileges even,
and it still doesn't respond
En Mon, 09 Apr 2007 08:43:23 -0300, Irmen de Jong <[EMAIL PROTECTED]>
escribió:
> I have this UDP socket server that binds on ('',9090) and is used
> to be a broadcast responder. It works fine when I start the server
> from the cmd prompt. UDP broadcast packets sent to ('',9090)
> arrive in the
Hello
Sorry this might be a bit offtopic but I don't really know where else
to post this question. If you could point me in the right direction that
is much appreciated.
I'm running into a weird thing on Windows XP.
I'm using Python 2.5 with latest pywin32 from Mark Hammond.
I have this UDP soc
10 matches
Mail list logo
