|
I think I heard that NT rumor before also. That might be your problem. Is the server running NT? Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com rick baird <rick.baird@xxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 01/13/2005 03:20 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: QNTC Rob, yes. On Thu, 13 Jan 2005 14:28:00 -0500, rob@xxxxxxxxx <rob@xxxxxxxxx> wrote: > Can you get to it from your PC by using Windows Explorer? > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com > > rick baird <rick.baird@xxxxxxxxx> > Sent by: midrange-l-bounces@xxxxxxxxxxxx > 01/13/2005 02:12 PM > Please respond to > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > > To > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> > cc > > Subject > QNTC > > > Hey all, > > I'm working to get access to windows servers on our network via WRKLNK > 'QNTC', and eventually using the CPY command to copy objects from the > IFS to a directory on that server. > > I'm using a user id and password that exist and are identical on both > the iseries and network. > > this user has been given permissions to said directory which resides > on the D: drive of the server. > > I can wrklnk 'QNTC' and see the server name, but when I place a '5' on > the server, nothing is behind it. > > I'm not doing the NT side of things myself, nor is it my expertise. > But the network guy verified that he can reach that drive and folder > from the windows shares utility (whatever that is) signed on as my > user and password. > > we're on os/400 V5R3, in a mixed windows and netware network - the box > in question is running windows NT 4.0 - no novell. > > Any guidance you can provide would be great. > > Thanks, > > Rick > -- > 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. > > -- > 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. > > -- 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.
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.