Re: Client Access Express, Win98SE, Network Neighborhood -- MIDRANGE-L

I was getting similar results when at a customer site, but they had no WINS server. As soon as I moved the NetServer into the same workgroup (and restarted NetServer) as the PCs, it showed up in NN.

A clipping from AS400 Client Access for Windows: Implementing V4R4M0 (SG245191):

The ideal situation is when the AS/400 NetServer and the client PCs are in the
same domain or workgroup and also in the same physical network or TCP/IP
subnet. Since UDP broadcasts can flow freely within a subnet, AS/400 NetServer
automatically shows up in the client's Network Neighborhood.
Unfortunately networks are not always this simple. There are some options. You
may have to use one or more of them depending on your specific network
situation. These options include:

- Using a DNS Server
If you use the Domain Name Service (DNS), make sure you enter both the
AS/400 system name and the AS/400 NetServer server name on the DNS.
IBM recommends that the AS/400 NetServer server name be added as an
alias to the AS/400 system name. However, a different IP address can be used
for each server.
Note: If you want to use both DNS and WINS on a Windows NT client for
computer name to IP address resolution, configure the DNS page of the
TCP/IP properties found in the Windows NT Network properties. Then, enable
DNS for Windows resolutions on the WINS configuration page of the TCP/IP
properties.
Figure 121. Windows NT: Enable DNS Lookup for NetBIOS Names
You do not have to do this for Windows 95 and Windows 98.

- Configuring a Windows NT WINS Server
The Windows Internet Name Service (WINS) is a proprietary Microsoft
service, and has nothing to do with the Internet at all. WINS is used by the
Windows Network Neighborhood browsing service to register and resolve
NetBIOS names (both computer and application names) to IP addresses.
Think of WINS as a specialized DNS for the Windows Network Neighborhood.
To use a WINS Server to resolve an AS/400 NetServer server name, enter the
IP address of one or two WINS Servers in the WINS configuration dialog of the
AS/400 NetServer properties. When AS/400 NetServer is started, it
periodically registers itself with the WINS Servers. If configured for WINS,
AS/400 NetServer also acts as a WINS Proxy server. It forwards broadcasted
name query requests to a remote WINS server for resolution, and then sends
the response to the originator of the name query request.
Enter the IP address of the WINS server or servers in the TCP/IP
configurations settings of Windows 95/98 or Windows NT, if you wish to make
requests directly from a client PC to a WINS server. If a PC client is not
configured to use WINS and the AS/400 NetServer is on the same TCP/IP
subnet as the client PC, it may take advantage of the AS/400 NetServer WINS
Proxy service.

- LMHOSTS File
Add the AS/400 NetServer name and IP address to the LMHOSTS file on each
client PC. The LMHOSTS file is used to resolve a NetBIOS name of a server
to an IP address.
The entry in LMHOSTS should be in the form:
<IP address> <AS/400 NetServer name> #PRE
The #PRE determines that the entry will be preloaded into a cache when the
PC is started. For example:
10.1.1.20 QAS400 #PRE
LMHOSTS is located in the \WINDOWS directory on Windows 95 and Windows
98 PCs, it is located in the \WINNT\system32\drivers\etc directory on Windows
NT PCs.

Tom Hightower
Solutions, Inc
http://www.simas.com
------------
If Bill Gates had a dime for every time a Windows box crashed... oh, wait - he does.

"Roger Vicker, CCP" <rvicker@vicker.com>
Sent by: midrange-l-admin@midrange.com

08/15/01 08:55 AM
Please respond to midrange-l

To: midrange-l@midrange.com
cc:
Subject: Re: Client Access Express, Win98SE, Network Neighborhood

I've tried something similar without success.

First the network layout

AS/400 @ 10.0.0.1 mask 255.255.0.0 on an otherwise Novel network
Cisco router @ 10.0.0.254
Frame Relay by Sprint
Cisco router @ 10.2.0.254
Local peer to peer network 10.2.#.# mask 255.255.0.0 but with a WINS
server @ 10.2.1.57
The AS/400 is in its own work group and has the above address in the
WINS tab. Because its network is otherwise Novel there are no PCs in
its workgroup. Also, I can not put it into one of our workgroups or
one of our PCs into its workgroup.

The AS/400 is reachable by CAE and direct shortcut or search by name.
However if you try to turn on the "Folders" pane in explorer or
"Explore" instead of "OPEN" after searching Windows (98 & 2K) gives a
message that the workgroup is not accessible. If there is a simple way
to make the AS/400 appear in NN I would prefer it over giving all the
users a shortcut.

Thanks

