China DOS Union

-- Unite DOS · Advance DOS · Grow DOS --

Union site: www.cn-dos.net Forum site: www.cn-dos.net/forum
DOS stands for freedom, openness and progress. Let us work hard, learn from the openness and GNU spirit of FreeDOS and Linux, and together build and grow a free GNU GPL world!

中国DOS联盟论坛
The time now is 2026-06-25 03:26
中国DOS联盟论坛 » DOS媒体世界 & 网络技术 (多媒体室) » Error occurred with the Netbind.com command in DOS networking View 2,527 Replies 4
Original Poster Posted 2005-03-03 00:00 ·  中国 上海 鹏博士宽带
初级用户
Credits 68
Posts 3
Joined 2005-01-25 00:00
21-year member
UID 35628
Gender Male
Status Offline
Recently, I need to connect my DOS machine to the Internet. When I installed the Microsoft Network client for MS-DOS, I selected the TCP/IP protocol. In Autoexec.bat, there appeared commands such as C:\Net\netbind.com /// c:\Net\umb.com /// c:\Net\tcptsr.exe /// c:\Net\tinyrfc.exe /// c:\Net\nmtsr.exe /// c:\Net\net start and so on. However, when I restarted the machine, there was no expected prompt like "Type your user name, or press ENTER if it is c100:" to enter the user name and password.

So I had to manually type the C:\Net\netbind.com command. An error was prompted as follows:
MS-DOS LAN Manager v2.1 Netbind
Error :33 Unable to bind.
What is the reason? Could it be that there is a problem with the network card driver and binding the network card fails? I hope an expert can give some pointers!
Floor 2 Posted 2005-04-12 00:00 ·  中国 重庆 城口县 电信
中级用户
★★
Credits 335
Posts 96
Joined 2004-05-07 00:00
22-year member
UID 23928
Gender Male
Status Offline
How did you create your Microsoft Network client for MS-DOS disk? There might be an issue. You can take a look at the network boot disk I made before (supports 20 types of network cards).
Freebsd网站架设\局域网维护管理\硬件维修\电路图纸
欢迎到 振兴电子
http://zxdz.8800.org
Floor 3 Posted 2009-06-01 07:24 ·  中国 浙江 绍兴 电信
初级用户
Credits 22
Posts 8
Joined 2009-04-11 09:23
17-year member
UID 142685
Gender Male
Status Offline
I get the message
MS-DOS LAN Manager v2.1 Netbind
Error :45 Unable to bind.
Don't know why???
Floor 4 Posted 2009-06-12 09:40 ·  中国 香港 城市电讯有限公司
管理员
★★★★
專業島民
Credits 4,869
Posts 1,633
Joined 2002-12-10 00:00
23-year member
UID 465
Gender Male
Status Offline
Please check if there are items with the same name in BINDINGS= in protocol.ini. For example:



drivername=PROTMAN$


drivername=PKTDRV$
bindings=nic
intvec=0x60
chainvec=0x66

; The following section contains information specific to your network card

drivername=MHZX$


If bindings=nic, then there should be a item in protocol.ini. And the drivername= in should indicate the driver name of this NDIS2 driver (please modify according to the content of the INI file provided by the NDIS2 driver)
我的網站:http://mw16.2ya.com/ 我的網誌: http://scrappedblog.blogspot.com/
~
我的Winamp正在播放的歌曲:
Floor 5 Posted 2009-07-05 22:26 ·  中国 广东 珠海 电信
初级用户
Credits 58
Posts 26
Joined 2008-05-12 09:06
18-year member
UID 118462
Gender Male
Status Offline
Hardware conflict, change to an 8139, should be no problem
Forum Jump: