|
Mark, Many thanks - Netserver was started as we use the IFS a lot through it, but the DOMAIN in the netserver configuration was set to the AS/400 serial number. Once that was changed, and Netserver re-started, QNTC is now showing all of my shares and allowing navigation. Now to see if I can use the 400 8mm tape drive to back up the servers.... Cheers Robin -----Original Message----- From: Mark Phippard [mailto:MarkP@softlanding.com] Sent: 01 June 2001 13:22 To: MIDRANGE-L@midrange.com Subject: RE: QNTC Robin, You need to configure and start NetServer. This is the feature of OS/400 that allows you to access the IFS via Network Neighborhood. Once this is setup properly, then the /QNTC stuff will just automatically work. Check out this link. http://www-1.ibm.com/servers/eserver/iseries/netserver/ You configure it using OpsNav. Hope this helps, Mark Phippard Robin Coles <robin@ringbase.com To: "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com> > cc: Sent by: Subject: RE: QNTC owner-midrange-l@mi drange.com 06/01/01 06:22 AM Please respond to MIDRANGE-L Are there instructions for setting this up anywhere? I can see QNTC in wrklnk but taking a 5 against is doesn't show anything. My AS/400 profile is set up identically on NT with administrator privileges and there are numerous shares I'd love to be able to access... Cheers Rob -----Original Message----- From: Urbanek, Marty [mailto:Marty_Urbanek@stercomm.com] Sent: 31 May 2001 18:51 To: 'MIDRANGE-L@midrange.com' Subject: Re: QNTC I don't think current QNTC is restricted to and/or dependent on FSIOP/IPCS/INS/IXA/IXS. Even a system without FSIOP can use QNTC to read/write data from/to NT. -Marty ------------------------------ Date: Thu, 31 May 2001 12:42:09 -0400 From: Pete Massiello <pmassiello@os-solutions.com> Subject: Re: QNTC Mark, That is your NT FSIOP (or whatever the current name of the card is) data that is associated with your *NWSD. It always goes in the IFS, although some piece will also go in QUSRSYS as *SVRSTG. Pete +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.