Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
Hi
Just a quick question.
We have a network with WIndows 98 machines that some of the printers are shared out to others. It's an Epson 1270 etc..
I have installed TCP/IP.Netbeui and Client for Microsoft networks and file and printer sharing.
By default the TCP/IP is binded to microsoft network and file sharing. I have unchecked it. So it's using netbeui instead but the default protocal is TCP/IP for internet access.
Is it necessary to bind TCP/IP to file and microsoft networking? If so what's the advantage and disadvantage of this?. We have just hubs in the network and one main switch.
We are only using it for file sharing on an NT server and internet access through a proxy. It's working Ok.
I had to bind TCP/IP to microsoft network for this messenger programs I installed for it to work.
Thanks in advanceKen

Netbui is fine for internal networking. It's even a lot more efficient for small networks, 'coz tcp/ip has a lot of overhead to make it routable. If you bind more protocols to the same service, all traffic will go out in ALL protocols, thus creating loads and loads of redundant traffic, slowing down your network. I strongly advise to to play around with network monitoring software to see what actually goes on.

![]() |
Where is DUN information ...
|
NT rpcss.exe
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |