Recommended Posts

just a "net view" is looking at the browse list, not doing a broadcast for the name.. The browse list has nothing to do with how the machine name is resolved.

I'm not interested in the netbios cache of chef, but that of a client trying to access chef. As to the firewall -- your not running any other firewall/security software -- lots of antivirus software now a days is more like a firewall, and can cause you all kinds of grief if not configured correctly.

As to how to view your node type.. I posted a screen shot of mine showing "Peer-to-Peer" What part of the ipconfig /all did you miss??? ;)

Can you give me remote access to both of these machines? Using teamviewer for example -- I would really love to take a look myself.

Nothing to install on your end.. Just run the customer module, and PM me the info it numbers and password it gives you.

edit: Unless your on a managed switch that would allow you to disable broadcast, hmmm can you verify your netmasks of your machines.. Its possible you have say a 16bit mask on the other machines, and 24 bit on your home machines? Or vice versa, etc. ---> so the broadcast addresses would be different, and your home machines would not answer a broadcast for their name.

edit2: just duplicated your problem with a mismatched netmask. As you can see the vista machine can not net view the machine by name \\p4-24g, but can by ip \\192.168.1.100

The issue here is the netmask is wrong on the vista box.. He would still be able to get on the network, ie access the internet, etc.. but his broadcast address would not be right - and therefore would not be able to resolve netbios with broadcasting to machines on the 192.168.1.x/24 network "255.255.255.0", but would be able to resolve machines using the same netmask.

post-14624-1211162255_thumb.jpg

Verify that both the xp home boxes and the machines your trying to access them with are using the same netmask.

Edited by BudMan

the node type is PEER-to-PEER

you would go crazy trying to remote in... i do it to fix problems while away (but our linkn to the outside is satellite internet, SUPER delays.. would drive you MAD!)

like i said, all the computers on our system are 255.255.255.0, all

and all are 192.168.1.X (i have triple checked)

i ran ipconig /all on the family xp home machine.. nothing stood out but the connection type, was peer to peer, my vista machine is MIXED

i looked at the other systems node types (they are all connecting via host name just fine)

i found hybrid, mixed, and unknown... the xp homes are peer to peer

hope this helps

let me know what other steps you want me to take...

pj

ALSO: the one home system is on the same router/switch as me... the other is on another UNmanaged switch...

so, nothing to flag a switch as being the problem...

And WTF would you be running in that mode for???

"the node type is PEER-to-PEER" When you clearly stated..

"wins is not enabled, netbios is"

Without a wins server P-node is not going to work!!

http://technet.microsoft.com/en-us/library/bb727013.aspx

Chapter 11 - NetBIOS over TCP/IP

P-node (peer-peer)

Uses an NBNS such as WINS to resolve NetBIOS names. P-node does not use broadcasts but queries the NBNS directly. Because broadcasts are not used, NetBIOS resources located on remote subnets can be resolved. However, if the NBNS becomes unavailable, NetBIOS name resolution fails for all NetBIOS names, even for NetBIOS applications that are located on the local subnet.

this is the First example I gave in duplication of your problem -- I setup my client as P-node, without a wins server - and could not resolve the hosts!!

Change your node type to broadcast, which is the default node type. This is setup on your dhcp server with option 46, b-node would be 0x1, or can be setup on the client in the registry..

Your node type needs to be broadcast if your not going to be running a wins server!!

budman, chill

im trying my best man.. thats why i am here, on the forum, looking for help

the other XP home machine is on hybrid (along with the office and POS ) and that is also having problems.. so i think this peer is only tip of the iceburg

can you please walk me though, slowly, on how to change the NODE of the chef computer

i have checked all settings under the network, and these are the same as everyone one else's.. i just fine it EXTREEEEEMLY oddd, that they both, happen, to be, XP HOME MACHINES...

kinda odd huh? hmm....

i have set all machines up, why oh why would i have happened to change the P node system file wins server crap on just these two... very funny coincidence if i did

pj

