when do non TCP/IP protocols interfere with network?

In another post, I had tried all the usual stuff to find out why a Win98 and WinME PCs were not connecting to WinXP pcs on a network.

Then at one point, I noticed that the ME and 98 pcs had the followng protocols, in addition to TCP/IP:
(Nwlink?) NetBios
(Nwlink?) IPX/SPX something or other

Up to then, I had only been checking the network properties of the TCP/IP protocol.

(1) Is it possible that the other protocols were interferring with the network access? How do you check this?

(2) To rule this out  -- when is it safe to remove the non TCP/IP protocols?

(3) Am I correct in assuming that different protocols get "dibs" on network adapters, via "binding order of network adapters"?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

The installed protocols do not interferate. For xsample ipx/spx was used by w98/me for some network apps on local network and also for some games.
you can remove the other prot if you shure no program is using it

there where a lot problems with connecting xp to w98 because of workgroups and domains and so on. So check it all the pc's are in the same workgroup if there is no domain configured on the xp box and so on...

and also:
try to ping the machines <to check the connection>
Set sharing on some files
On W98 in network settings you have to enable sharing!


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Are you running a Novell network? If not, chances are, you don't need anything with Nwlink or IPX/SPx. The protocols shouldn't interfere, but the traffic can possibly slow a network down for unneeded protocols.
I agree with masnrock- They DO interfere in that they put needless traffic on a network.  Depending on what they are, they will be carried by other protocols - for instance, you run IPX/SPX on a TCP/IP network.  Well, IPX traffic is still encapsulated into Ethernet at layer 2 - still goes out on the wire - still occupies a transmission slot.

If nothing else, it's just sloppy.  It increases the "back ground noise" just the same as a person making announcements in a foreign language in a room full of people speaking a common language.

2.) you can remove them at any time you are confident they're not in use - beware, it may require a reboot depending on the OS - so you might want to plan it well on a server.

3.) Yes.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

I agree with you guys,  but the interference is not that kind that you canot comunicate with tcpip.
and not just novel uses ipxspx. W98 can use ipxspx for sharing. And for games <solitare and so > it uses just this prot
I was just picking on IPX/SPX.  I've seen routing protocols coming from clients!

If it's not used, or in appropriate for the network, then best practice is to shut it down.  Why run an IP6 client if you're not using IP6 (for instance)!?!?
Michael SCommented:
More often than not if you're trying to access files and shares on an XP machine, then you have to:

1. Have the computers on the same workgroup/domain.
2. Make sure the shares give Everyone full control, not the folders.
3. Make sure any Windows Firewalls are turned off.
4. If you're not sharing folders with Everyone permissions, make sure there is a user account on the XP machine associated with whatever is trying to access it.

Other protocols will only listen for their own protocols, they do not interfere with the main protocol you want to use.

>>Other protocols will only listen for their own protocols, they do not interfere with the main protocol you want to use.

This just isn't true.  An encapsulated protocol will be received on a NIC and sent up the stack until it can unwrapped and determined that there isn't anywhere higher to go, at which point it will be disgarded.  This still puts a tangible load on the physical medium, the NIC, and processor.  If the wire, NIC, or processor is busy doing other things then they can't do what you want them to do.

Granted, the delay may be inconsequential, but its still there nevertheless.
Michael SCommented:
I understand they interfere to the extent you mentioned, but as you stated the delay is inconsequential for a setup like this - the issue is not performance on the wire, it's whether or not a conflict would cause these machines to not talk to each other.  In this case, with the protocols mentioned, this shouldn't cause the issue at hand.
dgrrrAuthor Commented:
OK, thanks for the info you guys!

Just to be sure -- do the above answers (e.g. that it's OK to delete this if I'm 'only using TCP/IP) also apply to the following:
NWlink NetBios
NWlink IPX/SPX/NetBios compatible transport proto...

(in other words, does "NWLink" or "compatible transport proto..." change things?)

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.