Connection Timeout Expired

SUGGESTED

We are having an issue resulting in the following Fatal Error message.

Connection Timeout Expired.  The timeout period elapsed while attempting to consume the pre-login handshake acknowlegement.  This could be because the pre-login handshake failed or the server was unable to respond back in time.....

Not sure the cause but we have a new server, Cat6 wiring, extended the timeout setting from 15 seconds to 30 seconds and made adjustments to the firewall.

Any suggestions that I can pass on to our IT Company, would be appreciated.

Parents Reply Children
  • 0 in reply to Denise Johnson

    Denise,

    To answer your questions:

    Can you generally connect to the server and complete tasks within the program? And does this error comes up intermittently? Yes, for the most part we can connect to the server and complete task within the program.  Yes, since going live at the end of the year, we have had about 10 instances.  However, the error will show up on someones workstation and they will close out  log back in and not see the error again that day.

    Is this a standard LAN type network-one server in the same physical location as all the workstations that connect to it? If not--if the server is a VM or hosted at a different site than the workstations, then that's where you should start to look.  We are using a virtual machine however the machine is on site at the same location as the workstations.

    Does the error occur on only a single workstation, or do all users experience the problem? I will happen to a single workstation and also found it would happen to 2 workstations at the same time.  I don't think that it has happened to a all users.  Also I worked in the system for about 2-3 weeks before I experienced the error.

    Does the error occur only when the server or network is under a load?
            * Does it work fine in the morning where maybe only a few users are logged in? I have seen it with multiple users and with only a few users logged in.

            *Does the error occur when someone is doing something unusual that requires a lot of server/network resources? From what I have seen no.  I have had instances where someone was just logged in and not in a menu and where someone was entering an invoice and while in takeoffs.

    We have increase our timeout to 60 seconds and since then only one time-out (to my knowledge) has occurred so far.

     

  • 0 in reply to Ray Chippeaux

    I too have this exact issue, and tried all of the above methods as well as a couple others with no fix. Someone has to know something.