There is no way to comment on that without knowing anything about how the
application works. But you can't make Windows overcome a poorly written
Application. If the Application needs to stay continuously connected yet
the developer never built any "keep-alives" into the communication channel
there is nothing you can do about that.
The Application needs to be designed to either reconnect "on-demand" or use
some form of Keep-alives. Having it reconnect "on-demand" would be the
correct and most bandwidth efficient approach.
--
Phillip Windell
www.wandtv.com
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"Jeroen" <(E-Mail Removed)> wrote in message
news:%23$Dh9G$(E-Mail Removed)...
>I have a Win2003 R2 Std. Server that runs an application to track vehicles.
>The information from the vehicles comes from a 3rd pary and connects to the
>server from the internet on a specific port. On Windows XP Pro and Windows
>2000 Workstation/Server there are no problems communicating between the
>application and the 3rd party. However on Windows 2003 the connection gets
>disconnected after exactly 600 seconds of inactivity. The problem isn't
>caused by routers or switches since it also happens on the console to
>localhost/127.0.0.1.
>
> I know keeping the connection open but inactive isn't the best way, but I
> didn't write the application.
>
>
> Jeroen
>
Similar Threads
Linear Mode
