**(EDITED)- Name Resolution not Network Priorities

[Deslok]

If a network uses netbui, tcp/ip, ipx/sx, etc
I thought there was some way (possibly in the registry)
to specify which protocol had top priority?
I know there is a key:
HKLM\current control set\services\vxd\nettran\something (I may be a bit off here)
where these protocols are specified.

So, is there a way to do this?
I think I read it somewhere just do not remember.

 

[IsOs]

In Windows NT4, Network Properties, Binding - you can move them up or down.

 

[Cnuke]

What os???

 

[Cnuke]

What os???

 

[spidey07]

Or get rid of those unwanted protcols (IPX, netbios)

You can move the binding orders up or down, but you have more pressing problems if you have to run all three protocols on the same box.

 

[LadyDi]

Does simply changing the order change the priority??

 

[spidey07]

DI, YES.

If you have your bindings in the following order

1) IP
2) IPX
3) Netbios

The the workstation service will try to locate a resource via IP, if this times out or cannot "find" a server or resource the WKS service will then attempt IPX, then Netbios.

The problem lies with the fact that each protocol has its own timeout settings. If you are trying to reach a server that is only running netbios it coule take you 3 minutes to reach it.

Bottom line - RUN A SINGLE PROTOCOL ON YOUR ENTIRE NETWORK (IP). If you must run another make sure you can truly convince yourself that it is necessary and can't be changed. I don't know of an operating system that doesn't support IP. Maybe Apple, they do support IP but still rely somewhat on appletalk to locate IP addresses/names.

hope this helps!

 

[Workin']

<< Maybe Apple, they do support IP but still rely somewhat on appletalk to locate IP addresses/names. >>

Off-topic a little but Apple supports IP even way back in OS 7.3, circa 1994, maybe even earlier. No AppleTalk necessary.

 

[Deslok]

ok,
I was a bit wrong - not network priorities but Name Resolution.
OS is nt4 and 2000 pro.