OS2FORCE.CH	PEER
Setup	Servers / Software / SPAM	LINKS
PEER Injoy Firewall ADSL Text Version TCP/IP Text Version	Weasel Mailserver  web/2 Must have own written Spamfilter How mail works	Web Infos & Antispamlist User groups dealers Home Pages IBM/ECS

My router is a Zyxel 650R

We connect the router as shown:
 

Warp 4:

during the installation, we have to choose on the screen network File   and Printer Sharing  If not, we do it now:
System -> Systemconfiguration ->Install/Remove -> networkinstallation.

The Peer installation does only install the peer installation programm.

We find this Symbol at Install and Remove.   Another source is x:\IBMLAN\INSTALL\PEERINST.EXE
Just now the insallation process starts.

during the installation of warp4 or ECs, we can select the Networkcard (NIC) and the wished protocols.   We can do this, any time later.

After the insatallation of network and printer sharing, we find a new Iocn on the WPS:

If our NIC is not listet, we install the needed Device driver ba hand.
Oftly we can find the OS/2 Device driver in a directory, that is under Microsoft Network.

We copy the file *.NIF and *.os2 in to the directory
x:\IBMCOM\MACS

We start the insatllation with System -> Systemconfiguration ->MPTS, or we start direct x:\IBMCOM\MPTS.exe

Alternativly, we can do the Setup by Hand. You have exactli to know, what you are dooing, or you you don't know the word fear. The installation is just set up the Parameters in the file Protocol.ini
Lest take a look into the file x:\IBMCOM\MACS\E100EOS2.NIF
[E100B]
   Type = NDIS
   Title = Intel(R) PRO PCI Adapter
   Version = 3.12
   Drivername = E100B$
   Xports = NETBEUI LANDD

[FILE]
   Name = E100B.OS2

[SPEED]
   display = "Media Speed"
   type = Decimal
   set = 10, 100
   optional = YES
   editable = YES
   help = "The driver can configure the adapter for either 10 or 100 Mbps.
 Assigning a value to this parameter will override the Auto-Speed-Sense feature
 of the driver.  Leave the field blank to enable the Auto-Speed-Sense feature."

[FORCEDUPLEX]
   display = "Force Duplex Mode"
   type = Decimal
   set = 1, 2
   optional = YES
   editable = YES
   help = "The driver can configure the adapter for either Half or Full Duplex.
 Automatic detection of Full Duplex REQUIRES a hub with ports which are capable
 of performing N-Way auto-negotiation, so forcing the duplex mode to Full is
 recommended for most users connecting to a Full Duplex hub.  Assigning a value
 of 1 (Half) or 2 (Full) to this parameter will override the auto-negotiation
 feature of the adapter, and will also make the SPEED parameter REQUIRED.
 Leave the field blank to enable the auto-negotiation feature."

[SLOT]
   display = "Slot/Device Identifier"
   type = Hexadecimal
   range = 0-1FFF
   optional = YES
   editable = YES
   help = "Use of this parameter is only required in systems with more than one
 adapter installed. If you are installing more than one PCI adapter: 1) complete
 the configuration process, but leave the Slot field blank for each driver;
 2) restart the system and record the list of Slots that each driver displays;
 3) complete the configuration by assigning one of the values from the list to
 the Slot parameter of each driver. Leave the field blank if you have only one
 adapter installed."

[NODE]
   display = "Locally Administered Address"
   type = String
   strlength = 12
   optional = YES
   editable = YES
   help = "Use of this parameter to modify the network address used by
 the adapter."

let us take a look at the PROTOCOL.INI
This file includes the NIC, the Protocols Netbios and TCP/IP.

[PROT_MAN]

   DRIVERNAME = PROTMAN$

[NETBEUI_nif]

   ETHERAND_TYPE = "I"
   USEADDRREV = "YES"
   OS2TRACEMASK = 0x0
   SESSIONS = 254
   NCBS = 255
   NAMES = 29
   SELECTORS = 15
   USEMAXDATAGRAM = "NO"
   ADAPTRATE = 1000
   WINDOWERRORS = 0
   MAXDATARCV = 4168
   TI = 30000
   T1 = 1000
   T2 = 200
   MAXIN = 1
   MAXOUT = 1
   NETBIOSTIMEOUT = 500
   NETBIOSRETRIES = 3
   NAMECACHE = 1000
   RNDOPTION = 1
   PIGGYBACKACKS = 1
   DATAGRAMPACKETS = 10
   PACKETS = 335
   LOOPPACKETS = 8
   PIPELINE = 5
   MAXTRANSMITS = 6
   MINTRANSMITS = 2
   DLCRETRIES = 10
   FCPRIORITY = 5
   NETFLAGS = 0x0
   Bindings = E100BEO2_nif
   DriverName = netbeui$

[IBMLXCFG]

   NETBEUI_nif = NETBEUI.NIF
   TCPIP_nif = TCPIP.NIF
   E100BEO2_nif = E100BEO2.NIF

[TCPIP_nif]

   Bindings = E100BEO2_nif
   DriverName = TCPIP$

[E100BEO2_nif]

   DriverName = E100B$

[NETBIOS]

   DRIVERNAME = NETBIOS$
   ADAPTER0 = NETBEUI$,0

