We have developed a time clock service for our phone system that utilizes SQL server procedures.
It works fine on the 7942 phones.  As we need additional phones, we are purchasing the 8941 phones.
The service is not working correctly on the 8941 phones.
On the first two screens that don't go out to SQL are fine. Each subsequent screen gets an HTTP Connection failed error.
If the user goes back one screen then forward again, it works.  It seems like a timeout issue, but I don't know how to correct it.
Any assistance is appreciated.
Thanks, Cindy

David, here are jpg's of two packet captures.  The first (longer one) is a 7942 phone.  The second (short) is the 8941 phone. The only obvious thing I see is that I was able to run the routine (and more) in 15 seconds, vs. 65 seconds. Of course, I'm not sure exactly what I'm looking at.
If you need more information that just the headers, I can attach the actual packet captures. Just let me know.
Here's how the process works.
Click on Services, Time Clock This opens a Clock In/Clock out screen.  User chooses. Asks for user's ID.  Up to this point, no SQL involved.
When user clicks submit after entering their ID, it goes to SQL to check the ID#. If it exists, it returns username. If not, error page directs users to go back one page.
When user ID is correct, page prompts for PIN#.  After hitting submit, it goes to SQL and a)checks to see if ID & PIN are a pair, b)if user is currently in a state of punched in/out.  C) Returns "successful transaction" page if all is well.  If not, error page tells user it wasn't a pair, or they are currently already clocked in/out. 
Thought this might give you a sense of where things may be slowing up.
Thanks for your help!  Cindy

Attachments: