DOS program on a NT Server?

[gregshin]

We have an in-house DOS program running on our NT4 server, are workstations are running winblows 98. Before i got here they were trying to setup a network without any idea how to setup one correctly. I noticed that they are not using DHCP to issue IP's for the 40 or so workstations. They are using NETbui as their main protocal. I believe netbui is decent when you have a small LAN, but for bigger LAN's i hear they can really compromise and degrade the network. We are having problems with files being locked and opened multiple times by different users. Can a DOS program handle a network of over 40 computers? This DOS program is vital to their operations.
any info will be helpful!

 

[bockie]

You don't say what your DOS program does or how it interacts with your network, therefore I can't comment on your problems with files being locked by different users. However, I can provide some insight into NetBeui.

If all you are doing is file sharing, NetBeui will work fine. The problem with NetBeui is that it is a Broadcast protocol. That means each machine periodically will send packets of data across the network indicating that it resides on the network. Imagine it as if you were in a room full of people and everyone would yell out "I'm Here" at random intervals.

At work we have a network of 40+ machines. The two protocols we use are TCP/IP and NetBeui. I doubt NetBeui is causing your problems. With NT Server, when a file is opened on a share, that file is "locked" and can not be updated by another user. This is typical of most Network Operating Systems. It is a way of ensuring file and data integrity.

My suspicion is that this DOS program needs to access a specific file on the NT Server. Unfortunately, only one person will be able to access it at time. This will cause problems with other people who want to use that DOS program as well.

Hopefully I've shed some insight into your issue.

 

[Castellan]

More important about the DOS app is how it interacts with its data. The locking could be a result of the design of the program as opposed to the network. I agree though, its a horrible idea to run a network that size on netBeui