Client Access V3R1M2 and AnyNet

In message <3404D081.277A@earthlink.net>, From "Rushdi A. Ariss" 
<rasmu1@earthlink.net>, the following was written:
> We've been setting up users using the AnyNet protocol to connect to 
> the AS/400 with Client Access.  Some machines get disconnected from 
> the AS/400 for no apparent reason, and others work fine.  Any ideas?  
> We are currently on patch SF40828 for CA.
> 
> Thanks in Advance!

No sure fire fix for you, but I've been working on rolling out CA95 +
AnyNet also, and a couple of common causes of problems that I have found
are: invalid or missing local HOSTS file entries on the PC: should
contain

111.111.111.111 ourname.com
111.111.111.111 SNANAME
111.111.111.222 DEVNAME.APPC.SNA.IBM.COM
111.111.111.222 DEVNAME

where the first two define the AS/400, the second two the PC

and nic IO port address conflicts. For some reason, conflicts don't
always show up in device manager. Simply relocating the nic port has
cured a couple of strange problems that only seemd to manifest
themselves when CA95 was involved. I haven't a clue why.

hth
Pete


--
 - Pete Hall peteh@earth.inwave.com
http://www.inwave.com/~peteh/

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---