problem with Network Boot Disk from Symantec Ghost 7.5 Corporate Ed.

['chris']

hi

I made Network Boot Disk with Boot Wizard
from Symantec Ghost 7.5 Corporate Ed.

but if I try to boot the Workstation with this
Boot Disk, then I get following error:
-------------------------------------------------
MS-DOS Lan Manager v2.1 Netbind
ERROR 33: unable to bind
-------------------------------------------------

I tried both ways to assign the fix IP address
or via DHCP, but still get this error.

the DOS driver FETND.DOS for the network card
Via Rhine II Fast Ethernet Adapter
should be correct, because I don't see any driver errors.

knows someone, what's wrong ?

kind regards
chris

['chris']

I found out:

there was a missing driver name in protokol.ini

[Thomas Tesone]

I have the same problem and I don't know how to fix it. Could you please help me? This is real urgent!!

[Thomas Tesone]

It would also be really helpful if you gave me a URL to download the drivers to use

[Norman_21]

Chris,

It may be late but I thought that you'll keep this link for future reference:
http://service1.symantec.com/SUPPORT/ghost.nsf/8477deaaaafc102288256b1e00704619/ceb803e8233d582a882566720077e978?OpenDocument∏=Symantec%20Ghost&ver=7.5&src=ent&pcode=symghost&dtype=corp&svy=&prev=&miniver=symghost_75

Thomas,
Run the boot disk wizard again and make sure the NIC driver for the target PC is available and selected:
http://service1.symantec.com/SUPPORT/ghost.nsf/docid/2000040710064725?Open&src=ent&docid=2000062113392125&nsf=ghost.nsf&view=8477deaaaafc102288256b1e00704619&dtype=corp∏=Symantec%20Ghost&ver=7.5&osv=&osv_lvl=


If the driver is not available you'll need to add it to Template Adapter list:
http://service1.symantec.com/SUPPORT/ghost.nsf/docid/2000011211551725?Open&src=ent&docid=2000040710064725&nsf=ghost.nsf&view=docid&dtype=corp∏=Symantec%20Ghost&ver=7.5&osv=&osv_lvl=

Hope this help

[Thomas Tesone]

The problem is that I got DOS drivers for de VIA Rhine II but I get the same error as Chris:
MS-DOS Lan Manager v2.1 Netbind
ERROR 33: unable to bind

I don't know what to do...

[Norman_21]

Thomas

I don't know what's happening to this thread but I'd suggest you start your own thread. Meanwhile, refer to this article on how to add or modify NIC template in Ghost:

http://tinyurl.com/3ljcm

How to manually create a Ghost network boot disk:
http://tinyurl.com/4c9nt

How to troubleshoot a Ghost network boot disk:
http://tinyurl.com/5zgjj

Here is an example of the protocol.ini file for a Broadcom 4401 NIC card:
[protman]
drivername=PROTMAN$

[pktdrv]
drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66

[nic]
drivername = B44$

Hope this help

[Thomas Tesone]

I managed to boot without any errors. There was something missing in the Protocol.ini file.
Somewhere it said DRIVERNAME =
And nothing after that... I searched that name and it worked fine! :D

[x85446 · Accepted solution]

Nasty Nasty configuration error: netbind.com does not like the format of the protocol.ini or if your using Barts. I have battled this bug all day, trying every driver ever made by brodcom. Finally, another forum pointed me in the right direction. If your having problems with whatever driver version,

1. install the latest b57.dos from http://www.broadcom.com/support/ethernet_nic/downloaddrivers.php.
2. look at the .ini file (I bet it reads)

; Protocol.ini section for the Broadcom Ethernet NDIS2
[b][B57][/b]
DriverName = "B57$"

Well there is the problem. netbind.com "don't likey" the [b][B57][/b].

3. make it read


; Protocol.ini section for the Broadcom Ethernet NDIS2
DriverName = "B57$"


and presto, it works! (thought I would share 10 hours of my pain with you.) Bart's disk uses netbind.com version 2.1, I know there is a 3.0 out there, I didn't try it. Brodcom ships all their .ini files with the [B57] but bart's netbind.com "no likey"

[David Cloyd]

I ran into the same problem. After reading the info above I searched through the VIA/Rhine II install material and found a sample protocol.ini file(I think it was located int the MSLanMan directory) the sample protocol.ini file contained the proper driver name for the FETND.dos file which was FetND$. After modifying the NIC template in Ghost I had no problem booting the machine.

['chris']

here is my protocol.ini:


[network.setup]

version=0x3110

netcard=ms$FETND,1,MS$FETND,1

transport=ms$ndishlp,MS$NDISHLP

transport=ms$netbeui,MS$NETBEUI

lana0=ms$FETND,1,ms$netbeui

lana1=ms$FETND,1,ms$ndishlp



[ms$FETND]

drivername=FETND$



[protman]

drivername=PROTMAN$

PRIORITY=MS$NDISHLP



[MS$NDISHLP]

drivername=ndishlp$

BINDINGS=ms$FETND



[ms$netbeui]

drivername=netbeui$

SESSIONS=10

NCBS=12

BINDINGS=ms$FETND

LANABASE=0

[Night Rider]

I like dinosaurs. I like the raptors. I like Dell. I like cows. I like hippos.

['chris']

in my last posting, I posted protocol.ini for NETBEUI protocol instead for TCP/IP

for a TCP/IP network boot floppy pls look here:

http://www.lboro.ac.uk/computing/desktop/reps-xp/ghost-disk.html

and:

http://digital.ni.com/public.nsf/websearch/C1A843A4F8DB753D86256C1C005ADCF0?OpenDocument

make a great day !
chris

['chris']

for NIC: INTEL PRO/1000MT, I'm using this protocol.ini:

[network.setup]
version=0x3110
netcard=a$E1000,1,A$E1000,1
transport=tcpip,TCPIP
lana0=a$E1000,1,tcpip

[a$E1000]
Drivername=E1000$
NODE="00802F0A04F4"
; Speed=Auto-Speed
; ForceDuplex=Auto

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

[tcpip]
NBSessions=6
DefaultGateway0=
SubNetMask0=
IPAddress0=
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=a$E1000
LANABASE=0


and this system.ini:

[network]
filesharing=no
printsharing=no
autologon=no
computername=test
lanroot=a:\net
username=administrator
workgroup=mydomain
reconnect=no
dospophotkey=N
lmlogon=0
logondomain=mydomain
preferredredir=full
autostart=full
maxconnections=8

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

[Password Lists]

*Shares=a:\net\Shares.PWL
ADMINISTRATOR=A:\NET\ADMINISTRATOR.PWL


and it works excellently !

greetings
chris