I read on a tutorial that Node type=Broadcast would be the correct value for
a small LAN with no DNS and WINS server and for address resolution NetBios
over TCP/IP must be explicitly enabled when connecting to a router since
usually it is Microsoft independent. Indeed my D-Link DI-524 broadband
router asks me nothing about NetBios, so I crossed all squares for enabling
Netbios over TCP/IP on all PCs in my LAN, yet by keying ipconfig /all I
don't see Netbios being quoted in none of them and Node type looks Mixed or
Hybrid instead of Broadcast. Anyway I see that Netbios over TCP Helper
service is active on all PCs.
Any suggestions?
il barbi

In-line...

Correct.

The 'Default' setting is usually OK.
This will enable NETbios-over TCP/IP unless something else disables it.

Yes, Routers are OS-independent.

Indeed.

OK, no harm there.

Thats OK

That is not uncommon, and is not a problem.
Mixed = try broadcast, then WINS ( if confgured ).
Hybrid = try WINS ( if configured ) then broadcast.

Since no WINS is configured, either should fall back to broadcast.

You can change this by editing the registry.

The registry location is:
   HKEY_LOCAL_MACHINE
     \System
      \CurrentControlSet
       \Services
        \Netbt
         \Parameters


Delete any of the two values NodeType and DhcpNodeType if they exist,
forcing Windows to fall back to its default node type, as described below.
Reboot.

If no entry is present in the registry, then the node type will show as
'Unknown', and will default as follows:

WINS server configured: Hybrid;
No WINS server configured: broadcast.

You can also set the NodeType as follows to force it:
The possible values are:

1: Broadcast;
2: P-node ( P-to-P, or WINS-only )
4: Mixed ( Broadcast then WINS )
8: Hybrid ( WINS then broadcast )

That's OK.

No, Why?
What actual problem do you have that you think is related to NetBIOS node
type?

the problem is that I can't connect wirelessly to the router from an Acer
notebook running Windows Vista - it's a month i'm playing with
configurations and testing...
There are too many parameters to manage and I'm not a system engineer
Lastly I discovered a list of problems for the coexistence of WinXP and
Vista in a wireless network and one of these was concerned with disabling
the broadcast flag which is forced in Vista, see Windows Knowledge Base
N.928233
il barbi

Show quote

Hide quote

Lots of people who aren't systems engineers can manage the parameters, you
probably can too if you focus your self.

NetBIOS Node Type has nothing to do with WiFi connectivity.  Node Type relates
to name resolution - finding out the IP address of another computers - on LANs
with no DNS server.

Disabling the Broadcast flag is a solution for specific problems with computers
running Windows Vista.  With or without computers running Windows XP also on the
LAN.

If you've been playing with configurations for a month, maybe you don't need a
notebook computer.  What specific problems are you having?

I'm glad to hear that...:-)

I only wanted to say that I can't connect wirelessly in any way... so I just
began to read your valuable suggestions, one of which is the Broadcast flag
problem. Indeed I'm not so able to locate the level of my malfunction - I
can't even ping the router, it gives error 1231. I was able to connect the
notebook (with Broadcom board) with another notebook running XP with a
D-Link wireless board by means of an adhoc connection, so I think the
Broadcom board works (even if I see 21 parameters in advanced board
configuration...). In the contrary both wireless board can't connect to my
D-Link router, so perhaps it is the wireless side of this router that
doesn't work at low level. Do you know some tool for finding it? I include
ipconfig /all (translated from Italian):

IP Configuration of Windows
   Node type . . . . . . . . . . . . . . : Hybrid
   Routing IP enabled. . . . . . . . . : No
   Proxy WINS enabled . . . . . . . .  : No

LAN wireless board:
   Device status. . . . . . . . . . . . : disconnected
   DNS Suffix for connection:
   Description . . . . . . . . . . . . . : Broadcom network board 802.11g
   Physical address. . . . . . . . . . . : 00-19-7E-2C-C5-67
   DHCP enabled. . . . . . . . . . . . : yes
   Authomatic configuration enabled: yes

