Hi HomerJ,
I have encountered this in the past and an adjustment recommended by Microfocus after testing with the client found that adjusting the timeout settings within the jetty.xml files had a positive result. The following was what was recommend to be changed:

Please try the below steps:

*In ALM Server (ALL YOUR NODES if running multiple servers) Open ''jetty.xml'' file.

This is typically located in the path: ProgramDataHPALMserverconfjetty.xml

*Open the file for editing and search for ''
*If you have a value of 30000. That's measured in ms.

*Increase this to 600000, save, then bounce the ALM service''

This was a suggestion that worked for a client in the past and if the increases after multiple tries yields nor positive results you may look into the network settings with your IT department to see if there is a slow down being caused by something in the network. At least you have the server portion to use as a work around in your instance,

Hope this helps,
Dan

@miraclefren2 Ping will tell the reliability of the signal and how it is reproduceable when run connsecutively. Tracert can reveal a slow or weak hop which could be a router/switch/hub/cabling error that is causing such issue. You could try wireshark for checking packet loss too. They need to look at the overall signal and path and see that it is not just ''working'' but ''working efficiently'' . Just getting there is not always good enough with data, as how much error correcting must happen among other things. they should be able to trouble shoot the network to locate it and if they have mapped it correctly then they should have performance stats and be maintaining these for historical data comparison to find failure in advance.

@miraclefren2 . Wireshark being supported in Linux or not should be a moot point, if you aren't having issues creating projects on the server directly, As that connectivity is working correctly. If you are having issues creating it on the server where it is timing out then you need to find a Linux tool to assist. Otherwise the wireshark can be run on a remote system testing the routing to the server as that is the link we are talking about with the above error. You could elevate the logs to debug level and then watch the commands created and compare the timing and differences between the project creations attempted on the server versus those on the remote system. If you can't create projects on either and it isn't a timeout issue then you need to be looking into permissions on the DB supporting the ALM application. You should probably open a case with your support provider to further trouble shoot this issue.