Re: XP Home Networking Nightmare



In article <178A3F1D-6D55-4374-8586-CEC024512CC5@xxxxxxxxxxxxx>,
"sonbolt" <sonbolt@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>I am going crazy trying to figure this out.
>
>I have two computers one laptop (wireless) & one desktop (directly connected
>to Linksys then Motorola cable modem) are using Windows XP Home SP2. I have
>had the same issue with two different routers D-Link DI-524 & Linksys WRT54G.
>I am currently using the Linksys.
>
>Went through the Network Wizard Setup on both computers and obviously turned
>on file sharing.
>
>Both computers can ping each other and access the internet. Windows IP
>Config on the desktop has Node Type of Peer-Peer and Hybrid on the laptop.
>
>On the desktop I can see the workgroup MSHOME & can see the Laptop icon but
>when I click on it I get the network path was not found error.
>
>When I go to the Laptop, I can't even view the workgroup. I get the message:
>
>Mshome is not acessible. YOu might not have permission to use this network
>resource. Contact the administrator of this server to findout if you have
>acess permissions.
>The list of servers for this workgroup is not currently available.
>
>On the Local Network for the desktop it states that I do have a SharedDocs
>on Desktop, but that one is not accessible, the network path was not found.
>
>I can also see the desktop printer on the laptop but cannot print.
>
>Both computers have different computer names and the same workgroup name
>MSHOME. Also tried with WORKGROUP as the name, this didn't work.
>
>Completely unecrypted the wireless router. Dropped the WEP security. Dropped
>the Windows Firewall on both computers. There is no other third party
>firewall installed.
>
>Even hardwiring the computers through the Linksys is giving the same errors.
>
>I also tried creating a user on both computerse named generic with the same
>password and then sharing a file on each computer. ALL TO NO AVAIL!!
>
>On the desktop, I tried using Ntrights.exe which is a Win2k3 resource kit
>because someone mentioned that this helped. After installation, click on:
>Start, All Programs, Windows Resource Kit Tools, Command Shell
>
>Then enter the following commands. (Attention: they are case sensitive.)
>
>net user guest /active:yes
>ntrights +r SeNetworkLogonRight -u Guest
>ntrights -r SeDenyNetworkLogonRight -u Guest
>
>The first command enables network access for Guest, the two subsequent ones
>change two different policies to allow network access for Guest.
>
>I'm so frustrated by this...I'm willing to try anything (except a complete
>format of course).
>
>Another interesting thing is that I can use remote desktop on the wireless
>laptop but not on the desktop?
>
>I would be indebted forever to anyone who could help me out!

The "Peer-to-Peer" node type on the desktop is probably causing all of
the problems. That node type (which is actually "Point-to-Point", but
ipconfig gets it wrong) requires a WINS server for name resolution,
but a peer-to-peer (workgroup) network doesn't have a WINS server.

On the desktop, run the registry editor, open this key:

HLM\System\CurrentControlSet\Services\Netbt\Parameters

and 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;160177

TCP/IP and NBT Configuration Parameters for Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
.



Relevant Pages

  • Help with 070-217
    ... The network contains 25,000 computers. ... single Windows 2000 domain named research.contoso.com. ... Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)
  • Re: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)
  • RE: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)
  • Re: WindowsXP and RISC OS computers
    ... >> - You can however ping Nixiyo from the windows XP machine, ... > workgroup: WORKGROUP ... > Name as M$ calls it, had been changed on the centrex machine. ... > Neither icon appears in My Network Places on the centrex. ...
    (comp.sys.acorn.networking)
  • Re: Probably a very basic problem
    ... >My sisters PC uses Windows 98 ... So I tried again creating a network ... >computer and changing its workgroup name to Mshome then Home. ... >in the network neighbourhood of the computers. ...
    (microsoft.public.windowsxp.network_web)