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
"il barbi" <angeieri.barboggi@ngi.it> wrote in message
news:OJAyEhTMIHA.5988@TK2MSFTNGP02.phx.gbl...
>I read on a tutorial that Node type=Broadcast would be the correct value
>for
> a small LAN with no DNS and WINS server
Correct.
> and for address resolution NetBios
> over TCP/IP must be explicitly enabled
The 'Default' setting is usually OK.
This will enable NETbios-over TCP/IP unless something else disables it.
> when connecting to a router since
> usually it is Microsoft independent.
Yes, Routers are OS-independent.
> Indeed my D-Link DI-524 broadband
> router asks me nothing about NetBios,
Indeed.
> so I crossed all squares for enabling
> Netbios over TCP/IP on all PCs in my LAN,
OK, no harm there.
> yet by keying ipconfig /all I
> don't see Netbios being quoted in none of them
Thats OK
> and Node type looks Mixed or
> Hybrid instead of Broadcast.
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 )
> Anyway I see that Netbios over TCP Helper
> service is active on all PCs.
That's OK.
> Any suggestions?
No, Why?
What actual problem do you have that you think is related to NetBIOS node
type?
"Ron Lowe" <ronATlowe-famlyDOTmeDOTukSPURIOUS> ha scritto nel messaggio
news:uNLqYGUMIHA.3516@TK2MSFTNGP02.phx.gbl...
>
>cut<
>
> That's OK.
>
>> Any suggestions?
>
> 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
On Wed, 28 Nov 2007 00:33:01 +0100, "il barbi" <angeieri.barboggi@ngi.it> wrote:
>"Ron Lowe" <ronATlowe-famlyDOTmeDOTukSPURIOUS> ha scritto nel messaggio
>news:uNLqYGUMIHA.3516@TK2MSFTNGP02.phx.gbl...
>>
>>cut<
>>
>> That's OK.
>>
>>> Any suggestions?
>>
>> 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
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?
--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking] http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
"Chuck [MVP]" <none@example.net> ha scritto nel messaggio
news:if7rk3p49q4no0n2gisbuob3a9fl3j5gg6@4ax.com...
>
> Lots of people who aren't systems engineers can manage the parameters, you
> probably can too if you focus your self.
>
I'm glad to hear that...:-)
>
> 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 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
On Wed, 28 Nov 2007 19:10:38 +0100, "il barbi" <angeieri.barboggi@ngi.it> wrote:
>"Chuck [MVP]" <none@example.net> ha scritto nel messaggio
>news:if7rk3p49q4no0n2gisbuob3a9fl3j5gg6@4ax.com.. .
>>
>> Lots of people who aren't systems engineers can manage the parameters, you
>> probably can too if you focus your self.
>>
>I'm glad to hear that...:-)
>
>>
>> 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 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?
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/0...ft-please.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/0...-problems.html
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/0...-layer-in.html
--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking] http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
"Chuck [MVP]" <none@example.net> ha scritto nel messaggio
news:fbpsk3tfjh9o5npqjp9u7egj1svnbvlrj5@4ax.com...
>
> 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/1...-maturing.html
>
unfortunately when trying to install KB938979 and KB941649 it says they are
not applicable to my system...
> 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.
>
how can I determine at what point the process breaks?
> 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.
>
I'm using Microsoft Wifi client (Wlansvc) and it is the only one
> 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)?
>
The log on the router says 0 packets received, some thousand transmitted...
ping error is 1231
> Check the other known Vista connectivity issues.
>
this is the Broadcast flag problem, but I've checked with PStools Broadstat
command and leaved only one Master browser
> Then, check for LSP / Winsock corruption, which will cause DHCP client
> problems,
> and the "Disconnected" notation in the ipconfig log.
>
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?
On Thu, 29 Nov 2007 19:52:05 +0100, "il barbi" <angeieri.barboggi@ngi.it> wrote:
>"Chuck [MVP]" <none@example.net> ha scritto nel messaggio
>news:fbpsk3tfjh9o5npqjp9u7egj1svnbvlrj5@4ax.com.. .
>>
>> 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/1...-maturing.html
>>
>unfortunately when trying to install KB938979 and KB941649 it says they are
>not applicable to my system...
>
>> 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.
>>
>how can I determine at what point the process breaks?
>
>> 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.
>>
>I'm using Microsoft Wifi client (Wlansvc) and it is the only one
>
>> 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)?
>>
>The log on the router says 0 packets received, some thousand transmitted...
>ping error is 1231
>
>> Check the other known Vista connectivity issues.
>>
>this is the Broadcast flag problem, but I've checked with PStools Broadstat
>command and leaved only one Master browser
>
>> Then, check for LSP / Winsock corruption, which will cause DHCP client
>> problems,
>> and the "Disconnected" notation in the ipconfig log.
>>
>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
LSP / Winsock problems can affect different portions of the network, with
astounding unpredictability.
The DI-524 has a WLAN activity light. Make sure that no other computer is
connected, try to connect, and watch the WLAN light while you do. Then check
the activity log, and see exactly is listed for the time period when you tried.
Look at page 36 of the manual, for viewing the router log.
--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking] http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
"Chuck [MVP]" <none@example.net> ha scritto nel messaggio
newse5vk318kosun9gcb4p720q5qkahs03it3@4ax.com...
>
> LSP / Winsock problems can affect different portions of the network, with
> astounding unpredictability.
>
I checked but LSPfix etc. seem not to be applicable to Vista
> The DI-524 has a WLAN activity light. Make sure that no other computer is
> connected, try to connect, and watch the WLAN light while you do. Then
> check
> the activity log, and see exactly is listed for the time period when you
> tried.
>
the WLAN light stays on and seldom blinks - I think this in accord to the
statistics at router side showing always 0 packets received and some
hundreds transmitted. Unfortunately when I try to ping the router from Vista
and Vista from the router (testing with fixed IP addresses) the log file is
not able to register anything...
Now I think that the router must receive at least some packet from Vista -
not receiving anything sounds to me a very low level problem. Perhaps it
would be useful to see what is the router transmitting but I'm not able to
find trace programs supporting wireless connections. Anyway the Broadcom NIC
works since the loopback test (ping 127.0.0.1) works and I succeeded in
connecting the Vista PC with another XP PC by means of an adhoc connection
I'm afraid there are matching problems between the Broadcom NIC and the
router, for instance there are just 21 parameters in Broadcom NIC
configuration (I don't understand their meaning since they all involve radio
knowhow)
il barbi
On Fri, 30 Nov 2007 22:00:55 +0100, "il barbi" <angeieri.barboggi@ngi.it> wrote:
>"Chuck [MVP]" <none@example.net> ha scritto nel messaggio
>newse5vk318kosun9gcb4p720q5qkahs03it3@4ax.com.. .
>>
>> LSP / Winsock problems can affect different portions of the network, with
>> astounding unpredictability.
>>
>
>I checked but LSPfix etc. seem not to be applicable to Vista
>
>> The DI-524 has a WLAN activity light. Make sure that no other computer is
>> connected, try to connect, and watch the WLAN light while you do. Then
>> check
>> the activity log, and see exactly is listed for the time period when you
>> tried.
>>
>the WLAN light stays on and seldom blinks - I think this in accord to the
>statistics at router side showing always 0 packets received and some
>hundreds transmitted. Unfortunately when I try to ping the router from Vista
>and Vista from the router (testing with fixed IP addresses) the log file is
>not able to register anything...
>Now I think that the router must receive at least some packet from Vista -
>not receiving anything sounds to me a very low level problem. Perhaps it
>would be useful to see what is the router transmitting but I'm not able to
>find trace programs supporting wireless connections. Anyway the Broadcom NIC
>works since the loopback test (ping 127.0.0.1) works and I succeeded in
>connecting the Vista PC with another XP PC by means of an adhoc connection
>I'm afraid there are matching problems between the Broadcom NIC and the
>router, for instance there are just 21 parameters in Broadcom NIC
>configuration (I don't understand their meaning since they all involve radio
>knowhow)
>il barbi
As I mentioned, Page 36 of the manual seems to indicate that the router has a
decently detailed log, hat should provide more detail than you're described so
far. Did you check the log, after trying to connect, and look at the entries in
there?
--
Cheers,
Chuck, MS-MVP 2005-2007 [Windows - Networking] http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
Netbios over TCP/IP 
e5vk318kosun9gcb4p720q5qkahs03it3@4ax.com...
Linear Mode
