RE: QNTC question

Thanks, I will try this 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Hall
Sent: Thursday, May 20, 2004 6:06 PM
To: Midrange Systems Technical Discussion
Subject: Re: QNTC question 

At 16:42 5/20/2004, Richard Allen wrote:

>I created a share the File Server and granted TESTUSR permissions to it
>Now I can execute WRKLNK /QNTC and I see SERVER1 but it does not show any
of
>the files or shares in it
>We created a local user TESTUSR on SERVER1 and then we could send the file
>to the folder on the root but not the network shares on the sub folders.
>
>Perhaps I still don't have the iSeries on the windows domain?  That is what
>our network admin believes?

Do a Go cfgtcp and take option 12. If the domain name is not the same as 
the domain that the share is in, add both the original domain and the 
share's domain to the domain search list as a space delimited list like 
this 'domain1 domain2 domain3'. That will make all of the hosts in the 
domain search list fair game. You don't need to IPL to make this change 
effective. Next do a QSH and in the unix command shell, type cd /qntc. Then 
type ls and go to lunch. If your host name doesn't show up there by the 
time the $ prompt comes back, type mkdir yourhostname. Then type cd 
yourhostname/yoursharename. Type ls and go to lunch again. Eventually, you 
should see a list of objects in the share. If this is successful, go to 
lunch one more time, and this time, have a couple of beers. You're done. 
BTW, the performance of ls is horrible, but using the C APIs to access 
specific files in NT shares from native programs works well.

Pete Hall
pbhall@xxxxxxxxxxxxx
http://www.pbhall.us/

_______________________________________________
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,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.