Our iSeries has autoconfigured many devices in the past. I loaded Client Access to another PC yesterday like I have done many times, but this time it didn't create the device. Auto config is on and the maximum devices value has not been reached. I created the device manually but couldn't get the PC to connect. It is an ethernet connection and the PC can access the network. Any suggestions as to what I can check would be greatly appreciated.
Software/Hardware used:
client access 6.1, dell pc, iSeries 520
ASKED:
December 7, 2010 4:19 PM
UPDATED:
December 9, 2010 11:20 PM
What is the TCP/IP configuration of your iSeries, including IP address, subnet, DNS setting and host.domain name? Is your iSeries host.domain name in your DNS or in your iSeries hosts table? If it’s in your iSeries hosts table and in DNS, do name and address match in both?
What is the TCVP/IP configuration of the PC? Did you install System i Navigator? Did you create an iNav connection to your iSeries? Did you run ‘Verify Connection’?
How did you define the connection for the emulator session? Did you start the session from inside iNav or through PCOMM Session Manager?
Are there any exit programs on the QIBM_QTG_DEVINIT exit point?
Can other PCs configure new session devices via auto-config? If so, can the same user configure new devices through auto-config on other PCs?
That’s enough to start. There are a lot of possibilities that have to be covered from a remote viewpoint.
Tom
Oh, and what System i Access service level did you install on the PC?
Tom
Can the PC ping the AS/400?
Wow! That’s a lot of questions. I want to first say that I can pretty much rule out the config of the iSeries being that there are 50 other PC’s that are working and some were added recently. Originally I installed only PC5250 because that’s all that is needed. I just uninstalled and installed again with Full install option. It still didn’t connect. I am able to ping the iSeries so I know the connection is good. I am also able to get into the IFS. It’s just that when I click on the Connect within Client Access it says “connecting…” for a few seconds but then goes back to “disconnected”. It’s not creating the device description.
Wow! That’s a lot of questions.
Remote (and unconnected) analysis is tricky. A list of questions sometimes is enough to get someone looking at a piece that s/he was blinded to before or to suggest a test that hadn’t been done.
Regardless, thanks for both returning to the thread AND posting the fix!
Tom