Re: flying pig?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Al Reid (areidjr_at_reidDASHhome.com)
Date: 09/16/04 

Date: Thu, 16 Sep 2004 07:19:12 -0400

"Larry Serflaten" <serflaten@usinternet.com> wrote in message news:Od0m$C8mEHA.3900@TK2MSFTNGP10.phx.gbl...
>
> "Al Reid" <areidjr@reidDASHhome.com> wrote
>
> >
> > You need to look at the posting host in the header of Miss O'Dors post to
> > see the public IP address, then trace that one. I came up with the same one
> > (prov.co.uk) as Peter.
>
> From OE File > Properties (header section), I see:
>
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>
> Using NetworkSolutions whois,
> http://www.networksolutions.com/en_US/whois/index.jhtml
>
> Typing in the IP part and selecting the IP option, I get the same results as Stefan.
>
> Can you be more explicit, with a step by step explaination?
>
> Thanks
> LFS
>
>

Larry,

I am using OE as well. I was trying not to post his IP, however. It is in the line that starts with "X-WBNR-Posting-Host: 193...."
and in my display it is the third line in the properties dialog.

That resolves to prov.co.uk.

As an aside, I see that Ben/Bonj has posted an apology and is going to reappear as Bonj and be a model NG citizen.

Later 

-- 
Al Reid
How will I know when I get there...
If I don't know where I'm going?

Relevant Pages

  • Re: flying pig?
    ... > You need to look at the posting host in the header of Miss O'Dors post to ... > see the public IP address, then trace that one. ... with a step by step explaination? ...
    (microsoft.public.vb.general.discussion)
  • [RFC] Common Trace Format Proposal for Linux (v1)
    ... The goal of the present document is to propose a trace format that suits the ... Packet: A sequence of physically contiguous events within a section. ... A metadata section contains information on trace event types. ... Per-section event header description. ...
    (Linux-Kernel)
  • [RFC tracing] Common Trace Format for Linux (v1.1)
    ... In order to get things rolling, I hereby append my trace format proposal as RFC. ... Packet: A sequence of physically contiguous events within a section. ... A metadata section contains information on trace event types. ... Per-section event header description. ...
    (Linux-Kernel)
  • Re: [PATCH 0/11] LTTng-core (basic tracing infrastructure) 0.5.108
    ... If we remove ASCII> event tracing from LKET, we could remove CPU id from the event header as> well. ... The original idea for keeping ASCII trace was that a user may have wanted to look at trace output information in real-time as it was being printed onto the screen. ... Since the user is> free to chose which tracepoints he wants to use for his workload, we can> not guarantee that scheduler tracepoints are going to be available. ...
    (Linux-Kernel)
  • [PATCH 2/11] LTTng-core 0.5.111 : Relay+DebugFS
    ... +struct ltt_channel_struct { ... a dynamic per trace alignment value must be set. ... so the buffer header and trace header are aligned. ... * The event header must be a size multiple of the void* size. ...
    (Linux-Kernel)