Change Protocol Bindings in adapters and bindings

Hey guys,

At our hospital, we have approx 1000 PCs mostly running windows xp. We run IPX and TCP. Today corporate wants us to go into network connections < advanced < advanced settings < and change the protocol order. For instance, under File and Printer sharing for Microsoft Networks, we have Novel IPX first and Internet Protocol TCP/IP second. We need to change the order to specify Internet protocol first.  We do the same thing for Client for Microsoft networks.
Now, the process is pretty easy, but it will be really tedious to walk around and do it on 1000 PCs.
The reason we are doing this is an upgrade to a new software program will not work correctly if the pcs are set to ipx first in the binding.
My question is, does anyone have a better solution? Maybe someone knows how to do it in the registry and we can just run a script? Any ideas will definitely be helpful. Thanks in advance, guys!
typertecAsked:
Who is Participating?
 
scrathcyboyCommented:
First, a "script" for the registry is nothing more than a statement as to "how you want it".  So the second post IS **IS** the script to set the registry right.  But if these keys don't do it, then I cant find which one is the right one, as that would appear to be it, but if it is not, then this is the only thing to do --

1) open regedit, click on the highest name in the tree, choose above -- export registry, pick ALL !!
name the file and export all 20 MB of it.
2) now change the order to the wrong order (I assume you have it in the right order already.).  Shut down and reboot (saves the registry) then go back into regedit, make sure the order is changed, now click on the top of regedit again, and choose - export registry -- pick ALL !!

Now do a file compare on the two registries (text files) using any free file compare utility (get on google).  There will be only one significant change of keys (a reboot always changes some stuff, not relevant.).

Once you figure out the right key, post back here, and then it is easy to make a REG file out of it --

1) It is a text file
2) it start with [regedit4]
3) the next lines are the way you want the registry to become, that is all there is to it.
4)  So export just the key that changed to a TXT file, then add it to your REG file, and you are done.
0
 
scrathcyboyCommented:
Here is Ms way to do it, as usual, fiddle with the system one by one, no concept of efficiency -
http://support.microsoft.com/kb/894564/en-us
But here is a better article pointing you in the right direction -
http://support.microsoft.com/?kbid=163576

The key is this registry key -

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider.
For example, the following entry establishes SPX, TCP/IP, and NetBIOS connections in the order indicated:
RPC_Binding_Order=ncacn_spx,ncacn_ip_tcp,netbios
That may only be for exchange, the article is not specific as to general networking or not. so ....

Look at what order you have under that key on a FIXED SYSTEM, not an unfixed one, and copy it to a text file, so say you want this (this is just an example)--

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider\RPC_Binding_Order=ncacn_ipx,ncacn_ip_tcp,netbios
then you just put [REGEDIT4] in front of that key on a new line, save it to a file called fixb-ord.reg and then you can push it out to the network clients, but !!
MAKE CERTAIN TO TEST THAT IT DOES WHAT YOU WANT BEFORE YOU DEPLOY IT !!!!


The key I found on my system was --
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\DCOM Protocols\
and the order was -
ncacn_ip_tcp
ncacn_spx
ncacn_nb_nb
ncacn_nb_ipx

Now see my next post for the full regedit file to create to match mine -

0
 
scrathcyboyCommented:
[REGEDIT4]
Key Name:          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc
Class Name:        <NO CLASS>
Last Write Time:   4/19/2006 - 9:07 AM
Value 0
  Name:            DCOM Protocols
  Type:            REG_MULTI_SZ
  Data:            ncacn_ip_tcp
                   ncacn_spx
                   ncacn_nb_nb
                   ncacn_nb_ipx

Value 1
  Name:            UuidSequenceNumber
  Type:            REG_DWORD
  Data:            0x2de6162


Key Name:          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\ClientProtocols
Class Name:        <NO CLASS>
Last Write Time:   1/25/2005 - 10:54 PM
Value 0
  Name:            ncacn_np
  Type:            REG_SZ
  Data:            rpcrt4.dll

Value 1
  Name:            ncacn_ip_tcp
  Type:            REG_SZ
  Data:            rpcrt4.dll

Value 2
  Name:            ncadg_ip_udp
  Type:            REG_SZ
  Data:            rpcrt4.dll

Value 3
  Name:            ncacn_http
  Type:            REG_SZ
  Data:            rpcrt4.dll


Key Name:          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\NameService
Class Name:        <NO CLASS>
Last Write Time:   1/25/2005 - 3:46 PM
Value 0
  Name:            DefaultSyntax
  Type:            REG_SZ
  Data:            3

Value 1
  Name:            Endpoint
  Type:            REG_SZ
  Data:            \pipe\locator

Value 2
  Name:            NetworkAddress
  Type:            REG_SZ
  Data:            \\.

Value 3
  Name:            Protocol
  Type:            REG_SZ
  Data:            ncacn_np

Value 4
  Name:            ServerNetworkAddress
  Type:            REG_SZ
  Data:            \\.


Key Name:          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\NetBios
Class Name:        <NO CLASS>
Last Write Time:   1/25/2005 - 3:46 PM

Key Name:          HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\SecurityService
Class Name:        <NO CLASS>
Last Write Time:   1/25/2005 - 10:54 PM
Value 0
  Name:            9
  Type:            REG_SZ
  Data:            secur32.dll

Value 1
  Name:            10
  Type:            REG_SZ
  Data:            secur32.dll

Value 2
  Name:            14
  Type:            REG_SZ
  Data:            schannel.dll

Value 3
  Name:            16
  Type:            REG_SZ
  Data:            secur32.dll

Value 4
  Name:            1
  Type:            REG_SZ
  Data:            secur32.dll

Value 5
  Name:            18
  Type:            REG_SZ
  Data:            secur32.dll

Value 6
  Name:            68
  Type:            REG_SZ
  Data:            netlogon.dll

-----------------------------------
end of file

So you could try that and call it fixb-order.reg, and MAKE SURE YOU TEST IT FIRST !!!!!
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

 
typertecAuthor Commented:
Thanks for the quick reply, scrathcyboy . I'll test this when I get home from work and give you guys an update tonight.
0
 
typertecAuthor Commented:
Hey Scrathcyboy,

I'm not sure what exactly your second post means. I'm not an expert with registry settings. Your 2nd post appears to be the same as what I currently see on my registry. Basically, I'm looking for a way to change the protocol bindings order through the registry so that I can make a script out of it. I went into the registry < rpc < dcom protcols < and changed the order to specify IP first and it still doesnt change it. any ideas?
0
 
typertecAuthor Commented:
Hey Scrathcyboy. I'm still working on the issue, but you pointed me in the right direction. I'm not sure you can even change the binding orders just by making a registry change. I have tried a registry compare but still can't seem to get it to work. Have you? well, thanks for the help!
0
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.

All Courses

From novice to tech pro — start learning today.