This is a Windows and NetServer setup issue. Has nothing to do with
Client Access. When you set up NetServer on the iSeries you specify a
"Workgroup" as well as a "Full Computer Name". (This is NetBios setup.)
When you access the IFS as a Windows Network Share, Windows will pass
the user id and password that was used when the user signed on to
windows as credentials for using the share. If that user id and password
are not good for the iSeries, NetServer rejects the signon and issues a
challenge. (Actually the challenge is issued first and then Windows on
the PC answers the challenge with the signon credentials.) This scenario
only works if the PC and NetServer on the iSeries have the same name for
Workgroup. Windows won't pass the credentials if the two machines are in
separate Workgroups thereby forcing the challenge and prompting the
user. This is further complicated by Domains instead of Workgroups.
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of tim
Sent: Wednesday, June 11, 2008 6:14 AM
To: 'Midrange Systems Technical Discussion'
Subject: trying to access iseries using windows start/run mistery
We have serveral pc's in the shop. When tring to access the iseries IFS
i do the following in windows xp pro:
Start/run \\184.108.40.206 <file:///\\220.127.116.11>
On some pc's it brings up the list of folders on the iseries. On other
pc's I get a "connecting to" logon screen requiring userid and password.
After entering a valid iseries userid and password, it just returns the
same logon screen again.
I tried this process on server pc's with the same network and iseries
Some pc's work fine. Other don't work at all.
Client access though works on all pc's without any issues, so I know all
pc's can telnet to the iseries. FTP on the other hand is also hit and
Any suggests on this mistery would be appreciated.
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l