the XP home machine node type does not matter for trying to resolve the home machine! The machine wanting to resolve the xp home machine matters.

if your node type is P-node on this machine, then it will ONLY ask a wins server for the names of machines, it will NOT broadcast for it.. So it will never find \\chef

How chef resolves machines its wanting to access is besides the point.

If your machines are dhcp -- then check that dhcp server option 46 is set for b-node.

As to how to set it in the registry..

http://support.microsoft.com/kb/903267

You cannot view other workgroup computers on the network on a Windows XP-based computer

CAUSE

This issue may occur if the computer is configured to use p-node mode for name resolution. To determine whether a computer is configured to use p-node mode, follow these steps:

1. Click Start, click Run, type cmd, and then click OK.

2. At the command prompt, type ipconfig /all, and then press ENTER.

View the Node Type section at the start of the output. If the value that appears on the screen is Peer-Peer, the computer is running in p-node mode.

In p-node mode, the computer uses only point-to-point name queries to a Windows Internet Name Service (WINS) server. However, the WINS server is not available for NetBIOS name resolution on a peer-to-peer network.

To resolve this issue, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.

2. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NetBt\Parameters

3. In the right pane of Registry Editor, delete the following values if they are present:

• NodeType

• DhcpNodeType

Note If the NodeType value is present, this value will override the DhcpNodeType value. If neither subkey is present and if no WINS servers are configured for the client, the computer uses b-node mode. If at least one WINS server is configured, the computer uses h-node mode.

4. Quit Registry Editor.

5. Restart the computer.

6. Try to view workgroup computers on the network again.

edit: BTW I would not find anything on your network odd or strange. It seems to be SO JACKED UP, your on here like every single day it seems like with a new issue.. ;)

edit2: BTW I would not delete both option.. since this will most likely give you an unknown in ipconfig /all -- If your dhcp server supports setting it.. Do that! Are you running dhcp on windows server? If your dhcp server does not support it, then leave the node type in the registry set for b-node.

Atleast this way when you look at ipconfig /all it will show you what node type your using - vs unknown.

fist off, howcome i cannot access the xp home by host name on ANY of the computers on the network.. i can ping my laptop from ANY of the other systems, even the xp home machines.. but the opposite is not true... so, its not just my system, or 1 other, but 7 others, are unable to ping or call the two xp home machines by HOST name

---

• NodeType

• DhcpNodeType

neither one was found...

--

odd or jacked up? i have problems, that need answers.. i have a lot of computers.. why are you on here.. i want help from helpful people.. if you see its a post from pj, ignore it than..

---

Edited by pjrey

Arggh dude -- What can I say your network is JACKED!!! it not rocket science -- its a simple broadcast for names.. I have pointed out how netbios name resolution works.. READ IT!!

But what I can tell you for sure is -- if you have a client set for P-node, and there is not a wins server -- it will NOT BROADCAST for names - PERIOD!!

So if on your network the only way to resolve a machine netbios name is with broadcast, you will not find this machine!

edit: Neither one was found on what machine???? You clearly stated a machine was in P-node!! Which machine is that???

As to needing answers -- I agree you need them!! I have given you ALL the info you need to correct your name resolution issue. I would even be happy to do it for you.. If you would give me remote access.

edit2: ping can be a dns look up.. As you see when I ping a machine, it could use dns to resolve it - not broadcast.

C:\>ping kidsdell

Pinging KIDSDELL.local.lan [192.168.1.101] with 32 bytes of data:

Reply from 192.168.1.101: bytes=32 time<1ms TTL=128

How is it machines would get set to P-node if you did not set it by hand or with a dhcp server? I would double check that all the machines are using the correct method of resolving netbios for how you want to run your network.. Be it broadcast, be it wins, be it lmhosts file, etc.. READ THE DOCUMENT I LINKED TOO!!

Edited by BudMan

keep writing the same thing over and over

im saying, i have tried everything you have told me to do.. dont get mad because it didnt work...

my network is not jacked...

