Solved

DOS - Netbind - Unable to bind

Posted on 2002-05-14
9
1,544 Views
Last Modified: 2007-11-27
I'm trying to make a bootable disk (NT) I've my NIC is 3c905c - I have the correct drivers in the \net directory and the drivers load to and bring the interface to a pingable state. the next command in the Autoexec.bat is NETBIND and it fails every time with ERROR 33 ?

ANY SUGGESTIONS - this is an emergency

Through the 3com utils I was able to determine that the card is responding to IRQ 11 @ 1000h

in my protocol.ini i've matched these settings to no avail


HELP HELP
0
Comment
Question by:hkaufm2
  • 5
  • 2
  • 2
9 Comments
 
LVL 7

Accepted Solution

by:
rin1010 earned 300 total points
Comment Utility

hkaufm,

Try putting everything in protocol.ini in lower-case and see if that works.

If not, try manually entering the drivername as "EL90X$" (but in lower-case)
under the [tcm$el90x] or header section, like:


[tcm$el90x]

drivername=el90x$


Please post back if that doesn't help...
 
0
 
LVL 7

Expert Comment

by:rin1010
Comment Utility

Should've mentioned to try the second option first
before bothering with the lower-case comment...
It can be tested in upper-case format, e.g.;

DriverName=EL90X$
 
0
 

Author Comment

by:hkaufm2
Comment Utility
I'll try it in the morning  - thanks
0
 

Author Comment

by:hkaufm2
Comment Utility
thanks - the lower case seems to have fixed the binding problem - now my problem is after the binding and loading of all the tcp protocols - the card just isn't accessible?

any thoughts
0
Top 6 Sources for Identifying Threat Actor TTPs

Understanding your enemy is essential. These six sources will help you identify the most popular threat actor tactics, techniques, and procedures (TTPs).

 

Author Comment

by:hkaufm2
Comment Utility
thanks - the lower case seems to have fixed the binding problem - now my problem is after the binding and loading of all the tcp protocols - the card just isn't accessible?

any thoughts
0
 

Author Comment

by:hkaufm2
Comment Utility
thanks - the lower case seems to have fixed the binding problem - now my problem is after the binding and loading of all the tcp protocols - the card just isn't accessible?

any thoughts
0
 

Author Comment

by:hkaufm2
Comment Utility
thanks - you're a life saver
0
 

Expert Comment

by:liloXwin
Comment Utility
0
 

Expert Comment

by:liloXwin
Comment Utility
0

Featured Post

Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

Join & Write a Comment

Using dates in 'DOS' batch files has always been tricky as it has no built in ways of extracting date information.  There are many tricks using string manipulation to pull out parts of the %date% variable or output of the date /t command but these r…
Being a system administrator some time we require to do things remotely, one of them is installing software. Here I am going to tell you how to install software through wmic (Windows management instrument console). I am not at all saying that this i…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now