× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



> From: Andy Nolen-Parkhouse
>
> Whether a domain or a workgroup, computers in the same named network will
> share information regarding shared drives and printers.  This is the name
> that should be reflected in the NetServer configuration and allows OS/400
> to both see and be seen by other computers on the network.

Okay, that's interesting.  You seem to be implying that as far as the AS/400
is concerned, workgroups and dmoains are the same.  Because I can set up
workgroups in my peer network, as you say, but not a domain, because I don't
have a domain controller.  And I'd rather not have one if possible.

So, if I have a workgroup and I set up my NetSerevr configuration to that
workgroup, then I should see everyone in that workgroup?  (JOE QUICKLY DOES
A WHACK HERE AND A HACK THERE)  Okay, I do see it!

I do a WRKLNK in QNTC, and I can see the workstation (and my AS/400).
However, when I open the workstation, there is nothing in it, even though I
shared a folder.  I power down the workstation, it's still in the QNTC
folder, but any attempt to access it hangs.

I reboot the workstation, and now when I do a WRKLNK and go into the
workstation, I see an empty folder.

So, why can't I access the share that I created?  I gave Everyone permission
to the share, no maximum users.

Joe


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.