dslreports logo

Well, some of what it did anyway.

NetTrans/000n folder education, 101.


This can get rid of all the "shotgun," bogus entries that these patches give you. In other words, goo. Having extra NetTrans folders is pointless, and it may even have a negative effect somewhere.

If you have a sniffer program, that adds several, and analyzer programs add some. VPN gives you at least one (depends on bindings). Then you get one .../000n key for each Protocol-Adapter pair that you have. TCP/IP > Dial-up is one. TCP/IP > every NIC you have is one each. NetBEUI, IPX/SPX or any other Protocol will add one for EACH Adapter to which they are bound. Get the idea? They come from a lot of places.

Well, let us see exactly what they are on your system. This analysis is exactly the same one I use to figure out which entries are not needed (i.e., which extraneous ones were added by SpeedGuide, etc).
~~~~~~~~~~~~~~~~~

First off, how many entries do you have in the Dr.TCP Adapter drop-down list? Temporarily change each one of those to their own unique number -- 111, 222, 333 or whatever you like. Apply and close Dr.TCP. You do not have to reboot yet!

Open regedit (go to Start/Run, and type in "regedit" (no quotes), and by looking for your unique MaxMTU numbers, find out which 000n key belongs to which Adapter -- write this down. Some 000n keys will obviously NOT be for TCP/IP. If an entry *is* for TCP/IP, you will find at least these two entries in the main .../000n key:

DriverDesc. "TCP/IP"
MaxMTU "1500"

While you are in the registry, you will want to modify the "Help Text" line in *each* of these keys:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
\Class\NetTrans\00nn\Ndi [where nn is a number]

For example, the Help Text line for a TCP key looks like this:
"TCP/IP is the protocol you use to connect to the Internet and wide-area networks."

If you can't tell what adapter a certain 000n entry belongs to, modify the line to look like this:
"(NetTrans 0001) TCP/IP is the protocol you use to connect to the Internet and wide-area networks."

If you can tell by the unique Dr.TCP number that a given 000n entry belongs to a specific adapter, modify the line to instead look something like this:
"(NetTrans 0002 : Linksys Etherfast NIC) TCP/IP is the protocol you use to connect to the Internet and wide-area networks."

Regardless of what the key is for (TCP/IP, NetBEUI, etc), modify the Help Text line in some unique way to clearly identify the .../000n key to which it belongs.

Close regedit, reset the MaxMTU settings in Dr.TCP to their correct numbers and reboot.

Now go to Control Panel | Network. Find the Protocol-Adapter pairs you have listed. Select each one sequentially and note the box at the bottom that says "Description." Magically, you will be able to tell exactly which NetTrans key belongs to which Protocol-Adapter pair.

This should clearly identify which NetTrans keys are being used and what is using each of them. Additionally, by their absence, it tells you which ones are "dead weight." If you desire, backup this section of the registry (Export>) and jettison the dead weight. Voila!

From R2 a while back.


Expand got feedback?

by Pinan See Profile edited by JMGullett See Profile
last modified: 2007-02-28 14:11:14