[an error occurred while processing this directive]




Peer LAN containing mixture of eCS and Warp 4.x systems

On eCS systems it is reasonably well documented that you must check/change the following to ensure each station can "see" every other:

  1. In bootdrive:\IBMLAN\IBMLAN.INI make the following changes:

  2. Set "wrkservices=" to "wrkservices = PEER,MESSENGER" (without quotes).
    Set "srvhidden=" to "srvhidden=no" (without quotes.)

  3. In the bootdrive:\STARTUP.CMD file, change

  4. "NET START REQ" to "NET START PEER" (without quotes).

The above changes will not necessarily allow Warp 4.x systems to access eCS stations. Additional changes are needed.

I am indebted to Mike O'Connor for the following information.

The principle illustrated by the following details is that the "Shared Resources & Network Connections" (W4) or "Sharing and Connecting" (eCS) objects in each system must contain both the User/Group information for anyone using that station, and the User/Group information for any remotions stations that will be using it in the future. Of course, the correct Permissions must be set up as well.

To simplify matters, it should be enough to have two UserID's and Passwords--one for the eCS systems (ECSADMIN) and one for the W4 systems (W4ADMIN). (At least these two were sufficient in my testing.)

This means that each system should have at least two UserID's (and Passwords): eCSADMIN and W4ADMIN. Note: the actual administrator UserID would be determined by the settings on the system, not the name.


This page last updated December 6, 2001


Copyright © 2003 VOICE
All rights reserved.