Author Topic: Networking 2 windows xp  (Read 658279 times)

thankful user

  • Guest
Networking 2 windows xp
« Reply #180 on: September 19, 2005, 08:14:52 PM »
Thank you so much for this post.  I have been trying to fix the same problem for weeks http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/smile.gif\' class=\'bbc_emoticon\' alt=\':)\' />

[quote name=\'matterdaddy.com\' date=\'Nov 14 2003, 05:18 PM\']1- Open dos prompt, type ipconfig -all.
2- Look at the 'Node Type' it probably says Peer-Peer or something (this is what mine said)
... we want it to say 'Hybrid'
3- Press 'Start' button > Run... > In the box type regedit. This opens your system's registry.
4- Navigate the tree to: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/NetBT/Parameters
5- Rt. mouse click and select New > DWORD Value
6- Name it 'NodeType' (without the quotes)
7- Rt. mouse click on it and select Modify
8- Set Value Data to '8' (no quotes)
9- Leave Base alone. 'Hexadecimal' should be selected
10- Press 'ok'
11- Close regedit and reboot. (Your done!)
12- Open dos prompt and type ipconfig -all
For node type it should now say 'Hybrid'
13- Do this to the other computer that you cannot network. Your computers should be able to see one another.
----------
I do not know what 'Hybrid' is, but perhaps some of the network freaks might be able to explain. I have used this on two different occasions and it seems to be the only thing that works.
[post=\"12029\"]<{POST_SNAPBACK}>[/post]
[/quote]

Guest

  • Guest
Networking 2 windows xp
« Reply #181 on: September 25, 2005, 03:40:09 AM »
If you have zone alarm goto zones under firewall in the program and add subnet with your routers subnet mask and ip address... problem gone and you can still have your firewall

Lanadmin

  • Guest
Networking 2 windows xp
« Reply #182 on: October 04, 2005, 03:03:53 PM »
The below post fixed my problem between Windows XP Pro SP2 and Win2K Server on a workgroup. Strange thing was the XP Pro machine could see machines on ANOTHEr workgoup, but not its own (Network path not found). After installing netBIOS on the problem machine (XP) it worked and I didn't even have to reboot.

[quote name=\'Angela\' date=\'Aug 12 2005, 11:33 AM\']Hi I had this problem too and maybe this solution will work for someone.

My network is 1- Windows XP home laptop, 1-Linux workstation and 1- Windows 98 first edition.

The Linux and Windows 98 were happily talking and sharing files and a printer. When I connected the laptop and joined it to the workgroup it gave the mentioned error.

My node type on the XP was hybrid and I have no firewall, not even the Internet connection firewall. I also tried enabling the NetBIOS in the WINS tab.

When I typed "net view" in a command window, I receved: " System error 53 has occurred. The network path was not found."

My solution was that on the XP laptop, on the LAN connection properties, I only had the following protocols:

Client for Microsoft Networks
File and Printer Sharing for Microsoft Networks
QoS Packet Scheduler
Internet Protocol (TCP/IP)

I needed to INSTALL the NetBIOS protocol using the Install... button. Now I can see my workgroup.

Thanks!
[post=\"52121\"]<{POST_SNAPBACK}>[/post]
[/quote]

Nick Matharu

  • Guest
Networking 2 windows xp
« Reply #183 on: October 07, 2005, 05:36:01 AM »
After months of trouble free working, my system started displaying this problem. I was unable to connect to network printers, because my machine could not see other computers in the network. System: Windows XP TabletPC (Pro) connecting to XP home over a LAN hub. Norton firewall.

Taking down the firewall enabled detection of other machines on the network, but not all, and this occurred randomly.

The below fixed this for me. Note: my node is still listed as "unknown" under ipconfig/all settings, but I can now see the entire network / workgroup and share files/ printers. Many thanks  http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />

[quote name=\'matterdaddy.com\' date=\'Nov 14 2003, 05:18 PM\']1- Open dos prompt, type ipconfig -all.
2- Look at the 'Node Type' it probably says Peer-Peer or something (this is what mine said)
... we want it to say 'Hybrid'
3- Press 'Start' button > Run... > In the box type regedit. This opens your system's registry.
4- Navigate the tree to: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/NetBT/Parameters
5- Rt. mouse click and select New > DWORD Value
6- Name it 'NodeType' (without the quotes)
7- Rt. mouse click on it and select Modify
8- Set Value Data to '8' (no quotes)
9- Leave Base alone. 'Hexadecimal' should be selected
10- Press 'ok'
11- Close regedit and reboot. (Your done!)
12- Open dos prompt and type ipconfig -all
For node type it should now say 'Hybrid'
13- Do this to the other computer that you cannot network. Your computers should be able to see one another.
----------
I do not know what 'Hybrid' is, but perhaps some of the network freaks might be able to explain. I have used this on two different occasions and it seems to be the only thing that works.
[post=\"12029\"]<{POST_SNAPBACK}>[/post]
[/quote]

Guest

  • Guest
Networking 2 windows xp
« Reply #184 on: October 10, 2005, 08:55:02 PM »
I have similar problem.
I am able to connect to shared folders by typing (in run) \\computername\sharedfoldername but not via \\computername

Not able to browse via network neighbourhood either.

My quick & dirty fix was to share all of C and make a short cut for \\computername\c

:shrug:

Guest_Stu_*

  • Guest
Networking 2 windows xp
« Reply #185 on: October 27, 2005, 07:36:46 PM »
Heres the problem I had:

Small home network, D-Link 4-port / wireless router.  PC's: two XP Home (wireless) , one XP Pro (wireless) one 2000 Pro (wired), one Win98 (wired).  

No firewall software on any PC's except Windows Firewall on all XP based machines (which by the way will not interfere with Microsoft File and Printer sharing or Client for Microsoft Networks).

The issue appeared only on my Laptop (XP Pro). It suddenly ceased being able to browse the network.  Error when clicking my Workgroup was:  "You might not have permission to use this network resource.  The path was not found."  Something along those lines.

However, entering the IP address into the address bar I could easily reach all PC's on the network inlcuding their shares and printers.

I found that my DHCP Node Type was "Peer-Peer" while my other WinXP based machines we're set to unknown.

I merely deleted the following registry key and was back in business:
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/NetBT/Parameters/DHCPNodeType
(If this doesnt work you could also try changing the value to one of the other suggestions in this post, such as: 1 - broadcast, or 4 - hybrid)

Still don't know what caused this, but it has happened to me before on other XP-based PC's.  If anyone has any info on this please post.

Cheers.

Offline HAKER

  • Newbie
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Networking 2 windows xp
« Reply #186 on: October 29, 2005, 06:51:27 AM »
i have are runescape secret! your mining, fishing, cooking, smithing... to up 50 lwls!!! if you send this mesagge with your information
to jagexxcorporationEmail Removed. send this:
@@@@@@@@for@runescape@@!!!?+_+_+_+_+_+_+_+_!!!!!!!!???:':????::::...<<<<?????>>>>>your user name@@@@@@^^^^&&&&&""::}{|{|{|}{}|{}|
@@@@########$$$%^&^*()(*&&&&&"""""_+_+_+_+_+_++__*&**&#()#?>>?>?><:"":}{{}||{}}}|(*#($(^$#($(#^$#^&*$&$*(your user password _)(((((***(
:":}{)(()**()&)*(^^&*^^%^%^%**&*^^&**%%$^&$&%$%^^&*%^$^*&())()(*(&&^%#$#@@@@!!!!@@#$%$%%^&^&&^&&**&(*^*^&&$@%@#@%^%^#$#%$^%%&%
 
i want to help for people who play runescape!

down in france

  • Guest
Networking 2 windows xp
« Reply #187 on: November 01, 2005, 12:20:44 PM »
Hey Guest_Stu*,  

I just had the same problem.  I suddenly lost my ability to search my network, ...but I could map to my computers using the IP addresses.  I went to the web-site that had me running a ton of tests, ...none of them said check your node type.  (http://www.experts-exchange.com/Networking/Microsoft_Network/Q_20965078.html) and (http://65.24.134.81/KipSolutions/P2PNetworks/TroubleshootingP2P.htm).

I deleted my node type, and I'm back up and running.  Thanks!!!

The last thing I did with my laptop was to hookup to a hotels wireless network, ....it must have changed the setting.

Regards,   ....Down in France

Guest

  • Guest
Networking 2 windows xp
« Reply #188 on: November 02, 2005, 12:30:30 PM »
I have tried everything in this thread and still not a clue what is happening.
I have 2 XP machines (1pro and 1 media ed.). They both are connected to a Dlink router and can access the internet.

I can ping from both, each other, the router, back and forth but cannot see either if I browse the workgroup.

They are both part of the same workgroup

both hybrid

both have Netbios in Wins enabled, computer browser running

firewall uninstalled

etc. etc.

I would even settle for a "cannot connect ot share" error just as long as I could see the  
PC's. Can't even map them.

When I click the workgroup on both PC's ther are none in the window. What's worse is on one of them it could at least see itself. Now after all the changes I made it disappeared from it's own window and can't even see itself.


Before I start looking at permissions and accounts I want to be able to see them if I browse the workgroup.

Does anyone have a clue to whay I can ping and but cannot see the PC's?

No one has mentioned DNS much could that be an issue? I know that you can have a DNS problem when you are working with PC names on a Domain but does this matter on a home network without a Server?

Another clue may be that I can't ping the PC by name, as in "ping comp1" which gets me a "unknown host" message even though that is the PC's name.

Goodrichmcse

  • Guest
Networking 2 windows xp
« Reply #189 on: November 09, 2005, 12:27:39 PM »
http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> YES YES YES this is probably the issue.
Most people want to go the hard route to simple.
keep it simple stupid method usually works.
Make sure that Client for microsoft box is checked and if its not there install it. This will allow the XP Pc to see other PCs in workgroup or domain.
Cheers http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/wink.gif\' class=\'bbc_emoticon\' alt=\';)\' />



[quote name=\'Biju Jacob\' date=\'Nov 18 2003, 01:21 AM\']Just go back to the basics and try.Is Client for Microsoft Networks Checked?
If not Please do it and try.I also faced the same problem and for me this was the issue.If it is rectified ,pls mail me.
Email: biju_caEmail Removed
[post=\"12065\"]<{POST_SNAPBACK}>[/post]
[/quote]

dark man852

  • Guest
Networking 2 windows xp
« Reply #190 on: November 09, 2005, 12:49:56 PM »
give me hack give me hack fooooor money plz  http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/laugh.gif\' class=\'bbc_emoticon\' alt=\':lol:\' />

Offline LordLiverpool

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Networking 2 windows xp
« Reply #191 on: November 09, 2005, 01:56:03 PM »
Another satisfied customer!   http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/rolleyes.gif\' class=\'bbc_emoticon\' alt=\':rolleyes:\' />

My problem was that I had a network with a Windows 2000 PC ( A ) and a Windows XP PC ( B ).

- I could access all the shares on A (2k) from B (XP)

- I couldn't see the shares on B (XP) from A (2k) (I got a message saying "not accessible").

- I could see B (XP) in the list of workgroup computers from A

- I couldn't see any computers in the workgroup from B

I finally managed to see the shares on B from A. I went through the following process, mostly by reading suggestions from this forum:

- I applied the "hybrid" NodeType fix to both computers (didn't make any difference)
- I fiddled with XP permissions and disabled Simple File Sharing so that I could specifically add "Guest" to the list of users allowed to access the shared folders (didn't make any difference).
- I changed the XP machine Local Security Policy to allow Guest to access the network, make "everyone" include "anonymous" and allow anonymous enumeration of SAM accounts (didn't make any difference).
- I installed NETBios on the XP machine and yippee! I got a different error message! Well, hey, it's progress of a sort. This time it said that it couldn't log on to the other machine.
- I reenabled Simple File Sharing on XP and fiiiiiiinally...... I saw the shares from Windows 2000.
- To round things off, I undid my Local Security Policy changes so as to keep security as tight as possible, and everything still worked.

What I haven't tried yet is undoing the "hybrid" change to see if it has made any difference.

I still can't see the workgroup computer list from the XP machine, but that doesn't worry me much. I just access the 2K PC via the UNC name directly and set up shortcuts.

A huge thank you to everyone who helped with this!  http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />
« Last Edit: November 09, 2005, 01:59:09 PM by LordLiverpool »

Offline Lord Roop

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Networking 2 windows xp
« Reply #192 on: November 18, 2005, 07:44:26 PM »
Folks, just to let you know I had this problem and it was purely down to Zonealarm. Solution: turned off ZoneAlarm and it worked fine. Turned it back on, put in the IP address and subnet mask from an ipconfig search on both machines and it now works fine.
Funny thing is that I did all this and got it working before, but now the IP addresses had changed. The wireless router had changed from 192.168.1.0 to 192.168.1.1 and the IP addresses of the machines had swapped over. Presumably that was due to the boot order.
Anyway, all working now.
Oh and I also checked the Registry to ensure it said what an early post mentioned and it did.

So thanks guys. An excellent thread and most helpful. In fact it was so good I registered  http://images.thetechguide.com/forum/public/style_emoticons/<#EMO_DIR#>/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />

Best regards,
The Lord Roop

P.S. Found the thread on google searching for "The Network Path was not found"

Offline novice2

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Networking 2 windows xp
« Reply #193 on: December 04, 2005, 01:13:15 AM »
My new xppro laptop was giving this error. Turning off Norton Internet Security--mentioned in about the second post in this threat fixed it. Many thanks.

Offline jcappell

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Networking 2 windows xp
« Reply #194 on: December 04, 2005, 11:37:43 PM »
It was very helpful to see the many good ideas for dealing with the sharing problem between two XP systems.  I have two XP Home sytems with sharing turn on for the "My Documents" folders and several other folders created at the root level (e.g., C:\backups).

While all of the shared folders on computer "A" are listed under the my network places on computer "B," the My Documents folders could not be opened.  Yet the C:\backups folder can be accessed with full permissions.

I tried a couple of the suggested fixes, including shutting down the firewalls and also setting Node Type to "hybrid."  Neither worked on my systems.

However, someone pointed out that the XP Home simple file sharing limitations are turned off when booted in safe mode.  I made a couple changes to the security settings for the My Documents folders while in Safe Mode and now sharing works fine.

In safe mode,  using windows explorer, right-click on the My Documents folder and select properties.  

Select the Security tab.  

Mine originally listed the following three "Groups or User Names"
Administrator
Ann (the account name for My Documents)
System

Yet the C:\backkups directory on computer A, which was accessible to Computer B, had the above Groups or User Names plus two additional entries:
Everyone
Users

Adding these two entries and granting them Full control worked for my systems.

Good Luck.

(By the way, I would have preferred to have given access to only a specific account on computer "B," but the advance settings in the security tab would not recognize Computer B and thereby could not specify B\username. )

Offline bowtie406cid

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Networking 2 windows xp
« Reply #195 on: December 13, 2005, 10:47:07 PM »
Ok check it out! I followed some advice from microsoft.
Searched for my computer and found it but if I go to Network Places view workgroup computers I cant see it... why??

Offline drilldown

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Networking 2 windows xp
« Reply #196 on: January 17, 2006, 02:11:13 AM »
Thanks to all posters of solutions.  I'm going to work on this tomorrow and I'd just like to say thanks to everyone tonight.  I'll not have been alone.

A summary of solutions for "Network Path not Found":
as of 1/16/2006 since around 2004.

1-   Open dos prompt, type ipconfig -all.
2- Look at the 'Node Type' it probably says Peer-Peer or something (this is what mine said)
... we want it to say 'Hybrid'
3- Press 'Start' button > Run... > In the box type regedit. This opens your system's registry.
4- Navigate the tree to: HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/NetBT/Parameters
5- Rt. mouse click and select New > DWORD Value
6- Name it 'NodeType' (without the quotes)
7- Rt. mouse click on it and select Modify
8- Set Value Data to '8' (no quotes)
9- Leave Base alone. 'Hexadecimal' should be selected
10- Press 'ok'
11- Close regedit and reboot. (Your done!)
12- Open dos prompt and type ipconfig -all
For node type it should now say 'Hybrid'
13- Do this to the other computer that you cannot network. Your computers should be able to see one another.



type ipconfig /all using Comand Prompt
If under node type it says Peer to Peer
Then go to start regedit
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters
Make sure that under DHCP node type (1) not 2 is in brackets. If (2) is present right click and modify it to (1)
Renew the IP
Check Config /all again.
The Node type should now be broadcast
The problem only seemed to be with the PC which booted up last - weird.

M$ docs refer to 1 as type "B", 2 as type "P", 4 as type "M", and 8 as type "H"
What this basically means is different ways of resolving netbios names.

1 = broadcast. The host sends a broadcast and the nodes which knows the ip of that name answers.
2 = peer. Sends the request directly to a wins server which looks up the name.
4 = multi node. I don't really remember but I think it starts with broadcast and if no answer does a direct lookup from a wins server.
8 = hybrid. Not sure here either, but I think it starts with a direct request to the wins server and if the server is unable to resolve the name it does a broadcast.


I have come across this issue setting up windows xp machines often. No matter how many times you run the network wizard it just won't work 50% of the time. But, I did find that if I did a search for the computer name, I found the machine everytime and as long as the folders have shared rights then it was never a problem and I just mapped the folder. This was networked across a linksys router with default settings. Hope this helps



Had the same problem. I have 3 computers networked on a wireless access point. Shared folders show in network places but access was denied. All run windows XP. I turned off zone alarm and now all computers can share.



After experiencing very similar problems to posts in this and numerous other forums, I finally figured it out: At some stage, the orignal user for whom the computer was setup changed their login name.

The solution:
Assuming all other (obvious) networking issues have been addressed (ie. usernames AND passwords setup for both users on both machines, NetBIOS enabled for TCP/IP, permissions granted for shares etc.)...

1.) In Windows Explorer, from the tools menu, select "Map Network Drive...".

2.) Select an appropriate drive letter and enter the path to the shared resource (\\machine\share).

3.) And here's the trick... Click on "Connect using a different user name.

4.) You'll notice that the Connect As... dialogue indicates the default username that will be used - probably the same name as your user folder under Documents and Settings. Enter the correct username and password for this shared resource and you should be networking happily.

Note: If you're not using DHCP with a DNS on the network, a suitably written hosts file in \<WIN>\system32\drivers\etc can help speed up finding shared resources.




I had this problem with an Acer TravelMate 290LMI (Intel 2100 802.11b on-board), a NetGear WGR614v4 AP/router. I tried everything that a good 6 hours of web searching will yield and in the end it was WPA.

WPA on the Acer screwed things up. I can use WEP and any other kind of security" (MAC restriction, etc.) but as soon as I turn on WPA it all goes pear-shaped and my local connections fail. Internet is fine.

BTW, I had looked for and found all the laterst drivers for the Acer and the AP/Router, tricked up the settings, tried EVERYTHING. It was definitely some kind of WPA issue.



Having tried just about everything to have a W2000 machine and an XP Pro machine both share files with another XP Pro machine, I finally came across these posts. All machines were already hybrid, but the XP machine I could not access had Zone Alarm on it. Even when I shut down Zone Alarm I could not access it.

So, per a previous post, I uninstalled Zone Alarm and was surprised to see the uninstall process shutting down a process. After the uninstall and reboot, I could "miraculously" access all shared drives on the XP machine.

Thank you!




I echo what others have said: There are many reasons why a share may been seen by another machine on a network but still won't be accessible.

In my case, the user "Everyone" was missing from the computer doing the sharing.

Remember that NTFS permissions are more granular and SUPPLEMENT the share permissions. In order to have access to a share, you have to have privileges. But if NTFS is not ALSO giving you access, then you will simply see the share and not the files (and possibly folders) in that share.

In my case, I could see the share, but it appeared to be empty when I accessed it from other computers on my network. This is a tell-tale symptom of INSUFFICIENT NTFS PRIVILEGES on that share. To change those permissions, you have to work with the security tab of the folder(s) being shared--and this is most easily accomplished by actually going the the computer that is hosting the folder.

If you see a share but can't access it, you likely have no firewall issue.



http://support.microsoft.com/?kbid=318030



You cannot access shared files and folders or browse computers in the workgroup
View products that this article applies to.
Article ID : 318030
Last Review : June 23, 2005
Revision : 3.2
This article was previously published under Q318030
On This Page
 SYMPTOMS
 CAUSE
 RESOLUTION
   Step 1: Turn on NetBIOS over TCP/IP
   Step 2: Start the Computer Browser service
 MORE INFORMATION
 APPLIES TO

SYMPTOMS
On Windows XP-based computers that are configured as members of a workgroup in a peer-to-peer network environment, you may experience one or more of the following behaviors: • You cannot access shared folders or files.
• You cannot locate other computers in the workgroup.
• You receive the following error message when you double-click the workgroup in My Network Places:
Workgroup Name is not accessible. You may not have permission to use this network resource.  

 Back to the top

CAUSE
This behavior may occur if both the following conditions are true: • NetBIOS over TCP/IP is not turned on (enabled) on one or more computers in the workgroup.
• The Computer Browser service is not started or is turned off on one or more computers in the workgroup.

 Back to the top

RESOLUTION
To resolve this issue, make sure that NetBIOS over TCP/IP is turned on and the Computer Browser service is running on each computer in the workgroup. To do this, follow these steps.
 Back to the top

Step 1: Turn on NetBIOS over TCP/IP
1. Click Start, click Control Panel, and then click Network and Internet Connections.
2. Click Network Connections.
3. Right-click Local Area Connection, and then click Properties.
4. Click Internet Protocol (TCP/IP), and then click Properties.
5. Click the General tab, and then click Advanced.
6. Click the WINS tab.
7. Under NetBIOS setting, click Enable NetBIOS over TCP/IP, and then click OK two times.
8. Click Close to close the Local Area Connection Properties dialog box.
9. Close the Network Connections window.

 Back to the top

Step 2: Start the Computer Browser service
1. Click Start, right-click My Computer, and then click Manage.
2. Double-click Services and Applications.
3. Double-click Services.
4. In the right pane, right-click Computer Browser, and then click Start.
5. Close the Computer Management window.

 Back to the top

MORE INFORMATION
The Computer Browser service maintains an updated list of computers on the network, and it supplies this list to computers that are designated as browsers. If this service is stopped, the list is neither updated nor maintained. If this service is turned off, any services that explicitly depend on it do not start.

For additional information about the Network Setup Wizard in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
308522 (http://support.microsoft.com/kb/308522/) Description of the Network Setup Wizard in Windows
For additional information about how to connect to network resources in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
311079 (http://support.microsoft.com/kb/311079/) How to connect to network resources in Windows XP without mapping a drive or port
For additional information about file sharing in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
304040 (http://support.microsoft.com/kb/304040/) How to configure file sharing in Windows XP
 Back to the top


--------------------------------------------------------------------------------

APPLIES TO
• Microsoft Windows XP Home Edition
• Microsoft Windows XP Professional



Let me just say... I spent hours and hours and hours pulling my hair out with this exact problem!

But after reading the quoted post i solved my problem!! Thank GOD!
Here is how i solved it:

I am running 2 machines. A desktop as my Server (running Server 2003) and a laptop as my client (running Windows XP Sp1). Im running ADSL (Alcatel 4 port ethernet modem) with a wireless Linksys WRT54G router.

My laptop is running with a wireless care and my server is directly connected via cat5 into the wireless router. I was able to ping and communicate with each other, I could also access the files from my server to the laptop but could not access files from my laptop to the server. I kept getting that bloody "may not have permissions to access this resource" microsoft crap.
I enabled NetBIOS over TCP/IP on both machines, I then went to my server (Which was the one i couldnt access) and added the "everyone" permission in the security tab. (Dont try adding it to the permissions tab. It doesnt work!)

This solved the problem!
Anyone else with problems feel free to email me on jamiesonyEmail Removed





I've been reading this forum with interest to help me solve similar network problems.

As it turns out, a different solution than the ones I've been reading about worked for me. Maybe my symptoms were the same and the cause (in my case) was different.

In any event, as "one more thing to check", the solution that worked for me was to make sure LAN WINS was configured with the IP address of my server on all clients.

To get there, from Control Panel I selected "Network Connections" then "Local Area Networking", "TCP/IP Protocol", "Properties", "Advanced", then the WINS tab. If your server IP is not listed in the WINS addresses box, click "Add" and type it in. Then reboot (if running NT4.0).

Basically, this makes sure your computer is telling the server about itself. Something had reset this and the server had lost track.

Note: My network uses NT4.0 Server with fixed IP addresses (mapped within a hardware firewall) and a collection of client OS's, including NT4.0, Win2000Pro, and XP ... this may not work for you if your network is set up differently.

The XP firewall (which I keep enabled for fear of Sasser) is *also* an impediment. When I have the full firewall enabled (IP Security/IPSEC "Require Security" on 2000Pro) I cannot browse into that machine.

My server is always accessible. Probably because it's NT4.0 and doesn't have a software firewall.

I have not found a way to open a door in the firewall to local IP's. I wish I could...that would let me get in to the XP machines with the firewall still up. It seems like there should be some way to list "trusted IP's", no?


http://support.microsoft.com/default.aspx?...kb;en-us;810881
"Access is Denied" Error Message When You Try to Open a Folder
View products that this article applies to.
Article ID   :   810881
Last Review   :   June 23, 2005
Revision   :   2.2
SYMPTOMS
When you try to open a folder in Microsoft Windows XP, you may receive the following error message, where Folder is the name of the folder that you cannot open:
Folder is not accessible. Access is denied.
CAUSE
This issue may occur if the folder that you cannot open was created on an NTFS file system volume by using a previous installation of Windows, and then installing Windows XP. This issue may occur although you enter the correct user name and password. This issue occurs because the security ID for the user has changed. Although you use the same user name and password, your security ID no longer matches the security ID of the owner of the folder that you cannot open.

For example, although you use the same user name and password, you may no longer have permission to open the folder after you complete the following steps:
1.   Before you install Windows XP Professional, you change the actual location, or target location, of the My Documents folder to another volume.
2.   You format the primary partition.
3.   You install Windows XP Professional.
RESOLUTION
To resolve this issue, you must turn off Simple File Sharing, and then take ownership of the folder:
1.   Turn off Simple File Sharing:
a.    Click Start, and then click My Computer.
b.    On the Tools menu, click Folder Options, and then click the View tab.
c.    Under Advanced Settings, click to clear the Use simple file sharing (Recommended) check box, and then click OK.
2.   Right-click the folder that you want to take ownership of, and then click Properties.
3.   Click the Security tab, and then click OK on the Security message, if one appears.
4.   Click Advanced, and then click the Owner tab.
5.   In the Name list, click your user name, Administrator if you are logged in as Administrator, or click the Administrators group.

If you want to take ownership of the contents of that folder, click to select the Replace owner on subcontainers and objects check box.
6.   Click OK.

You may receive the following error message, where Folder is the name of the folder that you want to take ownership of:
You do not have permission to read the contents of directory Folder. Do you want to replace the directory permissions with permissions granting you Full Control? All permissions will be replaced if you press Yes.
7.   Click Yes.
8.   Click OK, and then reapply the permissions and security settings that you want for the folder and the folder contents.
MORE INFORMATION
For additional information about file and folder permissions, click the following article number to view the article in the Microsoft Knowledge Base:
161275 (http://support.microsoft.com/kb/161275/) Interaction of file and folder security on NTFS volumes




A solution to the problem of not being able to browse a PC in the workgroup even though you can see it on XP. For all those who have been using the map network drive as another user this is a proper solution.

1. Right click my computer and choose manage

2. Go to Local Users and Groups\Users

3. Double click on Guest

4. select member of, click on add and choose administrators

5. You also need to make sure that guest account is enabled in control panel\users

This should work for everyone but be aware that its only advisable when you trust all computers on the network such as at home because admin privelidges are set for any computer on the network. If this is the case you could create a new group with the restrictions you want.

Now I can rest.........







Unregistered



 

I also tried everything here to no avail! So, in desperation I decided to look at it myself.

My solution was simply that one of the XP machines didn't allow access to its system without a password. However, there was no password set on the machine.

I changed the security policy (Control Panel / Administrative Tool / Security Policy / Local Profiles / Security Options / Limit Local Account Use of Blank Passwords to Console Login Only) from Enabled to Disabled.

Hey it worked for me.



Spent hours on this then when I saw guest's solution:

type ipconfig /all using Comand Prompt
If under node type it says Peer to Peer
Then go to start regedit
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters
Make sure that under DHCP node type (1) not 2 is in brackets. If (2) is present right click and modify it to (1)
Renew the IP
Check Config /all again.
The Node type should now be broadcast
The problem only seemed to be with the PC which booted up last - weird.
Good luck

Fixed immediately. Whooo hoo!! Thanks!!



http://ecross.mvps.org/faq.htm
Q: I have two XP Pro machines and another computer running Windows ME. When I try to access network shares on the Windows XP machines, I receive the following error:

    \\PC1 is not accessible. You might not have permission to use the network resource. Contact the administrator of the server to find out if you have access permission.

    Not enough server storage is available to process this command.

A: The problem is on the machine you are attempting to connect to. It's not on the machine you see the error message. On the computer you are connecting, check the Event Viewer for an Event ID 2011. If so, you need to fix the IRPStackSize that is indicated in the following Microsoft Knowledge Base Article. Norton Antivirus can cause this to happen.

Antivirus Software May Cause Event ID 2011
http://support.microsoft.com/default.aspx?...kb;EN-US;177078
Back to Top
Q: The "Wireless Networks" tab is missing in the Wireless Network Connection Properties. I only see the General and Advanced tabs. How do I restore the Wireless Networks tab?

A: The Wireless Networks tab appears when your network adapter fully supports the Wireless Zero Configuration (WZC) service. Check with your wireless adapter vendor for a version of a driver that supports Windows XP and the WZC service. Make sure the WZC service status is started. Click Start, Run, and type "services.msc". Open Services and scroll down to the Wireless Zero Configuration Service, start the service and set it to automatic.

If it does not show in the list of Services:

1. Run regedit and find

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WZCSVC

2. Add a DWORD entry named "Start" and value "2".

Warning! If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. I cannot guarantee that you can solve your problem from using Registry Editor, so use the Registry Editor at your own risk.
Back to Top
Q: How can I get Windows XP Home to join a domain?

A: Windows XP Home cannot join a domain. The behavior is by design. You can connect to domain resources. For more details, see the following links.

Windows XP in a Domain Environment
http://www.microsoft.com/windowsxp/home/ev.../xpindomain.asp

Why Windows XP Professional is Best for Domain-Based Networks
http://www.microsoft.com/windowsxp/home/ev...joindommore.asp
Back to Top
Q: Is there a maximum number of computers I can have networked using Windows XP?

A: There is no limit to the number of computers that can be networked with both Windows XP Home and Professional. However, there is a different limit. No more than 10 other people can connect to your computer at one time if you are using Windows XP Professional. For Windows XP Home Edition, the limit is 5. These limits cannot be changed. For more details, see the following Microsoft Knowledge Base Article.

Inbound Connections Limit in Windows XP
http://support.microsoft.com/default.aspx?...kb;en-us;314882
Back to Top
Q: I want to share a folder but require a password to open it over the network.  How do I password protect a folder in Windows XP?

A: Windows XP doesn't use passwords for shared disks or folders. If you are running Windows XP Professional, you can disable Simple File Sharing and assign different levels of permissions for each user, and NTFS file permissions for folders and shared resources. Many programs let you password protect individual files (for example, Microsoft Office applications), and with Compressed zipped folders, you can define a password to it. For more details, see the following links.

Windows XP Professional File Sharing
http://www.practicallynetworked.com/sharin...aring/index.htm

HOW TO: Use Compressed (Zipped) Folders in Windows XP
http://support.microsoft.com/default.aspx?...kb;en-us;306531
Back to Top
Q: What does a Network Bridge do?

A: The Network Bridge is a new feature of Windows XP. It combines two or more separate networks into one logical network. Adapters that have Internet Connection Sharing (ICS) or Internet Connection Firewall (ICF) enabled cannot be part of the network bridge. For more details, see the following link.

XP ICS - Network Bridge
http://www.practicallynetworked.com/sharin...tworkbridge.htm
Back to Top
Q: I'm trying to run ipconfig but the problem is that the command prompt window flashes on my screen for a brief second then disappears. How do I get it to stay on the screen long enough so I can read it?

A: This can happen when you are running the ipconfig command from the "Run" box. Instead run ipconfig at the command prompt. Click Start, Run, and type "cmd" (without quotes) and press ENTER. At the command prompt, type ipconfig and press ENTER. If you want to run ipconfig from the "Run" box, type cmd /k ipconfig.
Back to Top
Q: What is the 1394 Network Connection?

A: Windows XP detects a 1394 Network Connection when a 1394 network adapter is installed. This device is actually your firewire network card. Windows XP allows firewire networking. You can simply connect two computers with a firewire cable if the other machine has a 1394 adapter. Unless you are using the connection, you can simply disable it or ignore it and still allow your network to function.
Back to Top
Q: Every time I run the Network Setup Wizard, I get a "Spooler Subsystem App has encountered a problem and needs to close" error message. I have tried to find a solution but I don't really understand what this error has to do with me trying to set up a home network. Any suggestions?

A: To resolve this problem, obtain the latest service pack for Microsoft Windows XP. A workaround is to open the command prompt and type net stop spooler before running the Network Setup Wizard. After running the Network Setup Wizard, then you can restart the spooler service by typing net start spooler at the command prompt. The problem was first corrected in Service Pack 2 (SP2) for Windows XP.
Back to Top
Q: I have a computer that is running Windows XP Home Edition and I would like to add the computer to my Novell network to access some data. However, I cannot find the Client Service for NetWare when I attempt to add one. I don't know whether or not if Novell provides a client for XP Home. Any suggestions?

A: The Client Service for Netware isn't included in XP Home. You can upgrade to XP Professional which has the Client Service for Netware included. The Novell client may work on XP Home but it definitely isn't supported. The Novell client was not designed for that operating system. For more details, please see the following link.

Will Novell provide a client for Microsoft Windows XP Home Edition?
http://support.novell.com/cgi-bin/search/s...i?/10065595.htm
Back to Top
Q:  I have two computers on the network and they are both running Windows XP. The problem is with one of the computers on the network. I can access shared files on one computer. When I try to access any of the shared files and connect to the other computer I get the following error:

PC#1 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

Logon failure: the user has not been granted the requested logon type at this computer.

A: On any XP Pro computer check the Group Policy settings. Check your Local Security Policy (Click Start - Control Panel - Administrative Tools). Click to expand Local Policies, then click User Rights Assignments. Click "Access this computer from the network" and make sure that the Everyone group is included. Click "Deny access to this computer from the network" and make sure that the Everyone group is NOT included.

If the computer runs Windows XP Home Edition, the "secpol.msc" program isn't available to make the required user right assignments. Use the ntrights utility that is part of the Windows 2003 Resource Kit Tools to make the change. To do so, follow these steps:

1. Download and install the Windows Server 2003 Resource Kit Tools.

2. Click Start | All Programs | Windows Resource Kit Tools | Command Shell. Type these lines at the command prompt.  The second and third commands are case-sensitive, so type them exactly as shown.  Note the "+r" in the second one and the "-r" in the third one:

 net user guest /active:yes
 ntrights +r SeNetworkLogonRight -u Guest
 ntrights -r SeDenyNetworkLogonRight -u Guest


After doing a lot of head scratching and a lot of the suggestions above, here's what worked for me:

Simple file sharing, the only method on Windows XP Home and one of two choices on Windows XP Professional, always uses the Guest account. (Classic file sharing also automatically uses the Guest account if the original logon request fails.) If access through the Guest account is inhibited, then sharing cannot work, except when logging on to XP Professional with classic file sharing through another account.

There is a user rights policy to deny network access to certain users and groups, which contains a SUPPORT user and often, perhaps by default, Guest. If Guest is included here, guest access from other computers will not be possible and yields the error message, "Logon failure: The user has not been granted the required logon type at this computer.". Double-click on the policy and remove Guest from it.

For network access to Windows XP Pro with classic file sharing (Simple File Sharing disabled) through the Guest account, the Guest account has to be enabled on Windows XP and network login for the Guest account has to be permitted in Computer Management, Local Users and Groups.

Hope this helps somebody.


And also the registry key I changed was DHCPNodeType, not plain NodeType (Win XP Pro)




Okay guys, For those of you who are still looking, here is the solution...
Ross has it correct with an MS post. I had gone through all the basics and everything was correct. Basic Networking was fine, email was fine, Internet Browsing was fine...anything that was IP based. I disabled my Norton Internet Security and still nothing. I could not browse shared folders.

The post from MS Here is to make sure thant NetBios over TCP/IP is turned on Local Area C

Step 1: Turn on NetBIOS over TCP/IP
Click Start, click Control Panel, and then click Network and Internet Connections.
Click Network Connections.
Right-click Local Area Connection, and then click Properties.
Click Internet Protocol (TCP/IP), and then click Properties.
Click the General tab, and then click Advanced.
Click the WINS tab.
Under NetBIOS setting, click Enable NetBIOS over TCP/IP, and then click OK two times.
Click Close to close the Local Area Connection Properties dialog box.
Close the Network Connections window.

Step 2: Start the Computer Browser service
Click Start, right-click My Computer, and then click Manage.
Double-click Services and Applications.
Double-click Services.
In the right pane, right-click Computer Browser, and then click Start.
Close the Computer Management window.

It did, it did! This was the solution for me.

My situation is exactly as you describe: My XP Home laptop could see my XP Pro desktop in the workgroup but could not access its contents.

As you described, I went on the XP Pro desktop and went into ...

* Administrative Tools
*** Local Security Policy...

* Local Policies
*** User Rights Assignment...

And found the key "Deny Logon Locally," and removed "Guest" from it.

Bingo!

Of course, now that means that anyone who gets past our hub's firewall and our WEP can also log onto the home computer and access SharedDocs and Shared Printers. Whoopdee. I don't feel worried about this, but my better half would prefer to find another solution. Two things come to mind: Upgrade my laptop from XP Home to XP Pro (expensive) or replace our workgroup with an actual domain and set up the XP Pro desktop as a proper domain controller (complicated and beyond our current knowledge). Any one of you gurus care to comment on either solution or the appropriateness of worrying about it in the first place?

Thank you thank you,
--

i should mention that you need to run "net view" from command prompt to verify that you have configured your home network setting correctly in windows xp before tweaking your firewall settings.


Ok guys I had this problem and actually came to this forum to try and resolve it - I ended up resolving it myself after trying a few of the ideas/solutions listed here.

My situation:-

Working on my cousins lappy (XP HOME SP2), joined it to my network of 6+ PCs and Inet Gway so I could DL patches and trransfer cool files to and from it  

Connected fine to my Personal Use/Work PC (XP PRO SP2) and my File server (XP 2003 SERVER) but when I tried to access my Music Server/Entertainment Box (XP PRO SP2) I got "the Error" we all know and loath!

What I did to resolve:

Using Remote Desktop Connection (RDP) Accessed the PC that would not allow the connection ie Music Server/Entertainment Box.
Then proceeded to:

Start>
All Programs>
Administrative Tools>
Open Local Security Policy

In the left pane under

Security Settings>
Local Policy>

Clicked on Security Options

In the right pane I changed the 2nd Policy from the top
Accounts: Guest account status to DISABLED

Immediately upon doing so I was granted access, remember I am working on my EntBox via RDC from my Personal PC with my cousins lappy beside it for easy access.

Offline drilldown

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Networking 2 windows xp
« Reply #197 on: January 18, 2006, 02:20:59 AM »
Quickly eliminated the obvious suspects thanks to folks here.

It's the wireless thing.  Connections suddenly became unstable, hit or miss, and dropped as
"path not found".  Changed wireless router and access is somewhat better, and some can
access depending on distance from the router.  Same room is fine.  Two rooms is iffy, two
days ago went across the parking lot at speed with no problem.

From my personal experience a bad network card will take down a network by "chattering"
traffic.  That takes out the whole network usually and whatever this is simply takes out the
WiFi distance drastically and fast.

Some new interference or serious wi-fi traffic increase.  Weather?  I'll know better when
I find better.  Digging down.

Offline philipms

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Networking 2 windows xp
« Reply #198 on: January 31, 2006, 01:54:32 PM »
What a pain the Windows XP Pro "Access is Denied" Network Error is.
My Network obtains the IP address automatically.  It is not a fixed IP address.  I have a Speedstream DSL modem and a Netgear router.  I have no user or guest accounts.  I just boot up in XP with no login.  I have full admin priveledges and there are no passwords, since it's my home and I am the only one who uses both computers. The computers are nearly identical Windows Xp Pro SP2 systems.

The fix for me:
**************
Change security policy (Control Panel / Administrative Tool / Security Policy / Local Profiles / Security
Options / Limit Local Account Use of Blank Passwords to Console Login Only) from Enabled to Disabled.

thank you for all who posted this!

It didn't finally work until the above was done, but previously I had tried other things that may or
may not have helped set me up for the fix above:

-uninstalled Zone Alarm on one machine & closed Kiero Personal Firewall on other machine.
-I enabled NetBIOS over TCP/IP on both machines, permissions granted for shares etc.
-In the regestry and changed the nodetype from unknown to hybrid
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters
    Rt. mouse click and select New > DWORD Value
    Name it 'NodeType' (without the quotes)
    Rt. mouse click on it and select Modify
    Set Value Data to '8' (no quotes)
    Leave Base alone. 'Hexadecimal' should be selected
      M$ docs refer to 1 as type "B", 2 as type "P", 4 as type "M", and 8 as type "H"
      What this basically means is different ways of resolving netbios names.
      1 = broadcast. The host sends a broadcast and the nodes which knows the ip of that name answers.
      2 = peer. Sends the request directly to a wins server which looks up the name.
      4 = multi node. I don't really remember but I think it starts with broadcast and if no answer does a      
            direct lookup from a wins server.
      8 = hybrid. Not sure here either, but I think it starts with a direct request to the wins server and if    
           the server is unable to resolve the name it does a broadcast.
-Disable simple file sharing (well it was already disabled, but I double checked).

After everything worked I relaunched the Kiero personal firewall, and it still worked, so I'm keeping the
firewall active.  I installed Kiero on the other machine because I figure it best to have the same firewall
application on both machines.

Philip

Offline kemelinux

  • Newbie
  • *
  • Posts: 1
  • Karma: +0/-0
    • View Profile
Networking 2 windows xp
« Reply #199 on: February 15, 2006, 12:55:07 PM »
After installing a Windows Update (via the automatic update) I was unable to access my XP Pro machine via the network. Just before the update there were no problems connecting to this machine.

In the end I found out that my Windows XP firewall caused the problem.
But I NEVER enabled this firewall as I have a 3rd party firewall. When I tried to open the Firewall in the control panel I got an error saying that the service wasn't running. It failed to start the service. So I thought that the firewall was disabled. I started the Firewall service myself from within Services (Adm. Tools). Now I was able to see my Windows Firewall and it was ENABLED !

So, I disabled it and now I am able to access my shares & printer.