Discussion Locked

Network startup diskette

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello

I am trying to prepare the network installation startup diskettes in Windows NT. The problem is, when the system boots it initializes the network and at the command NETBIND it gives "Error 33: unable to bind" and does not goto the network server.

Can somebody tell me where the fault is and how can I overcome it.

Thanks.

10 replies

by technojunkie

Without more info, it's hard to give a good answer. I run into the same problem every time I build a network boot disk (you'd think I would SAVE that floppy!!!). The best way I have found is to use the NIC manufacturer's recomendations regarding a boot floppy for their product. Let's face it, Microsoft has no interest in compatibility; or accurate instructions, for that matter. It will be the NIC manuf. that will supply you with correct instructions, and drivers as well. Typically, I will go tothe manuf's website, and do a search for "boot floppy". Make sure you've got available resources, too (IRQ, etc).

by arlo mccalla

I've had this problem on certain 3Com cards if the plug n play is enabled on them. I've had to use the 3COM Etherdisk utility (3c5x9cfg.exe is one, for example) to view the config on the card and disable plug n play. Hope this helps.

Arlo

by emanon

This problem normally occurs when you are using the NIC driver, NDIS595.DOS, shipped with the COMPAQ Ministation/EN.

RESOLUTION:
Compaq has the correct driver for the network adapter available on Compaq's FTP
server and soon on the CPQFORUM onCompuServe. The files to download are
SP0634.DOC and SP0634.ZIP. Following are the recommended steps of upgrading the
driver for the Netflex-2 ENET network adapter.

1. Create a directory called Compaq and download SP0634.DOC and SP0634.ZIP to the directory.

2. Unzip SP0634.ZIP. SP0634.EXE should be available.

3. Run SP0634.EXE. This extracts files QRST.EXE (creates an installation disk
for the Intel 595-16E network adapters) and NDIS595.DOS (updated driver for
Intel 595-16E).

4. Place a blank, formatted 1.44 MB floppy disk in Drive A and run QRST.EXE from
the Compaq directory.

by jcurl

This can happen when protocol stack or driver cannot be bound to NIC. Make sure SYSTEM.ini and PROTOCOL.ini files are correct. Here are samples (for 3Com 3c905):
Protocol.ini
[network.setup]
version=0x3110
netcard=ms$EL3C574,1,MS$EL3C574,1
transport=tcpip,TCPIP
lana0=ms$EL3C574,1,tcpip

[ms$EL3C574]
drivername=EL3C574$

[protman]
drivername=PROTMAN$
PRIORITY=TCPIP

[TCPIP]
DriverName=TCPIP$
BINDINGS=ms$EL3C574
LANABASE=0
NBSessions=6
SubNetMask0=255 255 255 0
IPAddress0=192 168 100 92
DisableDHCP=1

System.ini
[network]
filesharing=no
printsharing=no
autologon=yes
computername=COMP2
lanroot=A:\NET
username="user name"
workgroup="domain name"
reconnect=no
dospophotkey=N
lmlogon=0
logondomain="your domain"
preferredredir=full
autostart=full
maxconnections=8

[network drivers]
netcard=a:\net\el3c574.dos
transport=tcpdrv.dos,nemm.dos
devdir=A:\NET
LoadRMDrivers=yes

Jeremy P, MCSE

by jcurl

HAHAHA, look at answer 3 by EMANON, then go to Knowledge Base Article Q122056. I thought his answer sounded a little off the wall since you didn't mention anything about using a "Compaq Ministation/EN"!!! Can you say "plagiarism". Good lookup EMANON, ha!

This discussion is closed to new replies.