At 20:10 05/13/2003, Tom Liotta wrote:
That is, if you have all the necessary PTFs and NetServer is correctly
configured (and it's a half-moon and it's Tuesday evening and who knows
what all else), then you can add QNTC subdirectories by IP address rather
than by machine name. This support supposedly allows you to cross Windows
domains. The /QNTC/IPaddr subdirectory must be explicitly created and it
will not survive IPL.
Of course, you also must have all Window domain trust relationships and
profiles and authorities (and it must be a full moon and only on Mondays
and...)
I've been experimenting a little with this. It wasn't even necessary to
bounce the IP server. I added the new (second) domain to the domain search
list, had my friendly network admin person create a user account for me in
the second domain (I already have one in the default domain), made all of
the passwords identical, started QSH, performed MKDIR /QNTC/<hostname>
(didn't even specify the domain), and then CD /QNTC/<hostname>/<sharename>
and LS * and after 4 or 5 interminable minutes, received an object list (LS
is always a real groaner in QSH. Maybe the sticky bits are set.) I've never
tried using the IP address though.
Anyway, the key parts of the process seem to be:
The domain must be in the domain search list (CHGTCPDMN).
The user must exist in the same domain as the NT host.
The user's password must be the same on AS400 and the NT domain.
(doesn't seem to be case sensitive, but there's a PTF issue in that regard
on V5R1 if I recall correctly).
I'm using a mix of NT4 and W2K domains.
In my (limited and uneducated) opinion, Netserver doesn't seem to honor
trust relationships between domains.
That's all I think I know.
Pete Hall
pbhall@xxxxxxxxxxxxx
http://www.pbhall.us/
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.