Re: TCP RST and why that might happen
From: Michael Fuhr (mfuhr_at_fuhr.org)
Date: 12/03/04
- Previous message: Tauno Voipio: "Re: My goal is a _really slow_ connection"
- In reply to: Tauno Voipio: "Re: TCP RST and why that might happen"
- Next in thread: Pete: "Re: TCP RST and why that might happen"
- Reply: Pete: "Re: TCP RST and why that might happen"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 3 Dec 2004 14:49:23 -0700
Tauno Voipio <tauno.voipio.REMOVE@iki.fi.NOSPAM> writes:
> Pete wrote:
> > Anyone have a clue as to why a connection I create with a server would cause
> > a TCP RST to be sent from the server? Here's the gist.
> >
> > I am working on a Gaim client for exchange messenging. Currently, I can send
> > a message to the server, but all I get back is the TCP RST on port 80. I at
> > first assumed it was a bad message, but if I send an identical message to
> > one the actual MS client sends (retrieved using ethereal), I get the same
> > behavior. I assume then it's a problem with my setup. Not sure what though.
> > Anyone have a suggestion?
>
> Sounds like a firewall reject.
Maybe, but there's not enough information to say for sure. He says
he can send a message but all he gets back is RST -- does that mean
that the original three-way handshake was successful and it's later
that he gets the RST? Or does it mean that he sent SYN but got RST
in response? Seeing tcpdump or tethereal output from the good and
bad connections might shed some light on what's happening.
-- Michael Fuhr http://www.fuhr.org/~mfuhr/
- Previous message: Tauno Voipio: "Re: My goal is a _really slow_ connection"
- In reply to: Tauno Voipio: "Re: TCP RST and why that might happen"
- Next in thread: Pete: "Re: TCP RST and why that might happen"
- Reply: Pete: "Re: TCP RST and why that might happen"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|