Ethernet board for connection to LAN:
   Device status. . . . . . . . . . . . : disconnected (I disconnect the
Ethernet cable when testing the wireless connection)
   DNS Suffix for connection:
   Description . . . . . . . . . . . . . : NVIDIA nForce network controller
   Physical address. . . . . . . . . . . : 00-16-D3-55-30-6C
   DHCP enabled. . . . . . . . . . . . : yes
   Authomatic configuration enabled: yes

Tunneling device for connection to LAN *:
   Device status. . . . . . . . . . . . : disconnected
   DNS Suffix for connection:
   Description . . . . . . . . . . . . . :
isatap.{CBEA9864-B603-4718-AD65-ABBB741F9225}
   Physical address. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP enabled. . . . . . . . . . . . : no
   Authomatic configuration enabled: yes

Tunneling device for connection to LAN *2:
   Device status. . . . . . . . . . . . : disconnected
   DNS Suffix for connection:
   Description . . . . . . . . . . . . . :
isatap.{ED5973AF-F337-492D-9BDD-9273F4F194FE}
   Physical address. . . . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP enabled. . . . . . . . . . . . : no
   Authomatic configuration enabled: yes
   Predefined Gateway . . . . . . . . . :
   NetBIOS over TCP/IP . . . . . . . . . . : Deactivated

Tunneling device for connection to LAN *6:
   Device status. . . . . . . . . . . . : disconnected
   DNS Suffix for connection:
   Description . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
   Physical address. . . . . . . . . . . : 02-00-54-55-4E-01
   DHCP enabled. . . . . . . . . . . . : no
   Authomatic configuration enabled: yes

Thanks for any suggestions

il barbi

Show quote

Hide quote

I'd start with the Vista pre-SP update.  WiFi is one item in the update.
<http://nitecruzr.blogspot.com/2007/10/windows-vista-is-maturing.html>
http://nitecruzr.blogspot.com/2007/10/windows-vista-is-maturing.html

And maybe we should review the WiFi connectivity process.
1) The WiFi client connects to the radio on the WiFi access point (router).
2) The WiFi client authenticates to the access point.
3) The DHCP client requests settings from the DHCP server on the router.
4) The IP stack on the laptop establishes connectivity with the router, and with
the LAN and WAN.

Next, what WiFi client are you using?  If not Microsoft client, make sure that
it's certified for Vista, and that you have the most current release.
<http://nitecruzr.blogspot.com/2005/08/driver-updates-from-microsoft-please.html>
http://nitecruzr.blogspot.com/2005/08/driver-updates-from-microsoft-please.html

And make sure that you're running only 1 WiFi client.
<http://nitecruzr.blogspot.com/2006/01/stabilise-your-wifi-use-only-one-wifi.html>
http://nitecruzr.blogspot.com/2006/01/stabilise-your-wifi-use-only-one-wifi.html

Did you check the access logs on the router, to see if there's any diagnostics
about failure by the laptop?  Or does the log maybe imply that the laptop is
connecting (step 2)?
<http://nitecruzr.blogspot.com/2005/05/dealing-with-physical-network-problems.html>
http://nitecruzr.blogspot.com/2005/05/dealing-with-physical-network-problems.html

Check the other known Vista connectivity issues.
<http://nitecruzr.blogspot.com/2006/12/windows-xp-and-vista-on-lan-together.html#Connectivity>
http://nitecruzr.blogspot.com/2006/12/windows-xp-and-vista-on-lan-together.html#Connectivity

Then, check for LSP / Winsock corruption, which will cause DHCP client problems,
and the "Disconnected" notation in the ipconfig log.
<http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html>
http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html

unfortunately when trying to install KB938979 and KB941649 it says they are
not applicable to my system...

how can I determine at what point the process breaks?

I'm using Microsoft Wifi client (Wlansvc) and it is the only one

The log on the router says 0 packets received, some thousand  transmitted...
ping error is 1231

this is the Broadcast flag problem, but I've checked with PStools Broadstat
command and leaved only one Master browser

from the text it seems they are only Internet problems
Perhaps some trace utility showing data exchange at lowest level possible
between router and Vista would be useful?

il barbi

How do I disconnect from a network share?
Easy fix, when you know how
Can't connect from notebook to router
cant connect to Localhost
Newbie - heip accessing files on network