everything is working perfectly fine.. except for not being able to call two systems by host name... hmmm

if that is jacked... wow...

p

  pjrey said:
keep writing the same thing over and over

im saying, i have tried everything you have told me to do.. dont get mad because it didnt work...

my network is not jacked...

everything is working perfectly fine.. except for not being able to call two systems by host name... hmmm

if that is jacked... wow...

p

Nice way to say thanks. :rolleyes:

It's not his fault your network doesn't function correctly. He's only trying to help you fix it.

:rofl: Your nework is not working fine.. You STATE you have machines set to use P-Node, which you have not a clue how they got set.. And your not runnings wins.. So why would they be set to use p-node????

Post the output from ipconfig /all of a machine that you want to resolve \\chef from. And post the output of chef's ipconfig /all

Well as I already said, if you remove the dhcpnodetype and nodetype reg entries it will show unknown.

Now your vista is showing Mixed, which is broadcast and then wins.

Where did it get that mode from??? That is for sure not the default type.. So either you set it, or your dhcp server is handing it out? This makes no sense --- and clearly only confuses the issue if you have clients setup like this, without fully understanding why you would set that up... There would be no point of setting that up, unless you had a wins server running for starters.

Also are you not showing all the network interfaces?, chef shows adapter #2 Also you have a search order set, so your machines will add pjrey.com to all dns queries -- Do you have DNS entries for these hosts? Are you running AD? This domain resolves to a public IP, with nameservers NS7 and NS8.JIFFYNET.NET --- so why would you have machines with private addresses searching for hosts on this domain in their search list? That is utterly pointless and only degrades your local name resolution!

Also these xp home machines are wireless, and your clients are wired? I recall you having a higherend router.. Is this also the wireless, or is there an accesspoint? Its possible with wireless to wired network that the broadcast over the wireless is blocked?, or its possible your getting a broadcast timeout, etc. Is there some device doing a bridge between your wired and wireless networks? What wireless security are you running? Its possible you have a groupkey issue, broadcast and multicast traffic is different over wireless -- it uses the groupkey.

To troubleshoot your name resolution problem -- really need to FULLY understand your network, seems clear you have a search order setup for name resolution.. Why I have no idea, but this can throw a wrench into for sure.

What is the output of nbtstat -n from the chef machine? It's possible your netbios name does not match its dns name, etc. Would be very strange --- but not out of the ?, etc.

Also your not running any other type of protocols are you? IPX, Netbeui, etc.

I would suggest you put the chef box on the wire with your other machines, vs being wireless -- does \\chef work then?

