VOGONS

Microsoft Netowking client 3.0 TIP/IP netbind issues

Topic actions

First post, by robbo007

Posted on 
User metadata
Rank Member
Rank
Member

Hi guys,
I've been messing around trying to get my token ring II ISA adapter working. I managed to get the correct NDIS +packet dos drivers and I can successfully load the card in MSDOS and run the TCP/IP stack with mTCP.

I'm trying to get the MS network client 3.0 working with TCP stack but having loads of grief. Can't get it bound to the NDIS driver. I can bind NWlink without issues but not TCP/IP

When I run:
C:\NET\net initialize
C:\NET\netbind.com

I get:

Error: 255 Unable to bind.

Here is my config.sys

STACKS=9,256
DEVICE=C:\DOS\SETVER.EXE
DEVICE=C:\DOS\HIMEM.SYS
DOS=HIGH
FILES=40
BUFFERS=30
LASTDRIVE=Z
fcbs=16,8
device=c:\net\protman.dos /i:c:\net
device=c:\net\ibm16tr.dos
device=C:\LSP\DXMA0MOD.SYS 001
device=C:\LSP\DXME0MOD.SYS 
install=c:\temp\ibm\netbindr.com
device=C:\NET\ifshlp.sys

autoexec.bat:

SET SOUND=C:\SB
SET BLASTER=A220 I7 D1 T3
SET MIDI=SYNTH:1 MAP:E
SET MTCPCFG=C:\NET\MTCP\MTCPCFG.CFG
@echo off
PROMPT $P$G
PATH=C:\NET;C:\DOS;C:\WINDOWS;C:\XTGOLD;c:\norton
SET TEMP=C:\WINDOWS\TEMP
C:\NET\net initialize
C:\NET\nwlink
C:\NET\netbind.com
C:\NET\umb.com
C:\NET\tcptsr.exe
C:\NET\tinyrfc.exe
C:\NET\nmtsr.exe
C:\NET\emsbfr.exe
C:\NET\net start
/code]

Protocol.ini:
[code][network.setup]
version=0x3110
netcard=AdapterII,1,ADAPTERII,1
transport=ms$nwlink,MS$NWLINK
transport=ms$ndishlp,MS$NDISHLP
transport=tcpip,TCPIP
lana0=AdapterII,1,ms$nwlink
lana1=AdapterII,1,ms$ndishlp
lana2=AdapterII,1,tcpip

[TCPIP]
NBSessions=6
DefaultGateway0=192 168 2 1
SubNetMask0=255 255 255 0
IPAddress0=192 168 2 8
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=ADAPTERII
LANABASE=1
[MS$NWLINK]
FRAME=TOKENRING
DriverName=nwlink$
BINDINGS=ADAPTERII
[PROTMAN_MOD]
        DriverName = PROTMAN$
        PRIORITY=MS$NDISHLP
[DXMAIDXCFG]
        DXME0_NIF = DXME0.NIF
        DXMJ0MOD_NIF = DXMJ0MOD.NIF
        IBM16DOS_NIF = IBM16DOS.NIF
        IBM16DOS2_NIF = IBM16DOS.NIF
[DXME0_NIF]
        DriverName = DXME0$
        Bindings = IBM16DOS_NIF
[IBM16DOS_NIF]
        DriverName = IBM16TR$
        ADAPBUFFSIZE = 1032
        ADAPMINTRAN = 5
        ADAPMAXTRAN = 10
        MAXTRANSMITS = 5
…Show last 19 lines
        MINRCVBUFFS = 8
        SIZWORKBUF = 2048
        IOBASE = 0X86a0

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

[ADAPTERII]
DriverName=IBM16TR$
ADAPBUFFSIZE=1032
MAXTRANSMITS=5
MINRCVBUFFS=5
SIZWORKBUF=1112

[MS$NDISHLP]
DriverName=ndishlp$
BINDINGS=ADAPTERII

Reply 1 of 2, by paradigital

Posted on 
User metadata
Rank Oldbie
Rank
Oldbie

It’s been a long time since I was involved in token ring networking, but if that Token Ring II adapter is only a token ring adapter then does it even talk TCP/IP without some kind of bridge between the networks?

We used to bridge our BNC TCP/IP network to token ring using I think an Allied Telesys device.

Reply 2 of 2, by robbo007

Posted on 
User metadata
Rank Member
Rank
Member
paradigital wrote on 2023-11-17, 18:35:

It’s been a long time since I was involved in token ring networking, but if that Token Ring II adapter is only a token ring adapter then does it even talk TCP/IP without some kind of bridge between the networks?

We used to bridge our BNC TCP/IP network to token ring using I think an Allied Telesys device.

Hi. You can use the IBM local area network support driver with this card and also the 8bit Token ring adapter. No bridging of network needed. This then allows you to load either the MS networking client 3.0 TCP/IP or mTCP.

My issues are binding the TCP/IP to the card 🙁 Its got to be a bad parameter.
Regards

Go to top of page Go to top of page
Back to General Old Hardware
Close window
Close window