Re: Http server implementation for Windows Media Server

Where do you do(modify) it ?
Arkady

"Ronny" <ronny@xxxxxxxxxxx> wrote in message
news:uR9ltw%231HHA.5772@xxxxxxxxxxxxxxxxxxxxxxx
Thanks,
I think I understand a bit more following your direction...
Now to a real case that I encounter, as described in the first post of
this
thread, modifying in the tcp packet before transmitting, just the port of
the client as the port is usually different than the original one, causes
a
real time sniffer to indicate a huge "relative sequence number". Leaving
it
without modification causes an indication of 1 - just as it was in the
original packet. Why should the port value influence on that?
Can you explain that?

Regards

Gur
"Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx> wrote in message
news:OSB8$$y1HHA.5884@xxxxxxxxxxxxxxxxxxxxxxx
On the tcp layer, both server's and client's tcpip stack do that
Arkady
"Gur" <gur@xxxxxxxxx> wrote in message
news:eGqSoat1HHA.484@xxxxxxxxxxxxxxxxxxxxxxx
Thanks,
Suppose a common scenario where a standard Web Server responds to a GET
Http request. Does the server ever ACKs the client and when?

Thanks

Gur
"Arkady Frenkel" <arkadyf@xxxxxxxxxxxxxxxx> wrote in message
news:uystfhs1HHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
That strange that no ACK appear because any data should be ACKed
Arkady

"Gur" <gur@xxxxxxxxx> wrote in message
news:ukd9yIq1HHA.1336@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

I'm trying to implement a specific Http server that listens on port
8080
(not the standard 80). Actually it resembles a Windows Media Server
that
also works as a HTTP server (among some other modes).
I have a dump file of prercorded transmision from an actual Window
Media
Server and Windows Media Player, and my server implementation should
transmit them after establishing the tcp connection with the Player.
In reality, the connection is established but the server behaves with
the following anomalies-
1. After the "GET" transaction by the Player, the server transmits an
ACK which doen't appear in the normal case.
2. The first dump packet that is being transmitted starts with a
huge
"Realtive Sequence Number" instead of a 1.

Can someone advise please?

Regards

Gur











.

Relevant Pages

  • Re: Question on IIS servers and reverse lookup ... found answer
    ... netbios over TCP/IP on the interface your web server uses to talk to the ... There's a huge list of steps to take to secure an IIS ... logs) in addition to the low-level packet capture. ... packet is being sent to that UDP:137 port. ...
    (Focus-Microsoft)
  • Re: Regarding dhcp client problem
    ... I have captured the packet information from the device. ... win2k dhcp server sends ... But the dhcp client in the device is not receiving the offer at ... User Datagram Protocol, Src Port: bootpc, Dst Port: bootps ...
    (comp.arch.embedded)
  • Re: Http server implementation for Windows Media Server
    ... Now to a real case that I encounter, as described in the first post of this ... thread, modifying in the tcp packet before transmitting, just the port of ... the client as the port is usually different than the original one, ... Suppose a common scenario where a standard Web Server responds to a GET ...
    (microsoft.public.win32.programmer.networks)
  • Re: TCP/IP Ports
    ... > The TCP packet sent from the client to set up the connection contains ... > destination port for which an application is listening on the server ... The client OS will assign a different source port to identify the ...
    (comp.os.linux.networking)
  • Re: Question on IIS servers and reverse lookup
    ... In addition to that I would say setup listening devices in addition to the low-level packet capture. ... They ought to give you more hints about what the system activity is as the packet is being sent to that UDP:137 port. ... Question on IIS servers and reverse lookup ... Maybe these are authentication attempts against your IIS Server coming from ...
    (Focus-Microsoft)
Loading