MSDOS networking

Hi there.

Sorry but this is kind of an emergency and I hope someone can help.

I can make network bootdisks, I have made a network bootdisk which can access a machine VIA router, works perfectamon.

If I take this bootdisk and connect P2P it will hang....

I made a network bootdisk from:

http://www.wown.com/j_helmig/w9xbtflp.htm

and that is ok.

however, when it loads my sis 900 driver, the lights on the nic goes off, and then:

"Error 5733: The protocol manager reported an incomplete binding. For more information, please contact your local adminstrator "

What does this mean and how can I solve it?

If I use a RTL8139 nic, the driver doesn't like it lol

so please, can we solve this bug or is there another MSDOS network bootdisk that I can make WHICH WORKS FOR P2P???

PLEASE help.

Thanks

 

Looks like a bad driver/config files or a problem with the NIC.

Test with the driver and boot disk from Bart.

 

um...the nic and driver is fine


but I don't like the bart disk lol...I dunno why, it doesn't work, I can't even get in the map network drive part and sometimes it just hangs, on ANY system and ANY nic!

PLEASE, I am really desperate.

Thank-you

 

any 1????

well, if it's too hard, then how can I solve that problem? what does it mean and how can I solve it?

 

When you say Peer 2 Peer do you mean you are trying to connect 2 PCs via a crossover cable?

 

YES SIR!!!!

using a x-over cable.

Please SIR, I need help, and it must be sorted out b4 this morning, as it is the last day of myself teaching some people, at my uncles technical shop, about basics of networking. I know I am not great at networking, but I can teach the basic stuff, certainly to improve the way they work.

Even myself, I can do it no probs, with a router, but not P2P (X-OVER CABLE)

Help !

 

Techno - I know your deadline has passed but if you are still interested, post back.

I am curious about a couple of things though. This whole process should work but is much more complex than should be needed. And not what I would call "basic ".

Do you just want to teach folks how to connect two PCs using NICs and a UTP cable wired cross-over?

 

yup, i'm interested, I told them that there will be an extension in the date *phew*

YES to answer ur question but more to it than that

I have connected 2 PC's together, P2P using a Xover cable.

Now, what I am trying to do is to map the machine 1 (master) from machine 2 (destination) and let me access to machine 1 from machine 2, IN MSDOS

I need a network bootdisk that WORKS FOR P2P - XOVER machine. I have bootdisks that works only via Router, perfect but I don't want to teach them the router part yet, plus they don't have 1

So please...n e advice/hints/tips, please, let me know.

The machine 2 has the SIS 900 nic.....just incase, and I do have the old and new drivers for MSDOS but no luck, still gives me that error msg.

Thanks

 

The error you cited indicated that a protocol (name not specified) wasn't binding properly to the NIC.

Sounds like a problem with the protocol.ini file you are using. If it is the one that works thru a router, it will fail with the Point to Point setup. Likewise, one that works with the direct NIC to NIC connection would fail thru the router.

If routed, you must be using TCP/IP or IPX/SPX since NetBeui won't route.

For that you must be using IP addresses that live on different subnets else no need to route them and problems in trying to route traffic between systems living on the same subnet.

Or maybe the router is providing DHCP information and your protoco.ini is forcing the PCs to look for a DHCP server that doesn't exist.

Please post a copy of the protocol.ini you are using.

And please say if you need to do this whole thing using a specific protocol or just whatever is easiest.

 

thanks for the reply.

this is a COMPLETLY new floppy disk, please go to that link I put up in this thread, that link is where I created the floppy disk from, exact same, except I changed the drivers for the nic. that's all.

I don't happen to have the copy of the disk in my hand, it's at the shop, waiting to be used....

It's the exact same file as that link.

What else can be done? do u have any knowledge on how to create a MSDOS BOOT NETWORK FLOPPY?

Thanks

 

I did go to the link. It is putting a copy of the protocol.ini file from a PC onto the floppy.

That particular .ini file must have the information needed to set up the networking protocol. The default protocol.ini is lacking most of the necessary information.

For instance, this one will set up TCP/IP using the IP address, netmask, etc. and will forbid DHCP settings. It will also bind the TCP/IP protol to the NIC. However, each PC would need a slightly different copy since they couldn't both have the same IP address.
[network.setup]
version=0x3110
netcard=ELNKII$,1elnkii$
transport=tcpip,TCPIP
lana0=elnkii$,1,tcpip

[TCPIP]
NBSessions=6
SubNetMask0=255 255 255 0
DefaultGateway0=0 0 0 0
IPAddress0=192.168.0.1
DisableDHCP=1
DriverName=TCPIP$
BINDINGS=elnkii$
LANABASE=0

[elnkii$]
DriverName=elnkii$
; Interrupt=3
; IOADDRESS=0x320

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

While this one will do pretty much the same except it will require and use a DHCP server.
[network.setup]
version=0x3110
netcard=cpq$n100,1,CPQ$N100,1
transport=tcpip,TCPIP
lana0=cpq$n100,1,tcpip

[TCPIP]
NBSessions=6
; SubNetMask0=255 0 0 0
; DefaultGateway0=0 0 0 0
; IPAddress0=0 0 0 0
DisableDHCP=0
DriverName=TCPIP$
BINDINGS=CPQ$N100
LANABASE=0

[CPQ$N100]
DriverName=N100$
ForceDuplex=Auto
Speed=Auto-Speed

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

And if you are going to use NetBeui on both machines, you would want something more like:
[network]
version=0x3110
netcard=ms$elnk3,1,ms$elnk3
transport=ms$ndishlp,MS$NDISHLP
transport=ms$netbeui,MS$NETBEUI
lana0=ms$elnk3,1,ms$netbeui
lana1=ms$elnk3,1,ms$ndishlp

[ms$elnk3]
drivername=elnk3$

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

[MS$NDISHLP]
drivername=ndishlp$
BINDINGS=ms$elnk3

[ms$netbeui]
drivername=netbeui$
SESSIONS=10
NCBS=12
BINDINGS=ms$elnk3
LANABASE=0

 

Thanks a bunch! I will give it a bash today and last question...

What is netbeui? will I be using it? heheheh

just wanting to access the other machine, that's all!

Must it have a DHCP server active? Can we disable it?

thanks

 

NetBeui - Old Microsoft networking protocol.

Good points - no addressing to fiddle with, pretty much sets itself up. If the PCs on the LAN are in the same workgroup, NetBeui will let them talk together and work together.

Good or Bad point - depending on your setup. NetBeui will not cross a router. By design.

Bad point (but only with a large network) - NetBeui resolves most everything by broadcasts. Unless your network is larger than 20-30 PCs, the extra network traffic doesn't slow things down at all.

For your situation, I'd say it was an ideal place to start and for any small network that doesn't need machines to connect to the internet, it is hard to beat.

But it doesn't know about or understand or see any TCP/IP things so no DNS, no DHCP, no internet awareness, etc.

It can easily run along side TCP/IP though so if you have a NetBeui network running and discover you want a couple of machines (or all the machines) to route or reach the internet, you can just add TCP and leave NetBeui running. They simply don't see each other.

 

cool, thanks for that.

just needing 2 PC's connected together, using a Xover cable, that's it, full stop

Thanks for that, I will get back to u as soon as poss

thanks, I appreciate this