Fixed IP address setup help?

[Mike Luther]

Can somebody please help me here with a pointer to PEERLAN fixed IP address
setup for the server and workstation in MCP2 please?

I thought I had all this done correctly and have this working at a couple sites
a long way from here with WARP4 servers and MCP2 workstations. I've tried to
start over at this with a WARP4 server as well now. That with Linksys or SMC
'dumb' switches for LAN cable connection, just like at the remote sites. But
here, no matter what I do, I can't seem to get a workstation to ever see the
server!

What I am after is to separate the PEERLAN on the NETBIOS side from the
Internet which will have no access to or be accessed from the PEERLAN side.
However, one workstation has both DHCP on LAN0 and a second NIC as LAN1 without
IP forwarding. I sent one workstation just like that to one of the remote
sites, configured as I thought right. It works perfectly at this.

But on the bench here, no matter what I do with the new MCP2 server which has
nothing but a LAN0 on it, can I ever connect to it at all from the same
configuration patterned remote workstation.

The MCP2 test fixed IP address server seems to be working fine. I can log on
to it at that local desktop and see the defined shared directories and all just
as I expect. But nothing I can do seems to let me ever see or ping that test
server from the test workstation.

I've looked at the MIT help URL for PEERLAN home network setups and so on. But
that is all Warp4 oriented as well.

Can somebody point me to an example cited how to fill out the blank spaces in
the setup folders and critical files to 'define' this? Or type in the
suggested needed data items for the server in reply to me here?


Thank you!

[Mike Luther]

Suggestion received and fixed..

Post by Mike Luther
Can somebody please help me here with a pointer to PEERLAN fixed IP
address setup for the server and workstation in MCP2 please?

The bug is in the workstation setup for exactly the same error that we worked
on months ago with dual NIC's then. The bug is the OS/2 failure to properly
record the two different PEERLAN network operations in the IBMLAN.INI file, but
in a re-write corruption of it! I had modified the PROTOCOL.INI file as well
as the IBMLAN.INI file for the dual lan0/lan1 operation per the research work
of about a year ago. The IBM configuration program generically misses the
twin adapter setup in PROTOCOL.INI and the use of NET1,NET2 in the IBMLAN.INI
file, which you must do by hand, so I found out earlier.

What is the other glitch here is that if you for any reason delete the load in
the MPTN setup program which has to do with the second NIC, the OS/2 setup
program will remove the older by-hand items for the NET1, NET2 additions you
put in there by hand earlier in the IBMLAN.INI file! When you go back and
re-add the second NIC in the setup, you'll have to go in by hand and fix up the
IBMLAN.INI file all over by hand again as well!

If anyone wants the whole scenario here again, I'll be happy to post the long
post for the whole process. But likely not needed here as well too.