Roger Vicker, CCP

tomh@simas.com wrote:

>
> I added the address of the WINS Server (at least, the system that
> has WINS Server software on it), restarted the NetServer, and voila!
> It showed up in my Network Neighborhood. Thanks for the help.
>
> Strange thing, though: it would show up in NN before, but briefly
> (like for a few minutes). Wonder what that's all about?
>
> And I had tried adding NetBEUI, but it didn't make any difference so
> I just removed again. I'm back to having TCP/IP as the only network
> protocol.
>
> Tom Hightower
> Solutions, Inc
> http://www.simas.com
> ------------
> If Bill Gates had a dime for every time a Windows box crashed... oh,
> wait - he does.
>
>
> "DeLong, Eric"
<EDeLong@Sallybeauty.com> To:
Sent by: "'midrange-l@midrange.com'"
midrange-l-admin@midrange.com <midrange-l@midrange.com>
cc:
08/10/01 02:45 PM Subject: RE:
Please respond to midrange-l Client Access Express, Win98SE,
Network Neighborhood
>
>
>
> Tom,
> Your best means of configuring this is through Operations Navigator.
> You'll find Netserver configuration in:
>
> Network -> Servers -> TCP/IP -> AS/400 Netserver
>
> Right click and select Properties. From there, you have full access
> to configurable items, such as the WINS server. If your network uses
> WINS, just name it here, and the AS400 will register itself with the
> WINS server.
>
> Now, the part about TCP/IP being the only protocol on the PC sound
> funny to me. I am probably wrong about this, but *I* always though
> that Microsoft required IPX or NetBEUI for network neighborhood. If
> my recollection is not valid, someone please let me know. (I have a
> home network that would be MUCH easier to manage without IPX.)
>
> hth,
>
> Eric DeLong
> Sally Beauty Company
> MIS-Sr. Programmer/Analyst
> 940-898-7863 or ext. 1863
>
>
> -----Original Message-----
> From: tomh@simas.com [mailto:tomh@simas.com]
> Sent: Friday, August 10, 2001 12:48 PM
> To: midrange-l@midrange.com
> Subject: Client Access Express, Win98SE, Network Neighborhood
>
>
> I have CAE V4R5M0, Service Pack 65435, Win98SE, OS/400 V4R5. Client
> for Microsoft Networks is installed on my PC, as is TCP/IP protocol
> (no other protocols are installed). For the life of me, I cannot get
> the AS400 to display in Network Neighborhood. I can ping it by IP
> address and by name. I can map drives to the shared resources. I
> can find the computer using the 'Start->Find->Computer' display.
> I've verified (via CFGTCP) that the 400 is on the same subnet as my
> PC (192.168.30.x, s/n 255.255.255.0), and is in the same workgroup
> (simas).
>
> I have read the books relating to Client Access and Netserver.
> Here's a passage from one of them:
>
> 2. Verify the AS/400 NetServer name and domain.
> The AS/400 NetServer server name is a Netbios name that the system
> administrator assigns to the AS/400 system. Once you have a AS/400
> NetServer server name assigned, it will appear on the PC through
> Microsoft Explorer. Make sure that the AS/400 NetServer server name
> is
> unique on the network and that the AS/400 NetServer is in the same
> domain (workgroup) as the majority of the clients that want access
> to the
> AS/400 file and print services. You must have *IOSYSCFG authority to
>
> change any part of the AS/400 NetServer configuration. To change the
>
> AS/400 NetServer default server and domain name, type the following
> at
> the AS/400 command prompt:
> CALL QZLSCHSN PARM(server-name domain-name 'text description or
> comment' X'00000000')
> Once the name has been changed, it should be added to the Domain
> Name Service or Windows Internet Name Service (WINS) if you use
> either
> of these. Refer to the Microsoft Windows NT Server Administration
> Guide
> for details.
>
> Since I can ping the AS400 by name (QIDOCKET), I assume that the
> previous administrator did the 'CALL...' line. However, I can't be
> sure that he added the system name to the DNS, or to the WINS. I
> don't have a WinNT Server Admin Guide.
>
> My questions are:
> What is the default server and domain name?
> How do I verify the AS/400 NetServer name and domain?
> How do I add the name to DNS on Windows NT?
> How do I add the name to WINS on Windows NT?
>
>
> Tom Hightower
> Solutions, Inc
> http://www.simas.com
> ------------
> If Bill Gates had a dime for every time a Windows box crashed... oh,
> wait - he does.
>

--
*** Vicker Programming and Service *** Have bits will byte ***
www.vicker.com ***
A mule dressed in a tuxedo is still a mule.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com