Network error: socket is already connected

[Rick Garland]

Identify what is on the socket that is causing your connection errors. This can be achieved using 'lsof' which can be downloaded from the HP porting center.
http://gatekeep.cs.utah.edu

The lsof app is in depot form as well as source code. Use of the application will help you identify what has the socket.

[Craig Gilmore]

You didn't mention where this error is presented. Is it in the system log file, on the console or on a users screen?

I will presume the console log.

"Socket already connected" means that an error code of EISCONN was returned to the program issuing a connect(2) call. The question needs to be: What program issued the connect(), and Why? When you have at least the first half of the question answered, then you might be able to answer the second half.

If this is a message in the system log file, then it should state what program/process generated the error. Is this vmunix or some other process?

True, lsof can help in identifying what sockets are in use by what process, but you need to first identify what process is generating the error. If you have Glance or PerfView/MeasureWear, or any good performance tool, this task is made easier.

Once you have the process identified, then you can determine if it is HP-UX or NSProxy.