Difference between TCP/IP and NETBEUI protocols?

[J741]

We replaced the "server" on an old Windows 98 peer-to-peer network with a Windows 2003 server, configured as a standalone server. We copied the entire shared data directory from the old Windows 98 "server" to a shared data directory on the new Windows 2003 server. We made sure that all the Windows 98 workstations had the TCP/IP protocol installed. Now when the users attempt to run their old database program from any of the Windows 98 based workstations, they are presented with a "Multi User ID Invalid" error message, and the program will shut down. We have fixed the problem by adding the NETBEUI protocol to the Widnows 2003 server, as per the instructions found at

http://www.winnetmag.com/Article/ArticleID/41056/41056.html

So my question is, what is so different between the TCP/IP protocols and the NETBEUI protocol that would cause such an issue accessing files from a shared network resource?

- Confused
- James.

 

[mlichstein]

Netbeui is a very simple protocol that requires almost no configuration.

In comparison, TCP/IP is very complex, and there are many things to configure, and therefore many places where mistakes can be made.

Netbeui is also no longer supported by Microsoft.

 

[J741]

That much general knowledge I already know, but I'm looking for more specifics that may help me change the TCP/IP configuration enough to resolve the issue I mentioned, without the need for the NETBEUI protocol.

- James.

 

[Eupher]

Have you bound TCP/IP to "Client for Microsoft Networks" and "File and printer sharing for Microsoft Networks" and enabled NetBIOS over TCP/IP in the clients' TCP/IP properties?

Ken S.