Re: Tcp Idle (inactive) Connection goes down

Tech-Archive recommends: Speed Up your PC by fixing your registry

Besides above ...Is there any way I can prove to client that its not
either
side of application causing it.?

I guess, you can do the following. Make a telnet connection between two
computers within one LAN (ideal variant - office computers) and check what
happens during two hours. If it's not dropped, this gives you an idea, that
this - is not an application layer problem.

--
Volodymyr
"Guru" <Guru@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E8D9D4E6-5210-4E5E-AB24-905605499F57@xxxxxxxxxxxxxxxx

Just somehting to add ->
I came across router configurations which controls the tcp connections for
various different reason (such as time-out, drop-mode, FIN-RST timeout)
but I
am still not able to prove it.
http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/srfenl.html
- The link has listed various tcp-intercept commands but not being ardent
networking guy Its really difficult to prove its router plus it sounds
remote
possibility.

Besides above ...Is there any way I can prove to client that its not
either
side of application causing it.?


"Volodymyr Shcherbyna" wrote:

Ooops, I hit the "send" button to fast in my prev. message. Here comes
explanation of my short reply in the first message,

According to TCP protocol, if the connection becomes idle, i.e. no data
is
sent during long time, the devices should not terminate the connection.
Actually, the protocol should allow suspend data flow, and then resume
without any special actions. You problem might be some "higher" level
issue,
maybe the ISP problem.

--
Volodymyr
"Guru" <Guru@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:51D7A442-6A00-4D53-97C8-4F05EDDFDD06@xxxxxxxxxxxxxxxx
My server app is running on Windows 2003 where as clients are on winXP
sp-2

Can you please explaing what do you mean by below line "IIRC, from
TCP/IP
point of view, if you need to have an idle connection all that you
have
to
do ... is nothing. It should not be reseted."



"Volodymyr Shcherbyna" wrote:

IIRC, from TCP/IP point of view, if you need to have an idle
connection
all
that you have to do ... is nothing. It should not be reseted.

What operating systems are you using?

--
Volodymyr
"Guru" <Guru@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:2919CA8B-02B5-4CEF-BC3A-F6EFE6CCF5AB@xxxxxxxxxxxxxxxx
Hi,

I've been experiencing the tcp connection problem from 2 different
customer
sites.

Background->

1)I ve a windows service (tcp-server) which accepts the incoming
connection
on specified port#
and gives the service (using child process)

2)Other business applications across network create connections and
starts
using my service

Now one application is creating socket pool which can remain "idle"
for
2+
Hrs or overnight so when
this client tries to submits any request using its pool after this
time
window or so it complins
"ECONNRESET" by peer error.

What I Did->
I started telent session from another machine to my server process
and
I
found that after ~2+ hrs I got
the message "connection to the host lost..." but when I looked at
my
server
side and executed the
netstat -a command it tells me that connection is still
"ESTABLISHED"
state..its strange..

We are not using SO_KEEPALIVE option..

so is there any specific configurations that I am not aware from
"network"
point of view?
I read about routers do have tcp-connection timeout in [sec] for
idle
connections but Im not sure about it.

Can somebody suggest me any specific direction to look for...

thanks
g








.

Quantcast