Client Access Connection Fails

Hi Pquittem,

Check this answer from berry:
https://www.experts-exchange.com/questions/21744402/Client-Access-Sessions-Losing-Connection-To-AS400.html


Regards,
Murph

Does this just happen to you, or does it happpen to everyone?  You may just have a short disconnect interval configured on your system.  Some shops do this as a security feature, especially if there are terminals or workstations in public areas where leaving them signed on creates a security risk.  

You can check and see if this is the case.  

There are two iSeries global system values that control session time-out behavior for the entire system (or partition):  QINACTITV, and QINACTMSGQ.  Use the DSPSYSVAL command to view these two system values:

DSPSYSVAL QINACTITV
DSPSYSVAL QINACTMSGQ

When a session is inactive for the number of minutes specified in QINACTITV, the system looks at the QINACTMSGQ system value to see what action to take:

*DSCJOB - Disconnects the job.  
*ENDJOB - Ends the job.
You can alternatively specify the name of a message queue to receive a message then the disconnect interval expires.  A programmer can write a program to monitor the message queue and do whatever you want.  This is the only way to discriminate between jobs and take differing actions for different jobs.

There are other things that can cause repeated drops: bad cabling, routing issues, failing switch port, or TCP/IP configuration issues on the workstation or AS/400.  Post back if the Inactivity Timer isn't the problem and we can explore some other alternatives.

- Gary Patterson

Gary, this is happening to 1 user. It started over the weekend. He's had no problems before that. It's not as if the session is stagnant. He's working and the connection is dropped. No error message. After 30 seconds a rerfeshed signon screen appears. We have tried connecting to our LAN via his docking station, directly to his ethernet port and using wireless. Same results. We have found, however, that if he connects from outside our network via VPN the connection is stable.  ?

pquittem.

Interesting.  Points to something that is interfering with the connection on his machine.  

I've seen similar problems when the workstation had a duplicate IP address on the network.  That would explain why it works over the VPN but not locally.

Is he addressed statically or via DHCP?

Look up his IP address (Start -> Run -> Cmd (enter) -> ipconfig /all), then pull his network cable (or disable his wireless adapter) and PING that address from another workstation, preferably on the same subnet.  If you get an answer, you have a problem.  Of course, there is no guarantee that there isn't a duplicate device the just doesn't respond to ICMP requests.  After you PING the address, check your ARP cache to see if ARP found an adapter with that IP address (ARP -A).
 
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/cnet/cnbd_trb_nqgq.mspx?mfr=true

If you don't find a duplicate IP on the network, post back and we can do some nore troubleshooting.

- Gary Patterson

It worked from outside?
SO it's the network, what about an other cable, other place, other outlet, other patchcable?
It sounds like a duplicate definition somewher or a timout.... ever try flush the DNS on that pc?
flushing  DNS from a dos box IPCONFIG /FLUSHDNS.

 

We have tried replacing patch cables, changing ports, wireless. Only through VPN will the session hold. We have tried fluishing DNS. Same results. We have just noticed that we cannot ping that machine from another. The machine in question is connected to the network, has internet access, fully functional (except for the droping sessions) but we cannot ping to it. We can ping from it.

Glad you got it worked out.

- Gary Patterson