Configuring and connecting your PC client

If iSeries NetServer and your Windows client are in the same workgroup (domain) and in the same subnet (network segment), then no additional setup on the client is needed. If you find iSeries NetServer only by the IP address, then no additional setup is needed.

If iSeries NetServer is not placed in the same workgroup and the same subnet as the PC client, the PC client must use one of the following approaches to locate iSeries NetServer:

• Make an entry for iSeries NetServer in the network Domain Name System (DNS) database. Using DNS is the easiest way to locate and connect to iSeries NetServer.

• iSeries NetServer is configured to register with Windows Internet Naming Service (WINS).

• Create entries for iSeries NetServer in PC client static configuration files (such as LMHOSTS).

• iSeries NetServer User Datagram Protocol broadcasts
  A system that is placed in the same workgroup (domain) and the same subnet (network segment) as the PC client uses iSeries NetServer User Datagram Protocol (UDP) broadcasts.

• iSeries NetServer and Domain Name System management
  If you are using Domain Name System (DNS) to locate and connect to iSeries NetServer, you need to connect and configure your PC client with DNS first.

• iSeries NetServer and Windows Internet Naming Service management
  If you are using Windows Internet Naming Service (WINS) to locate and connect to iSeries NetServer, connect and configure your PC client with WINS first.

• PC client LMHOSTS static configuration files
  In large distributed networks, LMHOSTS static configuration files are helpful for mapping system names to IP addresses.

 

Parent topic:

Getting started with iSeries NetServer