We have an application that uses a client program communicating with a
server program via TCP/IP.

They are experiencing Connections that take between 17 and 20 seconds.
Normally this takes less than a second.  this affects ALL the client
stations.

This is an intermittent problem as the system ran flawlessly for about 5
weeks then experienced this behavior on 2/20.  Nothing we knowingly did
solved the problem, but after a couple of days it started working again.

It ran again until this morning when the problem returned.

We have tried re-starting the program but the problem remained.  we have
replaced a switch and cable to no avail.  Next we will be pulling the
network card from the Server machine.

Any ideas?

TIA

Clyde









--
Clyde Annach
Senior Programmer Analyst
Professional Teledata, Inc.
Manchester, NH 03101
email  clyde@proteledata.com

This turned out to be a routing issue, not a software issue.

Using a program called "tracert". This will tell you how many hops it takes
to get from one machine to the specified machine. When we sent it to a
NETBIOS name it took 1 hop, when we specified an IP address it took over 30.

We used a file called "hosts." in which you map an IP address to a NETBOIS
name.  192.168.0.122 switch01 as an example.

 Its been speculated that resetting their hubs would probably reset the
routing table, but we felt the hosts file would be a more permanent
solution.

Thought I'd share,

Clyde






"Clyde Annach" <clyde@proteledata.com> wrote in message
news:3c7ff31f$1@asgcom.alaska-software.com...
> We have an application that uses a client program communicating with a
> server program via TCP/IP.
>
> They are experiencing Connections that take between 17 and 20 seconds.
> Normally this takes less than a second.  this affects ALL the client
> stations.
>
> This is an intermittent problem as the system ran flawlessly for about 5
> weeks then experienced this behavior on 2/20.  Nothing we knowingly did
> solved the problem, but after a couple of days it started working again.
>
> It ran again until this morning when the problem returned.
>
> We have tried re-starting the program but the problem remained.  we have
> replaced a switch and cable to no avail.  Next we will be pulling the
> network card from the Server machine.
>
> Any ideas?
>
> TIA
>
> Clyde
>
>
>
>
>
>
>
>
>
> --
> Clyde Annach
> Senior Programmer Analyst
> Professional Teledata, Inc.
> Manchester, NH 03101
> email  clyde@proteledata.com
>
>
>

clyde@proteledata.com (Clyde Annach) wrote in
<3c8cb5df@asgcom.alaska-software.com>: 

>This turned out to be a routing issue, not a software issue.
>
>Using a program called "tracert". This will tell you how many hops it
>takes to get from one machine to the specified machine. When we sent it
>to a NETBIOS name it took 1 hop, when we specified an IP address it took
>over 30. 
>
>We used a file called "hosts." in which you map an IP address to a
>NETBOIS name.  192.168.0.122 switch01 as an example.
>
> Its been speculated that resetting their hubs would probably reset the
>routing table, but we felt the hosts file would be a more permanent
>solution.
>

Thank you Clyde for sharing your findings, not many people bother to post 
the solution once they have solved it. I'm sure this will be useful to 
others.

Best regards,
Boris Borzic

http://www.SQLExpress.net
industrial strength C/S development tool