× 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.



midrange-l-request@xxxxxxxxxxxx wrote:

>  12. RE: New drive mapping question (Joe Pluta)
>
>> From: Steve Landess
>>
>> 1)You need to have Netserver running.
>> 2) The AS/400 or iSeries must be a member of the same Windows domain,
>
>This is the part I don't get.  What the heck is a Windows domain and how do
>you create one?  Do you have to have a box running a special (server)
>version of Windows to be the domain server?  Or can a W2K workstation be a
>domain server?  Can a Linux box be a domain server?  Can an AS/400 (with no
>integrated PC card) be a domain server?
>
>I'm soooo confused.

Joe, you can ignore this piece I'm going to add because it probably won't 
affect you in your network but it's a "nit" that's begging to be picked. This 
whole area is a part that almost NObody outside of _competent_ certified 
Windows networking pros gets.

The iSeries system doesn't need to be a member of the same Windows domain in 
order to access a share. As long as the domain that the iSeries belongs to and 
the domain the share is in have the proper trust relationship, and the route 
between them allows the right kinds of traffic, and you are on V5R1 or later 
and you have the right PTFs, and your iSeries 'domain search order' is properly 
set, and all the profile/password issues are resolved, and possibly other 
requirements are also correctly met, the domains don't have to match. I'm not 
sure but I don't think you even need a matching profile/password in the other 
domain if the trust is correct.

In order to set the route, you must explicitly create the link under /QNTC; it 
will not be shown automatically and the link will not survive IPLs. Use the 
MKDIR or MD command and specify the IP address of the remote Windows system 
rather than the computer name. (Proper PTFs are extremely critical.)

If all is more or less perfect on every system that participates in everything 
needed for this to work, it'll work. If it doesn't work, make sure _everybody_ 
with responsibility for Windows networking and authentication is available at 
the same time -- in a significantly sized network, that alone can be impossible.

For anybody who doesn't "get" Windows networking -- don't feel bad. A big bunch 
of the experts there don't seem to "get" it either.

Oh, wait... It's Win2K Servers? Active directory? Um.... sigh. Go find the 
experts again.

Tom Liotta

-- 
Tom Liotta
The PowerTech Group, Inc.
19426 68th Avenue South
Kent, WA 98032
Phone  253-872-7788 x313
Fax    253-872-7904
http://www.powertechgroup.com


__________________________________________________________________
McAfee VirusScan Online from the Netscape Network.
Comprehensive protection for your entire computer. Get your free trial today!
http://channels.netscape.com/ns/computing/mcafee/index.jsp?promo=393397

Get AOL Instant Messenger 5.1 free of charge.  Download Now!
http://aim.aol.com/aimnew/Aim/register.adp?promo=380455

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.