Netbeui default or top protocol in binding list

  • Thread starter Thread starter moetdp
  • Start date Start date
M

moetdp

Q. Is there any real difference or more importantly delay if NetBEUI is
bound first over TCP/IP? I couldn't find anything on TechNet or MSDN.

When having both TCP/IP installed on a Win2000 or XP client I have always
changed the binding so that TCP/IP is the topmost protocol. It seems that
after creating an image CD set using sysprep for PCs, even if you have
TCP/IP bound at the top of the list, TCP/IP is made second in the list after
applying the image to the new PC. So, I have always manually bound TCP/IP
following the installation. Some guys at work and myself are discussing if
there is any delay in networking, especially for clients over the WAN
talking to servers on the other end.

Input appreciated.
 
Why do you need NetBEUI if you change binding order anyway? Indeed having
multiple protocols causes the delays, 'cause the clients with different
preferred protocol have always to agree about the common one before every
session.
 
We need to have Netbeui for a few offices that use legacy
programs that specifically require Netbeui. I understand
the agreement on a comon protocol, but if I have a client
using Netbeui as default in a remote location connecting
to an Exchange email server elseware, my suspician is
that the client takes at least a little time to realize
that the remote IP is not local to the physical subnet.
maybe it doesn't take any time since the subnet mask
dictates that the IP is definitely in a different range,
so there for it would go for the default gateway, and
thus need to use TCP/IP.

.........I just don't know if there is any delay at all.
We have been binding TCP/IP up on the list in
troubleshooting, because since the Win NT days we were
told to do so. Some folks on my team says it helps, and
others disagree.

Input much appreciated

-Original Message-----
 
Back
Top