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



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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.