Archived from groups: microsoft.public.windowsxp.work_remotely (
More info?)
"Sooner Al" wrote:
> From a response by Steve Winograd, MS-MVP, to another user...
>
> **************************************
>
>
http://groups-beta.google.com/group/microsoft.public.windowsxp.network_web/browse_thread/thread/97dbb3f1a9a0bf89/115901c10e408185?q=node+type+group:*.network_web&_done=%2Fgroups%3Fq%3Dnode+type+group:*.network_web%26start%3D0%26scoring%3Dd%26safe%3Dimages%26lr%3D%26hl%3Den%26&_doneTitle=Back+to+Search&&d#115901c10e408185
>
> 4. Run "ipconfig /all" on XP and look at the "Node Type" at the
> beginning of the output. If it says "Peer-to-Peer" (which should
> actually be "Point-to-Point") that's the problem. It means that the
> computer only uses a WINS server, which isn't available on a
> peer-to-peer network, for NetBIOS name resolution.
>
>
> If that's the case, run the registry editor, open this key:
>
>
>
> HLM\System\CurrentControlSet\Services\Netbt\Parametersand delete these values if they're present:
>
>
> NodeType
> DhcpNodeType
>
>
> Reboot, then try network access again.
>
>
> If that doesn't fix it, open that registry key again, create a DWORD
> value called "NodeType", and set it to 1 for "Broadcast" or 4 for
> "Mixed".
>
>
> For details, see these Microsoft Knowledge Base articles:
>
>
> Default Node Type for Microsoft Clients
>
>
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177TCP/IP and NBT Configuration
> Parameters for Windows XP
>
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;314053******************************
> --
> Al Jarvi (MS-MVP Windows Networking)
>
> Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
> The MS-MVP Program -
http://mvp.support.microsoft.com
> This posting is provided "AS IS" with no warranties, and confers no rights...
>
> "Dingo" <Dingo@discussions.microsoft.com> wrote in message
> news:927E6567-FCD5-4DC5-9C6E-E7B42CC23227@microsoft.com...
> >
> >> That is not the default. Do you have (or have you ever had) WINS servers
> >> defined in the TCP/IP properties? If so, your PCs will be trying to use
> >> your corporate WINS server to do name resolution. As every PC is behind a
> >> NAT router, the responses from the WINS server will be confusing.
> >
> > I checked and found one of my computers had WINS server entries. I removed
> > them and then did ipconfig /all again. I noticed this changed the NoteType
> > to "Broadcast" on that PC, but my 2 other PCs have remained at Hybrid (even
> > after an IP release as well as a reboot) *How do I get them to change
> > NodeType?*
> >
> >> It is possible that your PCs are acquiring this WINS and NodeType
> >> configuration when they connect by VPN to your company network
> >
> > The WINS entries were on an older PC of mine that I used to connect to work
> > with. Removing them and connecting to my work VPN has worked fine. It is
> > not repopulating the WINS entries.
> >
> > Two other things - checking my router's dynamic DHCP entries; it was not
> > listing computer names for 2 of my PCs. When I did an ipconfig /renew from
> > those 2 PCs, that populated the router's dyn-DHCP table again. I then also
> > reran the home network wizard and though all my computers now show up in my
> > workgroup I am still not able to connect by COMPUTERNAME via Remote Desktop.
> > And I get the 'network path cannot be found' when I try to connect through
> > the workgroup explorer window....very strange...
> >
> > thx, Louie
It's working now. Thx to all on this thread. :^)
Just to confirm: I removed the DhcpNodeType entry and created a new
NodeType entry with a DWORD value of 1 - that changed the NodeType setting to
'Broadcast' when viewed through ipconfig /all.
Then I also found some old static entries in a hosts file on 2 of the
computers - some of which I put there a while back when trying to fix this.
I removed those and rebooted, and after that I am now able to ping
computernames and attach to them via RemoteDesktop.
Thank You!
Facebook
Twitter
Instagram