Sorry for the typo, 'grep /etc/passwd' was what I meant.
I would like you to change the last line of the .profile for the user with the most problems.
Remove the word 'exec' from the last line.
The file should look like:
If you do this, and the disconnect is from the application code, the terminal session will not end, but leave the user with a $ command prompt.
If you have X-Windows running, you can use the editor to change the .profile, otherwise log in as root, and type the following commands:
I wanted to thank everyone that has helped me along the way, especially JGT for your guidance.
I wanted to update the forum with the resolution to the issue.
In the end the disconnect was not a result of the SCO Openserver 6 server but was the McAfee Total Protection on the clients computers.
This was only found after doing wireshark packet captures which showed that there were several retransmit packet errors just before the disconnect.
These re-transmits showed that the communication toward the client computer was not getting through.
After checking the security history of the McAfee firewall there were entries that the McAfee firewall was seeing the telnet session as an unwanted connection even though the client computer had initiated the connection and the firewall allowed it through.
It appears that after a period of inactivity the McAfee Firewall would close the socket.
I have not found a setting in the McAfee to disallow this. The telent client is an allowed program in the McAfee Firewall as well.
In the end I needed to add the server IP address (which is in the same subnet as all of the client computers, no router of any kind in between the client computers and the server) into the Firewall as allowed on all ports. Since adding in this exception there has not been a disconnect to the users.
Again thank you for all of the assistance on this issue.
Hi,
Sorry if this question has been asked before, however, I have tried looking in the forum (and google in general) and I haven't found an answer, so I thought I'd ask here.
I am trying to use a GUI application in Solaris 10. Normally I connect with a VPN then SSH and use Xming to... (2 Replies)
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
I have intermec handheld device which is connecting to AIX Server on port 12431 or whatever. ( oracle application )
The handheld device connects for few seconds and then disconnects from the AIX server. Once it disconnects the handheld device automatically switches off.
Are there any... (2 Replies)
Hello,
I have AIX 5.3 at home connected to netgear router. Port Forwarding has been enabled on the router. Problem is that if I want to telnet, I have to try 2 or 3 times before I can get a logon prompt. It times out for first or second time (Connection to session <IP_Address> failed: Connection... (1 Reply)
We're having problems getting disconnected from AIX with our telnet sessions.
I can't ping the server when this happens, either. Other serves can be pinged at the same time.
This happens both at unix and within the database. Database locks remain when editing files. unix logins remain after... (0 Replies)
{
sleep 2
echo "$user"
sleep 2
echo "$password"
sleep 2
echo " ls"
sleep 10
echo "exit"
}| telnet $server
I have a machine x and i have executed the above script on machine 'x'.
i entered the... (6 Replies)
Dear friends..
Our project has a module that runs on handheld devices. Through the handheld we telnet to solaris where the application actually runs. I noticed that after starting a session through the handheld, if i go out of range or if i remove and replace the battery in the handheld, the... (1 Reply)