Oh, I've done all of that, Pat. I've never had an issue/problem/concern at
other places at which I worked, which is why I "think" it has to do with how
the "network" is set up here. I'm not a network guy, though, but I've had a
couple of other (outside) people look at it, and they just scratch their
heads. As, I think, I have said before, if I have to print PC stuff
(spreadsheets, for example) on a printer around the corner but cannot print
to one sitting in my office, that tells me the network is hokey (sorry to
get technical).
But I thought there might be an optional feature of the OS (V5R1) that isn't
installed. I'm going to be adding the QSYSINC (Openness Includes) on
Monday, anyway, so thought it would be a good time to add anything else that
were missing.
Jerry C. Adams
IBM i Programmer/Analyst
"I didn't attend the funeral, but I sent a letter saying I approved of it."
-Mark Twain
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pat Barber
Sent: Friday, May 27, 2011 8:46 AM
To: Midrange Systems Technical Discussion
Subject: Re: Netserver
You must create a "share" before you can map a drive.
I usually do the share on the root directory.
See the help while in Navigator on how.
On 5/27/2011 8:47 AM, Jerry C. Adams wrote:
Is there an extra (optional) feature of the OS that I need to have
installed
before Netserver will run?
iNav shows that Netserver is started, but I cannot map an IFS folder to
Windows Explorer. Thought I might be missing a feature code, but I really
think it is probably a result of the patchwork "network."
midrange.com
