Discussion Locked

communicating via netbeui v.s. tcp/ip

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
On our network thru an NT server, in a small group all on tcp/ip, two computers could see one another, but no the others and vise versa until we put all in the group on netbeui. The network admin said it should have worked with tcp/ip. Was he wrong?

5 replies

by pschuvie

No, the network administrator was not wrong. It SHOULD work using tcp/ip and does. However, there are a variety of circumstances that can occur that often cause the computers to "not show up" and it takes some jiggling of settings and timing issues to resolve. This most often occurs in mixed client, Win95, Win98, WinMe, WinNT evironments.

The netbeui protocol addition overcomes some of the conflict issues by providing an alternate method of making the network aware of participating machines and most of the time gives the appearance that is most desired, without really curing the underlying issues relative to why the tcp/ip protocol, by itself, did not produce the expected result.

In summary, network administrator was not wrong, using the routable tcp/ip protocol should make all members appear and it oftens drives people nuts getting it to work on every machine.

by churger

Yes, your admin was right. You can use only tcp/ip and be happy.
First re-check ip's you gave for each workstation, subnet mask and other settings thru networking properties for LAN card TCP/IP.
Then make sure that all computers (since your LAN issmall) are registered in the same workgroup.
You should also set server as Master Browser Server, and make a couple of workstations as Backup (or secondary or whatever) Browsers

But if you satisfied with using NetBeui, then why change something?

This discussion is closed to new replies.