ill try hardwiring in the xp home chef (but the thing is, the other xp home machine is hardwired, and directly into the fvx538 router... no switches or access points.. and i am undable to get the host of that machine like i stated before...

the chef (xp home) is routed bythe same router as well, of course (fvx538) over two unmanaged switches....

the nbtstat -n from chef is:

CHEF 00 UNIQUE REGISTERED

CHEF 20 UNIQUE REGISTERED

WORKGROUP 00 GROUP REGISTERED

WORKGROUP 1E GROUP REGISTERED

i have no other protocols running on the xp home machine, i have running: client for micro, file share, and internet protocol tcp/ip

thats it...

i told you that there were no entries for dhcpnodetype and nodetype in the REG, i dont know how i got the MODE, i dont know how to even change the mode....

i have setup all systems the same...

one odd thing i found, when i tried to run nbtstat n under cooks/chef it said it could not load nbtstat

i had to log into my account (admin) then i could run it, maybe that is normal...

pj

What about other protocols on the machines trying to resolve. If you have a hardwired xp home machine that is doing the same thing.. lets use that one as the troubleshooting box -- vs one that has more variables.

As to changing the mode -- I have pointed out multiple references that go over this, how Netbios name resolution works etc -- have you bothered to read any of it???? The node type is set either by the dhcp server option 46, or by nodetype HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NetBt\Parameters

NodeType

Key: Netbt\Parameters

Value Type: REG_DWORD - Number

Valid Range: 1,2,4,8 (B-node, P-node, M-node, H-node)

Default: 1 or 8 based on the WINS server configuration

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

what about the nonsense search order pjrey.com??? Why do you have a search list setup, without local DNS???

If the account is not ADMIN, then no it would not be able to do admin functions.

Question you have multiple downstream switches.. Plug one of the machines that will not resolve into the same dumb switch of a client that can not resolve it by name.. Does it work then?

You have too many variables! You do not know how your machines got a node type of mixed, you are using dns search orders for a public domain on local machines that are on private addresses. You have wireless, etc. etc..

I would suggest you remove them.. Connect a machine that will not resolve on the same dumb switch as a machine that will not resolve it. Change the settings to default.. And work from there!

your node type should not be mixed on a network without a wins server - PERIOD! Your using a dns search list? Why?

thansk for the breakdown of nodes, appreciate it...

i will look into it.. the thing is, if i never knew about nodes, how would i have changed it? i have never changed one in the past, and all has worked..

i looked on my machine, it is set to DhcpNodeType-4

i will look later on the chef

regarding the switches, i have one xp home machine directly into the router, no switches, and it does not work.. i have not tried with the chef yet.. but why when i have the other xp that is not working plugged directly in...?

i have removed the search order pjrey.com (i didnt know what i was doing with that... whoopsies)

as you can surely tell, im not the best at this whole 'networking' business... i try my best to help my parents out at our resort, this is by no means my dayjob! (scary if it was though huh! haha)

i will report back later when i get more info (im on break right now, gotta get back to work)

pj

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Yet the best laptop for all day battery life is a Mac, hands down, no contest. Windows is bloated and power management is rubbish. Search indexer. Defender. Malicious Software Removal Tool. Windows Update (+DISM). Office CTR. Telemetry. Disclaimer: I own a surface laptop studio, multiple gaming desktops, server, and a macbook pro.
    • And bring back taskbar deskbands which were removed, and full and total customization of notification area icons like earlier
    • This has all the markings of a thinly veiled mechanism for force users of older versions of Windows to upgrade...and trash perfectly good hardware. Microsoft, your history easily supports this line of reasoning.
    • Plasma 6.5 brings improved Emoji Selector, better performance in Activity manager, and more by David Uzondu This week saw the long-awaited release of KDE Plasma 6.4, bringing better window management and a whole lot of color management features. Apart from the release of 6.4, the KDE team was able to get other work done, and this was all outlined in the latest issue of This Week in Plasma, which details what is coming down the pipe for future versions. Looking ahead to Plasma 6.5, the developers are making some notable changes to improve performance and general usability. To prevent its database from growing endlessly and causing performance problems over time, the Activity Manager service will now only store the last four months of your history by default. The Emoji selector app is also getting a much-needed redesign that makes the window more compact and moves the sidebar button to the header for a cleaner look. Other little details for 6.5 are being polished up too. The unpopular vertical line separating the date and time on the horizontal Digital Clock widget is gone; if you want it back, you can add it yourself with a custom date format. The "Add New" button has also been moved to the top toolbar in the Shortcuts page within Settings, freeing up some valuable screen real estate. The devs also reduced the minimum size of custom tiling tiles, a small but significant fix for anyone with an ultrawide monitor. In addition to that, the Networks widget's captive portal banner now uses inline header styling, so it doesn't look like a bunch of frames stacked inside each other anymore. Of course, before we get to 6.5, the current release needs some attention. Plasma 6.4's first bug fix release, 6.4.1, addresses issues like broken item selection in the Folder View widget and a bug that could cause the system to lock or suspend faster than intended. Keyboard navigation in list views in Discover feels smoother now, and text is easier to read in certain list items in KRunner. The devs also cleaned up how list items look when you press or click them in Discover. 6.4.1 also fixes a bug where the clipboard history popup would fail to select the top item, and makes the Earth Science Picture of The Day wallpaper plugin work again after its data source changed. Here's the full list of fixes: Fixed several issues in the Folder View widget that caused selecting or opening items to not work when using certain non-default view settings, when the view was scrollable, or when using a touchscreen. Fixed a bug in the Meta+V clipboard popup that sometimes failed to pre-select the top-most item. The Clipboard settings window’s shortcuts page no longer shows columns for local shortcuts that don’t do anything, since the clipboard is global in scope. Fixed the Earth Science Picture of the Day wallpaper plugin after the source data changed formatting again. Made a few fixes to the “Missing Backends” section of Discover’s settings window that kept it from working properly. Fixed a bug that prevented direct scan-out (and its performance benefits) from activating on rotated screens. Fixed an issue where the system could lock or suspend sooner than expected after an app stopped blocking those actions. Installing a new wallpaper plugin no longer causes the plugin list combobox to appear blank. The team even went back to squash some bugs in the older 6.3.6, tackling an issue that could cause keyboard shortcuts to get lost during a system upgrade and fixing an overflow bug with KRunner's faded completion text. Plasma 6.4.1 is set to arrive on June 24th, with 6.3.6 following on July 8th.
    • UniGetUI 3.2.1 Beta 1 by Razvan Serea UniGetUI is an application whose main goal is to create an intuitive GUI for the most common CLI package managers for Windows 10 and Windows 11, such as Winget, Scoop and Chocolatey. With UniGetUI, you'll be able to download, install, update and uninstall any software that's published on the supported package managers — and so much more. UniGetUI features Install, update and remove software from your system easily at one click: UniGetUI combines the packages from the most used package managers for windows: WinGet, Chocolatey, Scoop, Pip, Npm and .NET Tool. Discover new packages and filter them to easily find the package you want. View detailed metadata about any package before installing it. Get the direct download URL or the name of the publisher, as well as the size of the download. Easily bulk-install, update or uninstall multiple packages at once selecting multiple packages before performing an operation Automatically update packages, or be notified when updates become available. Skip versions or completely ignore updates in a per-package basis. Manage your available updates at the touch of a button from the Widgets pane or from Dev Home pane with UniGetUI Widgets. The system tray icon will also show the available updates and installed package, to efficiently update a program or remove a package from your system. Easily customize how and where packages are installed. Select different installation options and switches for each package. Install an older version or force to install a 32bit architecture. [But don't worry, those options will be saved for future updates for this package] Share packages with your friends to show them off that program you found. Here is an example: Hey @friend, Check out this program! Export custom lists of packages to then import them to another machine and install those packages with previously-specified, custom installation parameters. Setting up machines or configuring a specific software setup has never been easier. Backup your packages to a local file to easily recover your setup in a matter of seconds when migrating to a new machine UniGetUI 3.2.1 Beta 1 changelog: Added per-package-manager default install options Added the ability to run pre-install/update/uninstall and post-install/update/uninstall commands Added the ability to kill process(es) before a package is installed/updated/uninstalled Block custom command-line arguments (and pre/post commands) behind a SecureSetting switch SecureSettings are settings that require administrator privileges to be switched. Bundles won't import custom arguments & custom commands by default Bundles will show a security report when importing potentially dangerous settings Added a better crash message for when UniGetUI files are missing Deep improvements to how bundles and InstallOptions are loaded from disk. Improvements to WebView lifecycle Download: UniGetUI 3.2.1 Beta 1 | 51.7 MB (Open Source) Links: WingetUI Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Rising Star
      aphanic went up a rank
      Rising Star
    • Contributor
      GravityDead went up a rank
      Contributor
    • Week One Done
      BlakeBringer earned a badge
      Week One Done
    • Week One Done
      Helen Shafer earned a badge
      Week One Done
    • First Post
      emptyother earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      665
    2. 2
      ATLien_0
      264
    3. 3
      Michael Scrip
      235
    4. 4
      Steven P.
      162
    5. 5
      +FloatingFatMan
      152
  • Tell a friend

    Love Neowin? Tell a friend!