|
Ken, Are you saying that you have specifically identified your PC in your host file on the AS/400? If you have, why? I have used a number of versions of client access, including V3R2, in a client DHCP environment, and never encountered an error such as you describe. I assume that you are using a straight TCP/IP connection. Are you assigning workstation names at the client (i.e. DEV01PC)? Are you allowing virtual devices to autoconfigure? Regards, Andy Nolen-Parkhouse > On Behalf Of Shields, Ken > Subject: TCP addressing scheme and CA > > Good morning > I'm using CA V3R2 on my pc to connect to the 400 at V4R3. > The W2000 sever adopted DHCP(dynamic addressing scheme), but I have > asked the > network chap to assign a static ip address to the /400 resource. > Problem: > Using my CA, the ip address of my pc is say xxx.xxx.xxx.10, and the > /400 cfgtcp > identifies the pc. > The next day DHCP changes the ip address of my pc to xxx.xxx.xxx.11, > and voila! > I can no longer connect. > I'm just wondering if there is a solution at my level, or will I > have to upgrade my CA to > CA Express to handle this problem? > Thanks. > > Ken Shields
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.