Strange 15 second timeouts occur on XP clients

Hello,

i have a nice one here, we have a .NET web application running on a Win2003 Server , IIS and SQL 2000 are both running on the same server since this is only the test server for this application. The server is member of the AD Domain TEST.
the authentication method used on the website is Integrated Windows authentication.

the test users test this application from their own XP clients which are member of the PRODUCTION domain , they are asked for a user name and password and then successfully access the application.
now everything seems to work fine and fast but after 45 seconds the application "hangs"for 15 seconds than it respond again but just for 45 seconds than it freezes again for 15 seconds , this cycles goes on all day even during the after hours when no one is using the system.

this however only occurs when users access the application from the XP workstations in the PRODUCTION Domain when i access the application from my laptop ( no domain member ) or from the Development domain there are no problems at all.

I have installed ethereal on one of the XP clients and found out that during the 15 seconds that the application seems to hang there is no network activity between the web server and the XP client at all .
the server responds within 0,5 seconds to every client request request and than it seems that the user did not made any request during these 15 seconds ( i can tell you that i was clicking like a madman to produce some traffic ) all these requests are however sent after this 15 second period...


i suspect that maybe a Domain policy is bothering my users here but so far found nothing, ... any suggestions ???

Kind regards Maarten Takens

How is the authentication set in the database?

How is it set for the .Net application?

Does the .Net app run fine on a workstation or other server?

Zath

As a guess, sometimes incorrect DNS settings can cause these types of delays.

Zath, Sorry for the late reply but the authentication in th .NET application is set as Integrates Windows authentication .

when the user starts the application it first checks if the username also exists in the agents table then the application is started ..

there is a Service account ( Domain account ) wich connects to the database to handle all requests this account has the system administrator role assigned in the database .