Two NICs on WFW3.11/MS Networking

[tuklu_san <"supratim sanyal]

Hi
Looking for an example of PROTOCOL.INI supporting two network adapters
on WFW/MSNetworking. I would like to use the first adapter for TCP/IP
and the 2nd one for another proprietary protocol.
TIA.

[Grant Taylor]

On 01/25/2018 04:05 PM, tuklu_san <"supratim sanyal wrote:
> Hi

Hi,

> Looking for an example of PROTOCOL.INI supporting two network adapters
> on WFW/MSNetworking. I would like to use the first adapter for TCP/IP
> and the 2nd one for another proprietary protocol.

I don't know if it helps or not, but here's C:\WINDOWS\PROTOCOL.INI from
a quick test VM.

I created the VM in VirtualBox with two AMD PCnet NICs. I'm not
completely sure about the driver and / or the I/O address configuration
for the vNICs. I bound Microsoft's 32-bit TCP/IP for Windows 3.x to the
first vNIC and NetBEUI to the second vNIC.

I have no idea how a proprietary protocol will change things. I suspect
that you would just trade the NetBEUI parts for your proprietary
protocol parts.

--8<--8<--8<--8<--8<--8<--8<--8<--8<--8<--
[network.setup]
version=0x3110
netcard=ms$pcntn3,1,MS$PCNTN3,3
netcard=ms$pcntn3,2,MS$PCNTN32,3
transport=ms$ndishlp,MS$NDISHLP
transport=ms$netbeui,NETBEUI
transport=tcpip-32r,MSTCP32
lana0=ms$pcntn3,1,tcpip-32r
lana1=ms$pcntn3,1,ms$ndishlp
lana2=ms$pcntn3,2,ms$ndishlp
lana3=ms$pcntn3,2,ms$netbeui

[protman]
DriverName=PROTMAN$
PRIORITY=MS$NDISHLP

[MS$PCNTN3]
DriverName=PCNTND$

[PCNTN3]
Adapters=MS$PCNTN3,MS$PCNTN32

[MS$NDISHLP]
DriverName=ndishlp$
BINDINGS=MS$PCNTN3,MS$PCNTN32

[NETBEUI]
DriverName=netbeui$
SESSIONS=10
NCBS=12
BINDINGS=MS$PCNTN32
LANABASE=1

[MS$PCNTN32]
DriverName=PCNTND2$

[MSTCP32]
BINDINGS=MS$PCNTN3
LANABASE=0
-->8-->8-->8-->8-->8-->8-->8-->8-->8-->8--

> TIA.

Hopefully that helps.



--
Grant. . . .
unix || die

[Thierry64]

I try it , looking for this , thanks

[Grant Taylor]

On 08/18/2018 05:25 AM, Thierry64 wrote:
> I try it , looking for this , thanks

You're welcome.

Please follow up and let us know what did(n't) work and what you
ultimately used.

Good luck. #hazfun

[tuklu_san <"supratim sanyal]

That helps, will try it and post results. The other protocol is DECnet
via PathWorks; I keep my IP and DECnet networks separate.

[Grant Taylor]

On 10/15/2018 10:59 AM, tuklu_san <"supratim sanyal wrote:
> That helps, will try it and post results.

:-)

> The other protocol is DECnet via PathWorks; I keep my IP and DECnet
> networks separate.

That makes sense.

I've not messed with PathWorks yet.

I assume that you're going to need to change the MAC address for
PathWorks. I have no idea how to do that in WFW3.11.

[tuklu_san <"supratim sanyal]

Actually I didn't have to do anything to insert the computed MAC
address; PathWorks somehow works with an arbitrary MAC and is rock-solid
and on HECnet (http://mim.update.uu.se/hecnet?node=wfw311). It is the IP
NIC I am having trouble with, interestingly.

Will play around this weekend using your PROTOCOL.INI.

If you want a copy of the VM I can upload it somewhere too.

Thanks,
Supratim Sanyal

[Grant Taylor]

On 10/16/2018 08:03 AM, tuklu_san <"supratim sanyal wrote:
> Actually I didn't have to do anything to insert the computed MAC
> address; PathWorks somehow works with an arbitrary MAC and is rock-solid
> and on HECnet (http://mim.update.uu.se/hecnet?node=wfw311). It is the IP
> NIC I am having trouble with, interestingly.

That surprises me. I thought that DECnet (Phase IV) had to use modified
MAC addresses. I guess if they were set appropriately at the VM level,
they wouldn't be a problem.

> Will play around this weekend using your PROTOCOL.INI.

*nod*

> If you want a copy of the VM I can upload it somewhere too.

I think I'm more interested in the PathWorks installation files than a
full VM.

That being said, if said install files are in the VM, I am perfectly
happy to extract them.

[tuklu_san <"supratim sanyal]

I sent you a direct email, hope you have it.