[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 767
  • Last Modified:

SBS 2003 - NetBios name of Server not showing up in My Network Places

We implemented a new Small Business Server 2003 on a 15 workstation network.  Everything was working fine for about two weeks, when all of the sudden the NetBios name of the server stopped showing up in the directory.  I.e. when you go to My Network Places (from the workstation or the server itself) and look at the domain, all workstations show up, but the server does not.  The server was showing up for those two weeks.

The server can be accessed normally in all aspects.  What I mean is, if I go to a client and type \\servername, etc, then I can access all resources.

Also, we cannot pinpoint any changes that were made to the server that could have killed this.

Other possibly pertinent information...
The server runs RAS.
On ipconfig /all, the node type is unknown.
In the registry, the EnableProxy value is 2.

An article on Msft's KB stated to go to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters\
I set the EnableProxy value to either 0 or 1, but whenever I reboot the server to make this fix, it automatically defaults back to 2.

Normally, I would probably just live with this problem and go on, but the client would like to be able to see the NetBios name.

I'm at a loss here.  I appreciate any help that anybody could give me.  Please let me know if you need more information.

  • 2
1 Solution
When I had this it turned out to be the enableproxy key.

Some of the other things to check are whether you have WINS, WINS on a dual homed server is supposed to be trouble, but you usually get away with it. Is Netbios over tcp/ip enabled on the LAN? Disabled on the Wan? Um...

here's the post MS PSS sent me when we worked this out - as I said, it turned out to be the node type, and it's been good since...

A) Firstly on the Server I need you to unbind the Browser Service from the External WAN NIC. We need to do this in 2 ways by using both the GUI and Regedt32. Note you must use Regedt32 and not Regedit

1) Right-click My Network Places, and then click Properties.
2) Right-click the external network adapter's Local Area Connection icon, and then click Properties . NOTE : VPN, RRAS, and RAS can also create a second network adapter to create the browsing issue.

3) Click Internet Protocl (TCP/IP) , and then click Properties .
4) Click Advanced .
5) Click the WINS tab.
6) Click Disable NetBIOS over TCP/IP.
7) Click OK , click OK , and then click OK .

If you see more than 1 device listed here you need to unbind it. This can be caused for example by Routing and Remote Access or the WAN card in the server.

The browsing role can be disabled on an adapter basis using the registry key


Data type: REG_MULTI_SZ
Value: UnboundBindings
String Value: NetBT_Tcpip_{BF3415B3-336D-42BE-B0DC-2768DCB70803}

If you have more than two network adapters in a multihomed Windows based server, enter each driver instance that you wish to disable on a separate line in the multi string field.

You need to enter the value for your WAN adapter which is reported by NetDiag as:


and any other values which are reported by BROWSTAT DUMPNET.

Reboot the Server after changing the above settings and test with BROWSTAT DUMPNET. You should see only:


List of transports currently bound to the browser

     1 \Device\NetBT_Tcpip_{9475C313-0F95-4303-9FDF-AED008AB213F}

If you do not see exactly the above please let me know as soon as you can


B) Your Server has this issue which may be causing your problem. When you use the Ipconfig.exe utility with the /all switch that shows the TCP/IP configurations on your computer, the node type may appear as "unknown"

B-1 To resolve this issue, use Registry Editor (Regedit.exe) to locate the following key in the registry:


Change the value of the EnableProxy value in the preceding registry key to 0, quit Registry Editor, and then restart your server.

References "Ipconfig /All" Command Shows the Node Type as Unknown (310570)"
"TCP/IP and NBT Configuration Parameters for Windows 2000 or Windows NT (120642)"


C) What methods NetBT will use to register and resolve names

Description: This parameter determines what methods NetBT will use to register and resolve names. A B-node system uses broadcasts. A P-node system uses only point- to-point name queries to a name server (WINS). An M-node system broadcasts first, then queries the name server. An H-node system queries the name server first, then broadcasts. Resolution via LMHOSTS and/or DNS, if enabled, will follow the these methods. If this key is present it will override the DhcpNodeType key. If neither key is present, the system defaults to Bnode if there are no WINS servers configured for the network. The system defaults to Hnode if there is at least one WINS server configured.

Windows 2000 and Windows NT

Value Type: REG_DWORD - Number
Value Name: NodeType
Value: 8

Reference " Default Node Type for Microsoft Clients (160177)"
"TCP/IP and NBT Configuration Parameters for Windows 2000 or Windows NT (120642)"

Please let me know how these go for you.
s1162282Author Commented:
Sorry that it took me so long to get back to this.  I've been very busy, but now I'm ready to get the problem resolved.

harleyjd, thank you very much for your suggestions, however, none of them solved the problem.  To comment...

The server is running WINS, however it is not a dual homed server.  We are only using one NIC in the server.  NetBios ofver Tcp/ip is enabled on the NIC.

I wish that some of the fixes that you had posted had helped, but I'm still stuck in the water.  Got any other ideas?  Thanks.

s1162282Author Commented:
Problem still not solved, but I will give harleyjd the credit since he helped the most.  Thanks.

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now