For sure, the Protocol.ini looks on almost every PC different. Dont chanche the setup for Netbui.nif. Wat you can chanche are the setup for ADAPTER, DriverName and Bindings. Keep in mind, that the very fist networkcard is Adapter0. The second NIC is ADAPTER1

On the firewall PC with two NIC's, it looks like this:
 

[PROT_MAN]

   DRIVERNAME = PROTMAN$

[IBMLXCFG]

   netbeui_nif = netbeui.nif
   tcpip_nif = tcpip.nif
FXWRAP_nif = fxwrap.nif
   RTL8139_nif = RTL8139.nif
   E1000_nif = e1000.nif

[NETBIOS]

   DriverName = netbios$
   ADAPTER0 = netbeui$,0

[netbeui_nif]

   DriverName = netbeui$
   Bindings   = RTL8139_nif
   ETHERAND_TYPE = "I"
   USEADDRREV = "YES"
   OS2TRACEMASK = 0x0
   SESSIONS = 130
   NCBS = 225
   NAMES = 21
   SELECTORS = 50
   USEMAXDATAGRAM = "YES"
   ADAPTRATE = 1000
   WINDOWERRORS = 0
   MAXDATARCV = 4168
   TI = 30000
   T1 = 1000
   T2 = 200
   MAXIN = 1
   MAXOUT = 1
   NETBIOSTIMEOUT = 500
   NETBIOSRETRIES = 3
   NAMECACHE = 1000
   RNDOPTION = 1
   PIGGYBACKACKS = 1
   DATAGRAMPACKETS = 50
   PACKETS = 300
   LOOPPACKETS = 8
   PIPELINE = 5
   MAXTRANSMITS = 6
   MINTRANSMITS = 2
   DLCRETRIES = 10
   FCPRIORITY = 5
   NETFLAGS = 0x0

[tcpip_nif]

   DriverName = TCPIP$
Bindings   = RTL8139_nif,FXWRAP_nif

[RTL8139_nif]

   DriverName = RTSND$
   MEDIUM = "_AUTO"
   NOIRQ = 0
   APM = 1
   CARDBUS = "NO"

[FXWRAP_nif]

   Drivername = FXWRAP1$
   Bindings   = E1000_nif
 

[E1000_nif]

   DriverName = E1000$

We have two NIC's an a adidtional protocol.

Start Peer:

Peer_networkstation  If Peer is not running yet, it will start now. It takes a few seconds. Next, we have to tipe our Username and Password   Default values aret USER and password.   We can at the point Networkuser  setup our user.

On Warp 4 we choose Connections -> Drives and press the right Mousebotton .   In the Pop Up Menu , we have Start Shared Access...Und Manage Access. First, we have to Admin AccessWe give every User his Propertys to Write and / or read.

Under ECS it is Ecommstation-> Drives. The rest is the same as Warp 4.

On Warp4 we open Connections -> Network -> Networkservice -> Shared Ressource and Networkservice.
On the page Kennung we fill in a name for the PC and a name for the network. The Domain name for the Peer Network does not have to bee the same as for the internet. Same with the PC. But, Hostnames must be individual.

On the Page shared Ressources we see the Drives we selected for sharing.
On the page Authorisation we don't fill out anything, as long as it ist not absolutly needed.
All other Pages, we let them, as they are.

Finaly made the setup on all PC's, we start PEER and open Connections -> Network -> LAN Requester Ressourcen-Browser.
Bei ECS : Local Network -> Networkservices -> LAN Ressourcen-Browser.

In both case we see al Peer PC's and all Servers. We see also our own PC. Open a PC we see the Drives for Shared access.

With the Ressouce Broweer, we can Copy, move, delete files per Drag and Drop. But Programms cannot work with these files. We get a error "no acces to file......".   To chanche this, Programms need a Drive letter, like C: or E: .....

We klick with the right mousebutton on the networkDriveand on Assign Drive...we assign a free Driveletter. The Networkdriveletter should not be just after the last existing last driveletter. Let some letters in between. Beginning with M: sould be ok. The driveletters shold be the same in the hole peer network.
If you do it the other way, it will work the same, but it is easier when the same drive has on every other PC the same driveletter.

In a Companie every User should have his unike username and his unike password.

For homeuser, you can leave the default user and password. But the Network messages don't work!!
Why networkmessages ??
You can send messages to other users and read messages from other users. Something like email, but it stays in the Netbiosnetwork.   This is s good solution, to tell useres, bevor doing something on a server.
 

Do we have to do this every time so complicated ??

No, we cann fill into the Startup.cmd following:
 

And OS2/Peer -> Peer-Workstation Announce -> Characteristics resp.   Local Networc -> LAN anounce
right Mousebutton in page Programm is the default value on Parameter /V:DOMAIN /D This is a announce for a lan. This is ok, if you have a OS/2 Server. But if you just have a   Peer Network, then chanche this to: User /P: Password /V:LOCAL   where the user ist the username and Password ist the password for this user.

On the next double klick on Peer_Workstation AnnounceIt seems, that nothing happend.

When we get a error message :
UPM0004C: The Programm could not be startet.
Errorcode is: 19
We are already announced and have access, or we made a space too much on the beginning or after the doublepoint.