Post by: ctm007 on November 09, 2003, 06:32:42 AM
Places" although I can see them from both computers. The error message is
\\Downstairs 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. The network path was not found." This error
message is on both computers. The host computer is a Windows XP Home
operating system and the second computer is a Windows XP Professional
operating system. The 2nd computer is named downstairs and the 1st (host) computer is named upstairs. I get the same error message on both computers; that is, the downstairs computer says "\\Upstairs is not accessible......
I am the administrator and I rebooted both computers and log in as the
administrator. Any suggestions?
Carl
Post by: Guest on November 09, 2003, 08:29:03 AM
Post by: Guest_ctm007 on November 09, 2003, 08:31:44 AM
Thanks, I'll give it a try.
Carl
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />
Post by: Guest_ctm007 on November 09, 2003, 11:01:34 AM
Carl
Post by: Guest on November 09, 2003, 11:16:46 AM
Post by: Guest_ctm007 on November 09, 2003, 06:32:06 PM
I would like to start over. Do you know how I can undo the folders that do show but I cannot access. When I try to right click on the network folder, I get that error message and cannot proceed. I'll like to just undo it all and start over.
Carl
Post by: Guest on November 11, 2003, 07:57:18 PM
Post by: kalvie on November 11, 2003, 09:38:19 PM
Itunes gives no error, and Win gives some "may not have permission..." thing.
Can you help me too?
Thanks!
Post by: pierroz on November 13, 2003, 01:17:00 AM
Post by: Dougal on November 13, 2003, 09:07:58 AM
Do you have any firewall or anything like Norton Internet security?
Post by: satnam on November 14, 2003, 05:45:14 PM
Post by: ross on November 14, 2003, 06:13:15 PM
Post by: matterdaddy.com on November 14, 2003, 06:18:21 PM
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 by: matterdaddy.com on November 14, 2003, 06:20:23 PM
Post by: ross on November 14, 2003, 06:25:23 PM
Post by: Biju Jacob on November 18, 2003, 02:21:46 AM
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 by: Guest_Richard on November 22, 2003, 03:13:12 PM
Post by: Guest on November 27, 2003, 09:01:37 PM
Post by: Guest_Mike on December 02, 2003, 09:02:23 AM
I'm running a DLink wireless network as well, that was not the problem.
Post by: Guest_Larry on December 02, 2003, 10:39:41 PM
I am having the same problem. I have 2 computers both using XP pro. I have a Linksys WRT54G router. Both computers are accessing the internet okay, but I can't seem to share any files between them. I keep getting the same error that everyone else here is getting.
I tried Ross' fix but that didn't help. My main computer can ping my remote computer, but not vice versa.
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' />
Post by: Guest_Larry on December 03, 2003, 06:24:55 PM
I uninstalled ZoneAlarm. Even though it wasn't actually running, apparently it still loads something at startup that prevents the networking from working. Some sort of vector monitoring or something. I knew I was on the right track when during the uninstall it warned me that it was shutting something down!
This was after I did Matter Daddy's and Ross' solutions, so I don't know if they were part of my solution or not, but they didn't hurt.
Hope this helps someone who was as frustrated as I was.
/unsure.gif\' class=\'bbc_emoticon\' alt=\':unsure:\' /> Good Luck!
/tongue.gif\' class=\'bbc_emoticon\' alt=\':P\' />
Post by: Guest on December 07, 2003, 02:10:49 PM
All this leads me to believe that the problem is purely with the xp machine and how it is set up, for some reason. Otherwise, I would be able to access the shared files of the xp machine through network neighborhood while on the xp machine.
I have shut off the firewalls on both machines. I have checked to make sure that the folders have sharing enabled, etc. My setting is "hybrid" (with reference to a previous post here). Browsing is started on "services" on the xp machine, and I changed to netbios over ip etc. as mentioned previously. Nothing works. Weird.
Post by: cprgmr on December 10, 2003, 07:27:57 PM
/smile.gif\' class=\'bbc_emoticon\' alt=\':)\' />
Post by: Guest on December 12, 2003, 02:37:13 AM
I had a similar problem. It took me a whole weekend to fix it. Here's what I did
On the XP machine that does not work.
Try
start
run
command
I have exactly the same problems. I'm sure it has something to do with the DHCP server on my ADSL router not set up properly but the following worked for me. I got this off computing.net
---------------
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
Post by: Guest_Peter on December 24, 2003, 06:16:13 AM
I uninstalled ZoneAlarm. Even though it wasn't actually running, apparently it still loads something at startup that prevents the networking from working. ...
This was after I did Matter Daddy's and Ross' solutions, so I don't know if they were part of my solution or not, but they didn't hurt.[/quote]
Looks like this problem is solved in many ways, but special thanks to Larry for posting his solution path which matched mine exactly.
I learnt a few things.
(1) search for the specific error message rather than "home network xp win98" or side issues like "Spooler SubSystem App has encountered a problem" both of which lead down to many hours of clicking what should not be clicked.
(2) If I find myself needing to do things to the registry or reflashing a modem to fix a problem, chances are there's a simpler solution.
I loaded ZoneAlarm because I was told I needed it. Like a lot of anti-virus software, it turned out to cost me more time than a virus or even a hack, so I turned it off (XP's Internet Connection Firewall and the modem router seem to cope just fine).
But months later, there it is lurking in the background, completely hidden and causing problems. Who'd have thought? I would not have picked it up but for Larry's posting.
(4) read the whole thread before implementing anything!
(3) posting the solution helps others!
Cheerio.
Post by: alexander on January 15, 2004, 04:35:38 PM
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.[/quote]
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.
cheers&alex
Post by: Guest on January 17, 2004, 04:47:49 PM
Post by: Guest on January 20, 2004, 12:24:53 AM
Check out Ross' link on the frist page for a quick check and possible fix.
=)
Post by: Fist of Fury 2k4 on January 20, 2004, 07:00:56 AM
You can get way too involved in a problem and miss the obvious.....The assumption that everyone knows what NFTS,WINS etc. means would drive you CRAZY.........Microsoft language is so far up their backside normal people cant understand what the heck they are talking about half the time LOL.....before you try any fancy stuff that might lead to you getting into even more trouble do this...............................Go to computer 1 and open control panel and double click "user accounts"..............double click computer administrator (your picture) and then "change my name"........put in the letter........ m.......................go to change my password type in the number 4....................restrt your computer if asked..........................go to computer 2 and do exactly the same.....if given the opportunty tick any box that says remeber my passwrd.......................if this work for you it will automatically let you go from one computer to the other without enterering any name or password.............probably cos they are bothe the same........ who knows.
BTW the letter "m" and number "4" can be changed to anything you like at anytime.
Post by: Anello Giovanni on January 24, 2004, 01:15:23 AM
I have a similar problem. I have 5 computers on a network. Three are running W98 the other two have XP Pro. The network is set up as a peer to peer network. Each of the five computers have identical user accounts and passwords and all have NetBEUI installed. Each computer shows up in the Network Neighborhood/Network Places of all five computers. However, when I try to view shares from the XP boxes it says "Access Denied" but shows the Shares from W98 Boxes fine.
The weird thing about it is if I know the EXACT share names on the XP Boxes and manually enter them in for mapped drives on the other computers, the mappings work fine. As soon as I retrun to Network Neighborhod/Places I get "Access Denied" again. I am currently using the mapped drive workaround but it is a pain to manually map new shares to four different computers.
Anyone have any ideas on how to fix it?
Anello
Post by: MikeC on February 03, 2004, 11:28:12 AM
MikeC
/wink.gif\' class=\'bbc_emoticon\' alt=\';)\' />
Post by: Michael on February 04, 2004, 12:30:54 PM
Post by: SirGawain on February 06, 2004, 05:26:14 AM
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.
Happy networking
http://www.ddc.co.za/ (http://\"http://www.ddc.co.za/\")
Post by: Vorhenze on February 10, 2004, 10:54:38 PM
THANKS. I knew this solution you mention had solved my problem in that past, but I lost that link. I just spent an hour trying to find this solution again. And it worked again!
Post by: terahari on February 28, 2004, 12:49:50 AM
I had been having similar problems. Finally I figured out that my antivirus is the cause of the problem.
My antivirus was configured to run Firewall and holding all the networking packets. When I stopped the firewall I was able to access my network without any problem.
My Antivirus program is PC-Cillin 2000.
Good luck.
Terahari
Post by: terahari on February 28, 2004, 12:51:30 AM
Hari
Post by: John Rigali on March 15, 2004, 12:25:48 PM
Several of you seem to have abandoned your firewall software. It seems that you were daunted by network problems, and figured that firewalls just aren't worth the hassle. They are. Let me give you a little guidance:
1) Set up your network first, and prove to yourself that it's fully functional. If any of your PCs have firewall software already, disable that software until full network functionality is proven.
2) Deploy your firewall software on one PC at a time, and ensure that it is properly configured on that PC before deploying on the next one. If any of your PCs had firewall software before you got to this step, enable that software on one PC at a time, ensuring that each PC's firewall is properly configured before moving on to the next one. It's very difficult to troubleshoot network problems when one has two or more PCs with improperly configured firewalls (and this is exactly what some of you encountered).
Personally, I don't like the Internet Connection Firewall built into Windows XP. It can't be configured to suit one's needs or wants. Because it doesn't generate any reports, its effectiveness can't thoroughly be known. I use and recommand the ZoneAlarm family from Zone Labs:
A) It has an intuitive and uncluttered interface.
/cool.gif\' class=\'bbc_emoticon\' alt=\'B)\' /> It can be installed and configured relatively quickly.C) It generates an activity report so that one can see what is blocked and what is allowed.
D) It monitors outbound traffic (which can be generated by viruses and spyware) as well as inbound traffic -- the mark of a good firewall.
E) It can be configured to automatically check for updates, upon which it notifies the user.
F) It is rated the best family of personal firewalls by more IT reviewers and pundits than any other family of personal firewalls.
G) There is a free edition for personal use.
That's my two cents' worth.
jarigali at bigfoot.com
Post by: Guest on March 23, 2004, 05:30:32 PM
and it will solve...
Post by: rambler on March 25, 2004, 04:04:07 PM
Post by: Willie Wheeler on March 27, 2004, 03:57:21 PM
/tongue.gif\' class=\'bbc_emoticon\' alt=\':P\' />
Post by: Guest on April 01, 2004, 04:54:24 PM
Post by: Anshul on April 03, 2004, 09:14:17 PM
/blink.gif\' class=\'bbc_emoticon\' alt=\':blink:\' /> , to transfer files. All of them are compatible with each other, since I use SmartFTP on my Pavillion computer and CuteFTP on the other computer, and it takes only some modest brains /unsure.gif\' class=\'bbc_emoticon\' alt=\':unsure:\' /> to work with FTP, and the transfer rate is around 10MB/s. But FTP didn't seem to work either, which i figured out was because my node type on the other computer was unknown. So I followed Ross's advice of changing my Node type to Hybrid on both computers. This solved the problem, I can see both computers on the Workgroup, and now my FTP works fine. I haven't tried the Network Set Up Wizard in WINXP. Before I couldn't see my other computer on the work group, I kept getting the perimission error. Now I can see both my computers on the workgroup. /tongue.gif\' class=\'bbc_emoticon\' alt=\':P\' /> /biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> So just try changing both node types to Hybrid, and use FTP if u just want to share files.
Post by: Anshul on April 03, 2004, 09:18:45 PM
/blink.gif\' class=\'bbc_emoticon\' alt=\':blink:\' /> , to transfer files. All of them are compatible with each other, since I use SmartFTP on my Pavillion computer and CuteFTP on the other computer, and it takes only some modest brains /unsure.gif\' class=\'bbc_emoticon\' alt=\':unsure:\' /> to work with FTP, and the transfer rate is around 10MB/s. But FTP didn't seem to work either, which i figured out was because my node type on the other computer was unknown. So I followed Matterdaddy.com's advice of changing my Node type to Hybrid on both computers. This solved the problem, I can see both computers on the Workgroup, and now my FTP works fine. I haven't tried the Network Set Up Wizard in WINXP. Before I couldn't see my other computer on the work group, I kept getting the perimission error. Now I can see both my computers on the workgroup. /tongue.gif\' class=\'bbc_emoticon\' alt=\':P\' /> /biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> So just try changing both node types to Hybrid, and use FTP if u just want to share files.
Post by: rKayd on April 10, 2004, 05:35:21 PM
Does anyone have an idea as to why the NodeType in the registry doesn't change the node type to Hybrid? the value is set to 8 (hex). On my laptop there is no registry setting for NodeType but yet it gives Hybrid as the node type in ipconfig.
As soon as I get a certain program disk I plan to reinstall Windows XP on my desktop. It's very possible there are corrupted files on it and that may correct my problems. (Don't take this as a suggestion to fix this problem - I am doing this for other reasons and just hope it will also help this.)
Post by: kc on April 13, 2004, 02:50:02 PM
Since one of the computers was brand new (and was actually able to share files with my linux machine for awhile) I did a full reinstall of windows xp. Reinstalling windows xp nor restoring to an earlier version did NOT fix the issue.
I am going to try out the fixes outlined above. It is ridiculous that we are hacking our computers just to share files within a small home network. This is something microsoft should be fixing rather than developing longhorn (i take offense to them naming the next os longhorn).
Another FYI, my linux machine (samba) tells me that the SID is not accessible. This sounds like a firewall issue to me. However, as far as I know, the only firewall on my network is the DLink router connected to the internet. I figured this is the only firewall i need. I loath to disable it for any reason.. but Ill give it a shot. I allowed full communications for the ip addresses 192.168.0.100 to 199 (my computers being in that range) but that still didnt fix it.
kc
PS hook em horns.
Post by: oh my god... on April 13, 2004, 08:17:36 PM
Now I am happy and all is good in the world.
Take care!
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />
Post by: Steve C on April 20, 2004, 08:32:31 AM
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.
Post by: Guest on April 21, 2004, 10:15:26 AM
currently my 98 machine says Broadcast and my XP machine says Hybrid and the XP machine is still denied access to the 98 machine's shares...
Post by: larry12275 on April 22, 2004, 12:08:18 AM
Post by: Bob on April 22, 2004, 12:39:31 AM
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!
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />
Post by: The_Unknown on April 23, 2004, 12:35:15 PM
Post by: Tino on April 30, 2004, 03:16:39 PM
Post by: Matthew on May 01, 2004, 10:11:33 AM
Post by: Guest on May 02, 2004, 08:21:33 AM
thanks
Mikeo
Post by: Guest_peter on May 13, 2004, 05:47:47 AM
Thx Peter
Post by: Guest_Lars on May 13, 2004, 12:40:22 PM
for you that still struggle with this problem, go control panel, my network connections, rightclick the LAN connection, click properties, click on the advanced tab, turn OFF firewall on all computers!
Lars
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> /laugh.gif\' class=\'bbc_emoticon\' alt=\':lol:\' /> /tongue.gif\' class=\'bbc_emoticon\' alt=\':P\' />
Post by: Guest on May 18, 2004, 02:50:04 PM
Post by: Jonathan on May 25, 2004, 10:35:02 AM
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.
Post by: Guest on May 31, 2004, 04:33:23 AM
Post by: eric on June 01, 2004, 07:07:13 PM
that solved it thnx man
Post by: BigManel on June 02, 2004, 04:05:18 PM
However... I was able to get to understand a little bit of the file and printer sharing protocol. At least the part where browsers get elected and so on... I even went so far as to edit the registry to make a windows95 box, I have working all the time as a print server, the browse master
Suddenly, possibly due to the installation of Norton SystemWorks & Internet Security, some parameters must have gotten confused
/tongue.gif\' class=\'bbc_emoticon\' alt=\':P\' /> (Micro$oft style!)However, I still don't get WTF that NodeType parameter does... But it does it good!!
Big thanks matterdaddy!
(just some key strings for people with simmilar problems to find this resource)
The network path was not found
The list of servers for this workgroup is not currently available
Network Neighbourhood
Post by: Iibuzne on June 02, 2004, 07:31:28 PM
I am having the same problem. I have 2 computers both using XP pro. I have a Linksys WRT54G router. Both computers are accessing the internet okay, but I can't seem to share any files between them. I keep getting the same error that everyone else here is getting.
I tried Ross' fix but that didn't help. My main computer can ping my remote computer, but not vice versa.
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' />[/quote]mate, your prob sounds identical to the prob i had, which i've just fixed courtesy of the articles, "Can Ping Other Client But Cannot See Workgroup or Any Computers in Entire Network" (http://\"http://www.experts-exchange.com/Networking/Q_20982831.html\"), and Connection to an office workgroup (http://\"http://www.experts-exchange.com/Operating_Systems/WinXP/Q_20792827.html\")
almost definitely firewall configuration &/or incomplete or badly configured installation of windows networking components. most common scenarios are discussed and solutions provided at above URLs.
oh yeah, you gotta sign up to see the answers, but it appears to be free
/smile.gif\' class=\'bbc_emoticon\' alt=\':)\' />iibuzne.
Post by: Nubreed on June 08, 2004, 01:38:33 AM
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.[/quote]
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
Cheers!
Post by: Guest on June 08, 2004, 01:45:36 AM
Post by: Mat128 on June 10, 2004, 07:04:00 PM
I disagree with you... My friend has a D-Link wireless network card and he spent about 2 hours on the phone and another 2 hours myself [with the techsupport]... The problem that was he fried the network card with a mac computer (well that's what he said...)
Post by: bryan on June 12, 2004, 03:02:20 PM
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?
Post by: Guest on June 19, 2004, 11:13:43 AM
Post by: Guest on June 19, 2004, 07:53:38 PM
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.
Happy networking
http://www.ddc.co.za/ (http://\"http://www.ddc.co.za/\")[/quote]
The winner! After performing every other fix described here and without success, I concluded with one desperate retry attempt at the solution described below. It worked. Earlier, when in Command mode pinging and net view-ing, I discovered that my computer's default username was "twster" (no friggin' idea why) but that I was listed as an administrator using my normal log-on name. So I did the ""Connect using a different user name" trick using my normal log-on username and it bloody well worked. Unbelieveable. Ten hours and a wasted Saturday later, thank you!
Post by: DougS on June 26, 2004, 06:56:27 AM
I can't map the drive because when I try to, there are no drives or folders in the other computer to map too!
I think I have all of the sharing on etc etc.
I've tried the Node type fix to 8 and in IPCONFIG it does say Hybrid (but in XP registry there is still a DHCPNodeType set to 4 which I can't delete - it just reappears every time!)
It's the total lack of understanding about all of these settings and what they do that limits any movement towards a solution.
I can access the Internet from both machines but can't get access from the laptop to the desktop to synchronise my files.
Post by: Guest on June 30, 2004, 03:51:12 PM
I had been having similar problems. Finally I figured out that my antivirus is the cause of the problem.
My antivirus was configured to run Firewall and holding all the networking packets. When I stopped the firewall I was able to access my network without any problem.
My Antivirus program is PC-Cillin 2000.
Good luck.
Terahari[/quote]
Bingo.
/smile.gif\' class=\'bbc_emoticon\' alt=\':)\' /> This was the fix I needed. Firewalls....
Post by: lost one on June 30, 2004, 08:28:38 PM
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' />
Post by: kabu on July 09, 2004, 04:57:54 PM
Both computers are able to ping each other and also in view workgroup computers they can see each other. On one computer the living room computer, it is able to access the bed room computer and view its files. But the bedroom computer when it tries to open the livingroom computer I get that famous message this thread is talking about. ...network resource etc.
These are the various methods I tried. ( did not fix my network probleem)
1. I verified that both are of node type "Hybrid"
2. They both belog to the same workgroup "Home"
3. The Bedroom PC gets a 169.xxx.xxx ip if the ip were to automatically assigned by the OS. So I changed it be 192.168.0.10 in the TCP/IP properties.
4. I turned off the DSL modem and the router and restarted the systems.
5. On the PC(Bed room) that was unable to access the other I deleted all the network stuff and added them back.
I am run out of ideas now .. what else can I try plz advice.
Post by: Hobbes on July 09, 2004, 10:54:30 PM
the above link should help i think. simply do what it says on that page. where it says "folder you want to take ownership of" it means your hard drive so right click on the c: drive in my computer etc.
Post by: Guest on July 22, 2004, 02:06:42 PM
I am having the same problem. I have 2 computers both using XP pro. I have a Linksys WRT54G router. Both computers are accessing the internet okay, but I can't seem to share any files between them. I keep getting the same error that everyone else here is getting.
I tried Ross' fix but that didn't help. My main computer can ping my remote computer, but not vice versa.
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' />[/quote]You need to enable "netbios over TCP/IP" on the windows xp machine
Post by: Jherek on July 25, 2004, 02:52:58 PM
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.........
Post by: Jherek on July 25, 2004, 02:59:40 PM
I also 99% solved the ICS problem also and can now share an internet connection using a firewall, the only problem is that my client PC will not see the connection until the server either connects or disconnects from the net and then its visible until the next reboot, which I can liuve with
The solution was to use kerio personal firewall v2.5 which allows you to set up a rule which allows all traffic from and 2 the network machine, in conjunction with setting up kerio 4 on the client, so that the client is protecting itself. Not the best of solutions but at least both are firewalled now, and ICS is working
I hate networking
/smile.gif\' class=\'bbc_emoticon\' alt=\':)\' />
Post by: mark_roberts_16 on July 26, 2004, 04:13:59 PM
Prior to this, I not only had problems seeing my system (an XP Pro laptop) from other computers, but also could not see my home LAN's samba print server.
Post by: NEED HELP! on August 04, 2004, 02:01:34 AM
Post by: PMan on August 04, 2004, 04:20:57 PM
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.
Post by: Guest_Jimmy on August 07, 2004, 05:20:03 AM
I tried all of the suggestions in this thread and nothing worked.
I came across the answer on another site, it is as follows;
Windows XP Home / "Access is Denied" Network Error
I've had the same problem as described above (\\Machine not accessible... access denied), using an XP Home machine as a server for my local network, and solved it this way:
Using Regedit.exe ...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
DWORD KEY "restrictanonymous" = 0
There are 2 enteries under restrict ; 1st is restrictanonymous and the other is restrictanonymoussam ; we have to change the value of both to 0
Then reboot. Notice that it lowers somewhat the security level for the anonymous logins on your XP Home PC.
This solution worked for me hope it helps
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> /ph34r.gif\' class=\'bbc_emoticon\' alt=\':ph34r:\' /> /biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />
Post by: Guest on August 07, 2004, 09:54:35 AM
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!!
Post by: Thankful Guest on August 09, 2004, 05:08:59 PM
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />
Post by: robert on August 12, 2004, 09:20:00 AM
I had a similar problem with two XP Pro desktops (recently upgraded from W2K). The usual "...not accessible ..." message, plus "Not enough server storage is available to process this command"
A quick search on google found this site http://ecross.mvps.org/faq.htm (http://\"http://ecross.mvps.org/faq.htm\"). Apparently Nortons AV stuffs up the IRPStackSize so that machines cannot connect. M$ Knowledge Base article 177078 http://support.microsoft.com/default.aspx?...kb;EN-US;177078 (http://\"http://support.microsoft.com/default.aspx?scid=kb;EN-US;177078\") provides the solution. Basically, use Regedit to increase ipstacksize to 15.
It worked for both of my computers. I can probably reactivate Zone Alarm now!
Its ridiculous that two such common programs can cause a major networking conflict, and that it takes such time and arcane measures to resolve!!!
Post by: Surya on August 15, 2004, 09:30:55 AM
Log in to system as Administrator and give the shring to the drives, u definetly solve the problem
Post by: Kiwi on August 16, 2004, 10:34:22 AM
Go to Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment, double click "Access the computer from the network" and click "Add User or Group" ... then set whichever Users/Groups you like who can access the computer.
That should do the trick... at least for me..
But there seems to be another problem. Everytime I log off, or restart the computer... the set value for "Access the computer from the network" has gone, I have to re-input the value again... and again.. and again...
Anyone knows how to set this value permanently?
Post by: Guest on August 18, 2004, 01:22:37 PM
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.
Post by: Whitley on August 20, 2004, 08:45:45 AM
I have three computers, a NT Server, XP Home, and a Win 98 computer. The NT 4.0 Server and XP Home ones get along fine as far as file sharing. The Win 98 one currently is seen much of the time but won't open up on either of the other 2 computers. I can't ping it either! But it shows up! I had this problem years ago when I had no firewall or virus program installed. I just decided that Win98 and XP just don't get along well! At times it would work?? But now, it won't work at all. I installed NETBUI on XP a while back and it worked for a while. This is not recommended or supported by Microsoft.
On the Win98 computer, I have selected "User Level" for sharing and noted the NT Server as where to find user groups, etc. When I boot the 98 computer, it says that NO DOMAIN SERVER is found and that network resources may not be available. So, I am doomed from the start! I don't understand why in the past I didn't have that problem! I have moved and didn't use the network for a while. I am just now hooking it back up.
And to make matters worse... years ago I got certified as an MCSE on 4.0 and used to know this stuff! The computing market crashed and I had to stay in construction! I just don't remember all this stuff. And I did have some confusion about permissions then too!
I don't think that I have a card or cable problem. I did put my own ends on the cable using the "B" designation, but I've done that before without problem.
I have disabled the Guest account. I have tried to take burdens off my poor computer by removing lots of stuff. I can now boot straight to Windows XP without having to select a user. I may try the Guest Account again to see if that makes a difference. Thanks.
Post by: Guest on August 23, 2004, 09:29:38 PM
I changed the node type with the problem PC, but in the mean time created another problem with the laptop and didn't realize it right away. Everything works slick-as-s#!t now. Thanks to the IT dept. at CMU. Thanks to my sponsers, and my loving wife for putting up with me while I pouted at the blank "My Network Places" window.
ok i'll shut up now.
Bferd [email protected]
Post by: Bferd on August 23, 2004, 09:32:30 PM
/wub.gif\' class=\'bbc_emoticon\' alt=\':wub:\' /> I changed the node type with the problem PC, but in the mean time created another problem with the laptop and didn't realize it right away. It's all good, everything works slick-as-s#!t now. Thanks to the IT dept. at CMU. Thanks to my sponsers, and my loving wife for putting up with me while I pouted at the blank "My Network Places" window.
/unsure.gif\' class=\'bbc_emoticon\' alt=\':unsure:\' /> ok i'll shut up now.
Bferd [email protected]
Post by: Mr_Loud_Trousers on August 25, 2004, 05:30:58 PM
I've been having a similar problem with my computer network as some of the other people here. I have two pcs running XP professional connected together via a switch. And the one PC is connected to the internet vie an ADSL modem. Ever since i set this up the file sharing has never worked and every now and then the internet connection sharing dies. At the moment it's not sharing at all. I've tried lots of the solutions on this thread and none seem to have fixed it. Whenever i try to run the "Setting up home/small office network" wizard it says it's had an error and i should run the wizard again.
Anyone got any ideas what this might be? As i said, it comes and goes, and i've fixed it in the past by going through the wizard and changing settings and then it dies again after a few months, but it's never anything specific.
Thanks!
Jamie
Post by: Guest on August 28, 2004, 01:46:22 AM
Dave.
Post by: Matthew on August 29, 2004, 11:57:49 AM
Post by: Joshua J. Slone on September 02, 2004, 03:42:04 PM
I've got the network working to a limited extent. We have three computers hooked toegether: 2 with Win XP Home, and 1 with Win ME. Both Win XP computers can access each other fine. And the Win ME computer can access everything on both of those computers fine as well. However, trying to connect to the ME machine from one of the XP machines brings up the old
Quote
\\Hippopc 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.
The network path was not found.
Nor can the ME computer be pinged from an XP computer, though the reverse works fine.
There's one solution often presented here that seems like it might work (since I can't say otherwise yet), but haven't been able to really try. This XP machine has node type Hybrid, but the ME machine has node type Broadcast. I've looked at the registry modifications you have to make... and not all those keys are there in ME. I tried adding them anyway, but that did nothing. I tried looking on MS's site and they showed an analagous change to make for Windows 95... but that didn't change it either. The ME machine is still set to node type Broadcast and I'm not sure why.
Post by: Guest on September 02, 2004, 04:34:44 PM
/tongue.gif\' class=\'bbc_emoticon\' alt=\':P\' />
Post by: Karen on September 04, 2004, 01:32:51 PM
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.
Happy networking
http://www.ddc.co.za/ (http://\"http://www.ddc.co.za/\")[/quote]
This solution seems to be the exact problem I am experiencing. I mapped a network folder to another drive with my current username and no problem accessing the mapped folder. But, how do I fix this so I can see the entire network? I can't get see anything on the network at all (no users, just the error). I don't want to have to map every folder.
Can I fix my username or restore it or something? Please Help!!
/blink.gif\' class=\'bbc_emoticon\' alt=\':blink:\' /> Karen
Post by: bosco on September 04, 2004, 02:55:17 PM
Post by: Guest_Steve on September 04, 2004, 06:02:48 PM
Post by: mostafa on September 05, 2004, 12:55:49 AM
Places" although I can see them from both computers. The error message is
\\Downstairs 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. The network path was not found." This error
message is on both computers. The host computer is a Windows XP Home
operating system and the second computer is a Windows XP Professional
operating system. The 2nd computer is named downstairs and the 1st (host) computer is named upstairs. I get the same error message on both computers; that is, the downstairs computer says "\\Upstairs is not accessible......
I am the administrator and I rebooted both computers and log in as the
administrator. Any suggestions?
Carl[/quote]
I have the same problem in my network.
Do you know how can i solve it?
Thanks
My Email: mostafa_vaghefiEmail Removed
Post by: Mario on September 09, 2004, 10:44:51 PM
/ohmy.gif\' class=\'bbc_emoticon\' alt=\':o\' />
Post by: Guest on September 10, 2004, 07:34:20 PM
[size=8]PROBLEM SOLVED by disabling the fire wall on the server computer [/size=8]
Post by: Homeycheese on September 12, 2004, 11:39:04 PM
LF
/blink.gif\' class=\'bbc_emoticon\' alt=\':blink:\' />
Post by: Giles K on September 15, 2004, 02:48:46 PM
AFAIAA hybrid is a better general purpose setting than broadcast in that it will also work in a WINS server situation (i.e. using Domains rather than Workgroups?)
Thanks to all who have contributed suggestions. I had tried many other things - this was the last one on the list! It's easy to see if the setting is correct by running the IPCONFIG /ALL command from a command window prompt.
BTW, LF - the reason you cannot connect to a machine in the way you were trying is that you can only connect to a shared folder on a disk on the remote machine (could be the whole disk). So the format \\computername\sharename is always required. sharename will be the name given under the "Share Name" box in the "Sharing and Security" dialog (XP).
Post by: Giles K on September 15, 2004, 02:55:40 PM
System error 53 has occurred.
The network path was not found.
and
This computer name is invalid.
More help is available by typing NET HELPMSG 2351
(I got the last one by trying NET VIEW 192.168.0.2 - which was the IP address of the share PC)
Post by: Giles K on September 15, 2004, 02:59:11 PM
Post by: MABE on September 16, 2004, 11:20:50 AM
I have experienced similar troubles about the network settings, I have not found any solution yet.
I have a PC with Windows ME connected to a Linksys WRT54G, I have one printer installed on the ME.
My (wireless) laptop runs XP
I have change the node type in the XP to hybrid, also I have enabled NETBIOS over TCP/IP. Also XP firewall desable.
In the ME the node type is Broadcast (I haven't found the way to change it).
When created the network on XP, created the disk and run it on the ME, same Workgroup. -Printers and folders specified as Shared. I also specifiacally in share the printer under Printer Properties -So the "hand" is under the printer"
From the XP I can see the ME in My network places, I see the Group and the ME, however I cannot access anything else, I cannot see the printer when addig it. I cannot ping the ME machine!
From the ME I cannot even see the group, so I cannot even open the folders that are share under XP. I can ping the XP machine!!
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' /> Mabe
Post by: HIRichard on September 20, 2004, 11:10:01 PM
Post by: Stan Grz on September 27, 2004, 07:10:33 AM
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> 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 (http://\"http://support.microsoft.com/?kbid=318030\") 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.
this solved the problem I've been working on for 2 weeks.
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />
Post by: same router, same problem on September 28, 2004, 06:51:27 PM
I am having the same problem. I have 2 computers both using XP pro. I have a Linksys WRT54G router. Both computers are accessing the internet okay, but I can't seem to share any files between them. I keep getting the same error that everyone else here is getting.
I tried Ross' fix but that didn't help. My main computer can ping my remote computer, but not vice versa.
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' />[/quote]i tried every fix listed here and on Microsoft and have no firewalls running... I cannot ping the computers in the workgroup or access the computers in the network. i reinstalled the adapters and everything... no help
Post by: Eureka! on September 28, 2004, 07:25:05 PM
I didn't realize it was still running until I figured I'd try complete removing Zone alarm... look for zauninst.exe in your Zone alarm directories!
I have probably wasted days and days on this!
I also have disabled Net Firewall on my XP2 system but will try turning it back on to see if that was having effect.
Post by: ParadiseCowgirl on October 01, 2004, 10:23:21 PM
THANKS!
I was going batty!
(PS: I have no problem (now) just entering \\computername and seeing all the shared folders)
Post by: colonel on October 08, 2004, 12:07:21 AM
Post by: reuben on October 12, 2004, 12:23:45 AM
I can successfully ping either computer from either one. I can print from my wireless laptop to my printer which is connected to my other PC that is connected through the LAN. I can see both computers in My Network Places. When I try to copy a file or for some folders even open them i get an error:
[color=\"red\"]\\MyNetwork\folder is not accessible. You may not have permissions to use this network resource. Contact the administrator of this server to find out if you have access permissions. Access is denied.[/color]
It sounds like I'm doing better than most people on this string in that I can see and ping the other computer. Both computers are set to "hybrid", NetBIOS is enabled. I have no firewalls, and the XP firewall is disabled. I run an anti-virus program called Avast. I've disabled it to see if it would make a difference but it didn't so I still run it.
I once had Zone Alarm running on my LAN PC but have long since removed it. I've run the Network Setup Wizard many times resetting the network over an over several times.
I installed Windows XP Service Pack 2 and actually saw a benefit to this right away as before I wasn't even able to see my computers in My Network Places, now I can. I have user accounts with same name and passwords and as administrators. I've changed permissions to allow for everything to be read - write - execute on all the shared folders. File and Printer Sharing is enabled.
I'm at wits end in trying to solve this. I just want it to work and I'm at the point of considering an OS reinstall on my LAN computer as it hasn't had one in several years. I'm open to more suggestions, and hope somebody has a similar problem and have been able to get through it.
Post by: Guest on October 16, 2004, 06:26:31 AM
Post by: vortexae on October 18, 2004, 12:59:42 AM
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.[/quote]
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,
--
Niki
Post by: vortexae on October 18, 2004, 09:12:48 AM
I am a moron. Of course I meant "Deny access to this computer from the network", not "Deny Logon Locally". Durh.
Neither computer has passwords set up. I am experimenting with creating a passworded logon on the XP Pro desktop, and mapping to that drive as that user and password from my XP Home laptop, and then adding "Guest" back to the access key here mentioned. I'm not sure what that will do to printer sharing, though...
Post by: paul on October 18, 2004, 11:47:46 PM
Post by: Guest on October 25, 2004, 03:28:16 AM
silent blocking....ie why tell another potential hacker etc, that you exist if you arent sharing anything anyway...)
Post by: Steve Low on October 25, 2004, 08:25:18 AM
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.[/quote]
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.
cheers&alex[/quote]
I've struggled with these problems for weeks--spending countless hours trying to resolve them.
Replacing "peer to peer" with "hybrid" did the trick.
Thanks to all for the great guidance.
Steve Low
Post by: Guest on October 27, 2004, 12:07:44 PM
worked for me (at least for one direction)
Post by: jagdwire on October 27, 2004, 03:19:30 PM
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> 1.http://www.mp3players4free.com/default.aspx?r=4070
2.http://www.mp3players4free.com/default.aspx?r=14984
3.????????
4.????????
5.????????
To be part of this conga line, e-mail me at habjabEmail Removed with the following info:
1. referral link
2. offer completed
3. e-mail you used to sign up for the FREE mp3 player
PS: Do not e-mail me if you don't use these referral links to sign up! Also, YOU MUST SIGN UP UNDER THE FIRST LINK OR YOU WILL NOT BE ADDED!
Thanks for your time and good luck!
Post by: Mossbrook on October 28, 2004, 08:10:58 AM
I first had discovered that although XP pro would not allow access through the workgroup,
(error: You may not have access...) I could access the various workgroup computers by entering their IP in the address bar of a folder on XP pro. ie
\\192.168.1.103 or whtever had been asigned by the router.
but the computer "\\name" would not work in the address bar. Even if I could call up the workgroup (sometimes possible), clicking on the computer name would not allow access.
I could not understand why XPpro would see the computer but not record
Using Search/files and folders/computers on the network/computer name
The computer was found. s
Still, I could not get to it by clicking on the found link in search.
However, I made a shortcut of the found link on my dedsktop. Then clicking this desktop shortcut, I was taken to the computer.
I could then enter "\\computer name" in the address bar and go to the chosern computer.
Following this, clicking on the workgroup, now found the computer and allowed access.
Go figure..
I have been struggling with this for a month and reading every internet search refference to "you may not have permission.."
so I had done all the suggestions
enable NetBios
disable simple file sharing on XP pro
All using same workgroup name
All with shared folders available.
I did not disable the firewall in SP2
I did discover that the linksys DSL wireless router keeps track of what IP it has assigned to a given computer and always reasigns the same IP to that computer regardless of which computer logs on first. Unless you go to the list under Status, Local Network, DHCP list and delete the entry. The router apparently holds the number in reserve for 24 hours at which time if there has been no return logon, the number expires and becomes available for reassignment.
Mossbrook
Post by: BoomZilla on November 07, 2004, 02:01:34 PM
Also - many new PC's these days (Dell, Sony, HP to name a few) include Norton AntiVirus software, which has its own firewall. Turn that off too!
Post by: Guest on November 13, 2004, 12:07:40 AM
I just spent 2 weeks on this, and it was that simple. As soon as I closed Zonealarm, both computers happily saw eachother. Of course, I now have to install proper firewall capabilities...
Post by: EENO11 on November 17, 2004, 06:31:48 AM
I tried all of the suggestions in this thread and nothing worked.
I came across the answer on another site, it is as follows;
Windows XP Home / "Access is Denied" Network Error
I've had the same problem as described above (\\Machine not accessible... access denied), using an XP Home machine as a server for my local network, and solved it this way:
Using Regedit.exe ...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
DWORD KEY "restrictanonymous" = 0
There are 2 enteries under restrict ; 1st is restrictanonymous and the other is restrictanonymoussam ; we have to change the value of both to 0
Then reboot. Notice that it lowers somewhat the security level for the anonymous logins on your XP Home PC.
This solution worked for me hope it helps
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> /ph34r.gif\' class=\'bbc_emoticon\' alt=\':ph34r:\' /> /biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />[/quote]This one worked for me as well...after trying all the other fixes without success.
Thanks!
Post by: Guest on November 20, 2004, 04:58:09 PM
Thanks for the help!!!!
/laugh.gif\' class=\'bbc_emoticon\' alt=\':lol:\' />
Post by: avstan on November 23, 2004, 03:53:44 PM
I have read all the posts and checked or tried about every solution listed without success.Let me explain.
I have 2 PC's, A & B, that are networked through a Linksys router. PC A runs XP Home with SP2 and B runs XP Pro without SP2. I am able to see the network Icons from either PC and access the Net with either. I have all firewalls, Antivirus, and Pop ups disabled. I am able to access PC A by using the network icon. I am able to see B's icon but unable to access it using its icon. I get that old message, "You must not have permission.....etc". I am able to see both PC's using the cmd "Net View". I am also able to access B's drive by entering " \\computername\vol 1 ©\" on the RUN line. Need some more ideas. I have been fightin gthis for weeks. Thanks in advance for any ideas.
avstan
/ph34r.gif\' class=\'bbc_emoticon\' alt=\':ph34r:\' />
Post by: flisher on November 29, 2004, 04:05:13 PM
On the computer that IS able to access shared files from the second computer,
but is not giving user permission to the second computer, download and install the:
Windows Server 2003 Resource Kit Tools
http://go.microsoft.com/fwlink/?LinkId=4544 (http://\"http://go.microsoft.com/fwlink/?LinkId=4544\")
Once the install has finished, go to:
Start | All Programs | Windows Resource Kit Tools | Command Shell
Enter these commands, exactly as they appear here:
net user guest /active:yes
ntrights +r SeNetworkLogonRight -u Guest
ntrights -r SeDenyNetworkLogonRight -u Guest
then try to connect to the drive/files from the second computer. No need to reboot.
Post by: superman40 on December 06, 2004, 08:09:10 AM
/wink.gif\' class=\'bbc_emoticon\' alt=\';)\' /> Not enough server storage is available to process this command.
Not enough memory to complete transaction. Close some applications and retry.
These error messages can indicate the IRPStackSize bug on the other machine (the server that has the share). On that computer open the event log and check for event ID 2011. If this is present, it is a strong indication for this particular bug.
To repair it, you have to reset the IRPStackSize parameter back to its default value of 15 on the server where the share is.
HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Services
\lanmanserver
\parameters
Check for the presence of a value named IRPStackSize. If it doesn't exist, create it as type DWORD. With base set to decimal, enter the value 15.
Reboot the computer.
One frequent culprit is Norton AntiVirus, which tends to change this parameter.
Check also this Microsoft Knowledge Base article. It does not mention Windows XP, but applies to XP as well.
Antivirus Software May Cause Event ID 2011 (Q177078)
http://support.microsoft.com/?kbid=177078 (http://\"http://support.microsoft.com/?kbid=177078\")
Post by: Master Devwi on December 07, 2004, 10:27:57 PM
Post by: autavi on December 16, 2004, 07:35:19 PM
Post by: Guest on December 16, 2004, 08:07:29 PM
Quote
I don't think it's Norton (my firewall), because I've looked at it, and as far as I can tell, it's not blocking it. Shortly after my last post, my 98 started to not work. So now, it freezes up all the time, and I can only use it every once in a while.
Post by: Master Devwi on December 16, 2004, 08:11:26 PM
~ Master Devwi
Post by: Philbini on December 17, 2004, 01:13:49 PM
After banging my head long enough I came to the realization that I had tried every trick on every home networking tutorial guide I had found on the net. NONE of them worked. But all of them seemed to have inconsistencies with the way my system ran in the ways of what menus and options were available.
I am running two XP Home machines with SP2 installed connected with a switch. I had to go back into window setup and install components:
Start - Control Panel - (on the left) Add/Remove Windows Components - Networking Services - Details. Check the services you need. For me it was Peer to Peer. This didn't load by default when I applied SP2. Once this was in place -BAM- my connections are working, everything is visible, and I have every protocol available with no conflicts. I also made sure that Windows was completely updated and that my NIC drivers were the latest and greatest.
Post by: Guest_Billy on December 18, 2004, 12:11:00 AM
I CAN SEE ALL 3 pcs in the workgroup but can't access one of them
discovered it is because i was running BlackIce on that PC
disabled BlackIce and network works like a charm
Post by: argus on December 21, 2004, 03:01:59 PM
I tried all of the suggestions in this thread and nothing worked.
I came across the answer on another site, it is as follows;
Windows XP Home / "Access is Denied" Network Error
I've had the same problem as described above (\\Machine not accessible... access denied), using an XP Home machine as a server for my local network, and solved it this way:
Using Regedit.exe ...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
DWORD KEY "restrictanonymous" = 0
There are 2 enteries under restrict ; 1st is restrictanonymous and the other is restrictanonymoussam ; we have to change the value of both to 0
Then reboot. Notice that it lowers somewhat the security level for the anonymous logins on your XP Home PC.
This solution worked for me hope it helps
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> /ph34r.gif\' class=\'bbc_emoticon\' alt=\':ph34r:\' /> /biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />[/quote]Thanks very much. It was THE solution for my problem. I have a network of 3 machines (a XP, a W2k & a Red Hat 8.0. I could do nearly all the networking, but I could not print from the Red Hat to my printer on the XP (home SP2). From the smbclient command in RH I got also a kind of acces denied and also from my Wk2 machine. On the Wk2 machine, however, I could 'reach' my xp by just mapping a network drive and printersharing was no problem. Now it is soved after 3 weeks searching all the forums...... Many thanks and 'happy christmas from France"
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />
Post by: Guest on December 23, 2004, 02:42:52 AM
Post by: Guest on January 01, 2005, 03:23:03 PM
For both computers, I turned off the Microsoft Windows Firewall as follows:
[Start] -> [Control Panel] -> [Security Center] -> [Windows Firewall]
I then clicked on the Off circle followed by -> [OK] -> [X] -> [X] to get me back to my desktop. I did not reboot either computer.
In retrospect, I probably needed to turn off Windows Firewall for only the target computer, the one with the second disk drive (the D: drive) being shared.
Anyway, immediately, I could, with Windows Explorer, see the shared drive on the other computer and all of its folders and files. I had full read-write-copy and file modify capability just as if that shared drive was truly on the other computer. Problem solved!
Funny thing then happened. I turned back on the Microsoft Windows Firewall for both computers and that disk drive was still being fully shared as described above. I even re-booted both computers to double check. Yep, still shared. Problem still solved!!
A couple of days ago, I tried to access that shared drive again. Couldn't. I then checked the log of the Trend Micro Internet Security 11 firewall software running on that computer with that disk drive being shared. That log showed my "violation" attempt. I could tell by the time stamp. So, I turned off the Trend Micro firewall. Problem solved!!!
So, when I was through with that drive being shared across my Local Area Network (LAN), I just turned that non-Microsoft firewall back on to give me that added protection.
Hope this helps others.
Post by: NZOldFart on January 01, 2005, 07:16:08 PM
The XP Home machine is set up as the server with connection to the internet still using dial up. I have always been able to access the XP Pro machine from the XP Home - no passwords or anything required but could not get from the XP Pro to the XP Home machine - was getting the dreaded "You may not have access permissions ..... Network Path not found" message.
I have tried all the solutions in this thread and have finally managed to get rid of the "You may not have access permissions"message (God only knows which one actually did the trick) .......BUT
Now when I try to connect from the XP Pro machine to the XP Home machine I get a "Connect to Office"dialogue box (Office is the name of the XP Home machine)
which asks for a password. The actual text in the dialogue box is:
Connecting to Office
Username Office\Guest (this is greyed out - so there is no other choice)
Password
Now Guests don't have passwords so damned if I know. Can anyone help me with this? It's driving me up the wall!!
Thanks
Post by: Dave on January 05, 2005, 08:52:07 PM
i tried absolutely everything, from uninstalling fireewalls, to messing with local security policies, installing/uninstalling protocols.
in the end you're simple hack into the registry did the trick. i don't understand it but basically i don't give a damn.
strange though I would have thought there would be a better way to set HYBRID from within Windows than using regedit.
what a legend, make sure you guys try that suggestion first!
Post by: was frustrated on January 20, 2005, 10:36:12 AM
I did notice that for some reason, zone alarm switched (w/o my knowing) the attached nw adapter from its original trusted setting to internet. I just flipped it back and it works beuatifully.
Post by: was frustrated on January 20, 2005, 10:40:47 AM
Post by: Desperate 2 Network on January 22, 2005, 12:01:49 AM
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' /> I am able to ping both computers (computer A pings B and vice-versa). Computer A sees all shares, computer B sees none. Any advice?
Tks!
Post by: Guest_Andrew on January 23, 2005, 01:08:53 PM
Two of them are working fine, they are recognizing eachother etc.
These two are using Windows 98 & 95 - New computer, Windows XP Professional is bringing up an error message which says: "Homenetwork is not accessible. You might not have permission to use this network resource. Contact the administrator of the server to find out if you have access permissions."
Post by: Spinman on January 25, 2005, 12:35:09 AM
I think my problem is more basic...
2 computers loaded with XPhome SP2 over the weekend. Therefore a clean install on each - no accumulated garbage - no 3rd party software installed.
Computer "A" seems to have loaded properly (whatever that means) - when I check 'My Network Places' in windows explorer - I can see the shared folders from Computer "A" listed as a sub line - along with entire network\microsoft network\workgroup... (Computer "B" is not represented).
Computer "B" (my problem child) does not display the shared folders from Computer "B" under 'My Network Places'. As I drill down through the hierachy - I eventually get the message that others have reported about access being denied...
I have setup a USB wireless point on "B" and a PCI wireless point on "A". I am able to lock on to the signal and affect a peer to peer connection - but that is as far as I can get. "A" will not display any of the shared folders from "B" and "B" will not display any of the shared folders from "B" or "A".
Why is "B" not showing the shared folders under My Network Places?
BTW - in addition to the default shared folders - I have also established 2 slave drives as shared network devices - so they should appear as well...
Does this sound like a software problem? I can't imagine that it would be hardware related (defective part or irq conflicts, etc...)
Appreciate any thoughts...
/mad.gif\' class=\'bbc_emoticon\' alt=\':angry:\' />
Post by: Spinman on January 26, 2005, 05:29:56 PM
I booted into safe mode - at which point an unspecified device loaded.
Rebooted and returned to normal mode - no improvement.
Rebooted and returned to safe mode.
Reconfigured entire network settings in safe mode.
Renamed PC and Workgroup
Rebooted back into safe mode
Renamed PC and Workgroup
Rebooted back into normal mode.
System partially correct.
Followed networking instructions and downloaded registry patch @ careyholzman.com/net1.htm
Rebooted back into normal mode.
System stable and works perfectly (for at least the last hour).
Very strange....
Post by: myth on January 27, 2005, 12:32:47 PM
but related with the same error message..
My problem is rather that the computer with XP Home seems like it has
no "root dir" for users wanting to browse the computer.
If i specify the full path of the folder i want to access, it works fine.
But if i just double-click the computer icon, i get the error message.
Is there a quick and easy way to define this root-dir, or is it set
by one of the screwed up windows wizards?
Please let it not be that i have to enable guest account or something
sick like that to make it work.. I want to be able to use my computer fully,
since it's mine
/wink.gif\' class=\'bbc_emoticon\' alt=\';)\' /> Without having to enable stupid options like that..Other annoying things are the shared documents, shared tasks, and shared
printers and faxes folders, which are automatically shared..
These would also be nice to control, but this has do be done registrywise? or not?
I have read a lot of different problems now, and it seems like this area of
difficulties with file sharing is quite vast. Some firewall-related, some
group/user access related, and so on..
But i just have problems entering the remaning computer with a double-click,
instead of specifying the entire path.. So, how does the root-dir thingy work?
Do i need to h4xx0r the registry, or just enable some silly crap?
/smile.gif\' class=\'bbc_emoticon\' alt=\':)\' />
Post by: myth on January 27, 2005, 12:42:33 PM
\\Computer -> Error message...
\\Computer\Folder\ -> Works Fine...
\\Computer on the computer itself reveals the rootdir of the shared folders though.
\\Computer2 (mine) from \\Computer -> Works fine to!
So the problem is accessing \\Computer directly, without specifying subdirs,
from \\Computer2
I have read others with exactly this problem, but i have not read any
solution to the problem..
HELP! Any geeks around here?
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />
Post by: Dave C on February 03, 2005, 06:01:13 PM
I hope this helps someone else.
Post by: Eric on February 04, 2005, 08:52:24 PM
I tried almost everything possible, still was not able to get to one PC from the other, but no problem from the other to the first one.
I finally changed the registry entry, on the computer to which i want to connect to (the one I can't access)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
'restrictanonymous' set to dword 00000000 (which was set to 1 on that computer, and 0 on the other!).
Then, rebooted that computer.
After reboot, I could access both computers from any of the two.
Post by: maezee on February 10, 2005, 11:20:21 PM
After reading all the suggestions in this forum, I used the "Hybrid" suggestion in matterdaddy's post of 11/14/03. As it turned out, when I ran "ipconfig -all", my laptop was already shown as Hybrid, but the Desktop computer was "mixed" -- so I changed it, according to his directions. Still nothing.
Then . . . I went to the Laptop and turned off the firewall. I thought I'd disabled it before from a previous suggestion, but I had to go into the McAfee security program to REALLY turn it off.
Now . . . . at long last . . . my computers are communicating!! Ain't life grand!!!
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> Thank you , thank you, one and all for this great forum!! I'll be back -- but I hope not too soon!
/wink.gif\' class=\'bbc_emoticon\' alt=\';)\' />
Post by: Darek S on February 12, 2005, 10:06:25 PM
If you want to use the network for the sporadic file transfers, you can start your xp system in diagnostic mode with network acces to omit all the blocking walls.
Darek
Post by: Andrew on February 20, 2005, 02:56:05 PM
Post by: Andrew on February 20, 2005, 10:04:42 PM
I have 3 computers all running on Windows XP Home. I have a D-Link Wireless Router, with one of my desktops [A] connected to the router via ethernet. I have another Desktop connected via wireless with a D-link adapter. Then I have a Laptop on the wireless network via a wireless card as well. I can access Desktop from Laptop in Workgroup computers, and I can access laptop from Desktop in workgroup computers. However, Desktop [A] will not work!! I can see it in the workgroup computers on Desktop and Laptop, but on Desktop [A], I cant even view workgroup computers - not even itself! i click it, and it says i do not have permissions. I have tried everything!! Could someone please help?!?!
Post by: svbetsy on March 14, 2005, 02:42:32 AM
I have done everything recommended on this thread and zillions of microsoft troubleshooting guides and online guides, etc. Days and days of work, all to no avail. I might need to send my nice new laptop back--I can't use it with my other machine!
I have 2 Dell XPpro machines, a laptop and a desktop, networked via a Linksys wireless router. Internet works fine, machines both answer to pings, all of the user, IP, sharing, and node settings are correct. the guest user is now an administrator. The desktop has full access to the laptop's shared files, but the laptop can't access the desktop's shared files. Sometimes the desktop appears in the workgroup folder, sometimes it doesn't. When it does appear, I get a message saying that the computer is not accessible and that I might not have permission.
This is driving me be bonkers. Any suggestions would be greatly appreciated.
Svbetsy
/ohmy.gif\' class=\'bbc_emoticon\' alt=\':o\' />
Post by: svbetsy on March 14, 2005, 12:04:44 PM
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> I DID IT! YAY!!!!Okay, this was my fix...
I had to uninstall--completely--Norton Anti-Virus, reboot, and PRESTO! the share showed up in the workgroup. Disabling the Norton firewall didn't work, and I couldn't set an exception to allow access because the network wouldn't see it and I couldn't map. Uninstalling was the only way. Btw, in the process of rechecking that all the settings were still okay in hopes that the uninstall of Norton would work, I discovered that the File and Printer Sharing Protocol had turned itself off on the culprit computer, too--hmmm. Once I had the share showing up in the workgroup, I mapped it to an unused drive letter and enabled reconnect at logon. Repeated on the other computer. Then reinstalled Norton Anti-Virus and set the exceptions to include the new mapped drive on both computers. All working fine now.
I'M FREE! AND I DIDN'T EVEN HAVE TO PAY DELL $150 TO DO IT.
Great site, very helpful. Thanks.
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> SVBETSY
Post by: LJP on March 19, 2005, 12:35:46 AM
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
/tongue.gif\' class=\'bbc_emoticon\' alt=\':P\' /> 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.
Post by: Somebody on April 04, 2005, 04:07:01 PM
Went here to solve it..
http://www.michna.com/kb/wxnet.htm (http://\"http://www.michna.com/kb/wxnet.htm\")
Post by: Guest on April 17, 2005, 11:44:00 AM
Post by: Guest on April 19, 2005, 01:53:23 AM
http://service1.symantec.com/SUPPORT/nav.n...nav&svy=&csm=no (http://\"http://service1.symantec.com/SUPPORT/nav.nsf/5faa3ca6df6f549888256edd0061c0a4/f81c3db6d420729188256f5100062b90?OpenDocument&prod=Norton%20AntiVirus&ver=2005&src=sg&pcode=nav&svy=&csm=no\")
Post by: Guest on May 07, 2005, 05:55:52 AM
Select home network and then restart after. This set the Workgroup name to "WORKGROUP" on both computers and they can now see each other. They were both set to HOME before but could not see each other, the Wizard must of set something else or maybe only WORKGROUP will work.
Post by: True_Snake ([email protected]) on May 15, 2005, 07:28:06 AM
For XP PRO: Right click "MANAGE" , Expand the "SYSTEM TOOLS" category, select "LOCAL USERS AND GROUPS", click on "GROUPS", double-click "ADMINISTRATORS", press "ADD" on the window that pops up.
Under "ENTER THE OBJECT NAMES TO SELECT", type "Guest" and click "CHECK NAMES".
Once done, in the "ENTER THE OBJECT NAMES TO SELECT" box, you should see "yourcomputername/Guest".
Hope that helps.
Didn't need to add the Guest account in the welcome page or anything.
I love you guys
/smile.gif\' class=\'bbc_emoticon\' alt=\':)\' /> !True_Snake
Post by: dakila on May 17, 2005, 10:58:43 AM
If you can browse the computers but cannot access the shares/directory on it, try the procedure of SirGawain
Code: [Select]
http://www.thetechguide.com/forum/index.php?showtopic=9932&st=20this works well....
I'm running Windows XP SP2 on 6 workstations....
Post by: COOLER224 on May 18, 2005, 10:28:49 PM
found a super fix! Not a workaround but the true fix The one thing most overlooked did anybody have a virus or spyware in the past! this is a big problem out there. Here is the fix. first get rid of the spyware. pest control is the best I have found and scan for virus with the most updated software you have. Say what you will but norton with all its little glitches still is the best!
Go to regedit,
HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Control
\Lsa
Value name: RestrictAnonymous
Value type: DWORD
If the value is 1 or even 2, change it to 0, reboot and retest. If the problem is solved, leave the value at zero. If not, you can change it back if you like.
Check immediately afterwards and again after a reboot, whether the value changes back to non-zero on its own. If that happens, then you have to find the culprit, which can be spyware, a worm, or a badly designed security program. In this case this procedure most likely solved your problem, but then the bad software stepped back in and recreated the problem.
This help was found at : http://www.michna.com/kb/wxnet.htm (http://\"http://www.michna.com/kb/wxnet.htm\")
good luck!
Post by: Ryan. C on May 19, 2005, 07:16:24 PM
I am having the same problem. I have 2 computers both using XP pro. I have a Linksys WRT54G router. Both computers are accessing the internet okay, but I can't seem to share any files between them. I keep getting the same error that everyone else here is getting.
I tried Ross' fix but that didn't help. My main computer can ping my remote computer, but not vice versa.
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' />[post=\"12192\"]<{POST_SNAPBACK}>[/post]
[/quote]-------
Just run the "Set Up a Home or small office network" on both machines, then problem solve.
Post by: Guest_jayjay_* on May 26, 2005, 03:11:04 AM
Share ANY folder.
Try to connect to the computer again.
After you successfully connect, you can un-share the folder.
Worked for me.
Post by: Guest on June 02, 2005, 12:24:49 PM
Thanks
Post by: Guest on June 04, 2005, 11:59:32 PM
I would like to start over. Do you know how I can undo the folders that do show but I cannot access. When I try to right click on the network folder, I get that error message and cannot proceed. I'll like to just undo it all and start over.
Carl
[post=\"11971\"]<{POST_SNAPBACK}>[/post]
[/quote]
Post by: Guest on June 05, 2005, 02:11:03 AM
cannot find network path, it WILL NOT CONNECT!
i tried every fix on this board, HELP!
Post by: dakila on June 05, 2005, 04:22:28 AM
Code: [Select]
i am having a problem where i cannot acess my main computer on the network from my laptop or other desktop. i can access the two from my main computer, but when i view the workgrouips on the other two and try to access the main computer i get the error
cannot find network path, it WILL NOT CONNECT!
i tried every fix on this board, HELP![/color]Try mapping the shared folder you want to access. Right click the MyComputer>Map Network Drive, on the dialog box click Connect Using A Different UserName, Enter the username of the computer where the shared folder located. Browse the shared folder you want to map, if you can't browse, use UNC path instead. Click finish...
Works for me in several situations...hope this works for you, too...
Post by: mdavidjohnson on June 09, 2005, 03:21:59 PM
I'm experiencing a similar problem on a larger scale. For the past four years I've been running a Domain network that includes one NT4 Server (no service packs), 32 W2K Pro workstations, and 8 W98 workstations.
I'm in the process of replacing the entire network with 2 Dell Proliant 150s running Windows Server 2003 SP1 and 40 Dell Dimension 3000 workstations running WinXP SP2, all using the original Domain name.
I've reached the stage where I'm currently running the two new servers, two of the new workstations, and the forty old workstations. The old NT4 server is completely off line (there was no transition period - I just unplugged the NT4 and plugged-in the WS03s) and the servers are running in 2003 native mode.
The two new workstations access the servers perfectly. But the old workstations are almost all experiencing the "Network Path Not Found" error. They can ping the servers. They can see them and their shared folders. But they can't access those folders.
I'm thinking the problem is SID related somehow but I haven't found it yet. I'm going to try several of the ideas I found here and keep working on the SID angle too.
I'll post the results as I git 'em.
M. David Johnson
LAN Administrator
Maine Township, IL
Post by: ClemP on June 20, 2005, 12:47:37 AM
Today, suddenly, one of the desktops (my daughter's system) stopped communicating with the shared printer on the other desktop. I found that I could not see the printer and when I tried viewing "Workgroup computers" or clicking on the Workgroup name under "My Network Places/Entire Network/Microsoft Windows Network" I got the error message "<Workgroupname> not accessible..." Now I can see my daughter's system from the other desktop just fine and I can even see the shared folders and files on her system as well as the shared printer on her system. I just can't see the rest of the network from hers! I can ping the other desktop's IP address from the command line of my daughter's system just fine, also.
I did notice that the Node Type on my daughter's system is UNKNOWN and the Node Type on my desktop is PEER-PEER. I remember changing the setting on one of my systems months ago to HYBRID. I just can't remember which one it was.
It's late here now and I'm just not up to turning her system back on to try the registry change to HYBRID. I'll do it in the morning. But I just can't understand why it was working one minute and not the next. I know for a fact that she hasn't mucked around with her system or added any software to it recently.
If anyone else has had this type of problem (WinXP Pro Peer-to-Peer network working fine for long time then suddenly just one system can't see rest of network but others can see it), I'd love to know what you found caused it and what you did to fix it!
Thanks and sorry for the novella!!!
Clem Patafio
Post by: Guest_Alex_* on July 11, 2005, 04:23:22 AM
I have tried EVERYTHING in here. (I think!)
/dry.gif\' class=\'bbc_emoticon\' alt=\'<_<\' /> My problem is slightly different than most and sounds like one post a while back.
/sad.gif\' class=\'bbc_emoticon\' alt=\':(\' />I am on a network trying to put files onto a Win 2k machine from other machines running XP. I can see the file/folders on the 2k machine and have all the access rights set up. When I start copying (or cut/pasting) it works fine but ALWAYS cuts out before it's done -and gives me the error message this thread is famed for!
/mad.gif\' class=\'bbc_emoticon\' alt=\':angry:\' /> After that I cannot access the 2k machine any more until I reboot it.Any ideas? Please assume I've tried everything in this thread.
Thanks -Alex
/blink.gif\' class=\'bbc_emoticon\' alt=\':blink:\' />
Post by: David on July 26, 2005, 02:19:29 AM
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.
cheers&alex[/quote]
I've struggled with these problems for weeks--spending countless hours trying to resolve them.
Replacing "peer to peer" with "hybrid" did the trick.
Thanks to all for the great guidance.
Steve Low
[post=\"15960\"]<{POST_SNAPBACK}>[/post]
[/quote]
Post by: David on July 26, 2005, 02:22:02 AM
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.
cheers&alex[/quote]
I've struggled with these problems for weeks--spending countless hours trying to resolve them.
Replacing "peer to peer" with "hybrid" did the trick.
Thanks to all for the great guidance.
Steve Low
[post=\"15960\"]<{POST_SNAPBACK}>[/post]
[/quote]I have tried evrything on these posts and this is the one that works...you are the man. Been 2 days working on it and edited the registry and everything works great. Thanks
Post by: Guest on August 07, 2005, 06:55:33 PM
Post by: Angela on August 12, 2005, 12:33:28 PM
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 by: Guest_Scott_* on September 12, 2005, 09:33:02 PM
Interestingly, my PC can see my laptop using netbios but my PC cannot ping my laptop. Conversely, my laptop can ping my PC but it cannot see my PC using netbios...
Very irritating... any additional suggestions?
Post by: Guayi on September 13, 2005, 02:08:44 PM
Post by: Kiran Patel on September 14, 2005, 11:10:15 AM
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> Finally Solved!!! I went up to page 4 and tried all of the solutions, and then i realized that NETBIOS wasnt installed on one of the comps I was trying to get to. I installed it and viola! Everything worked!
Post by: Guest on September 15, 2005, 03:00:46 AM
install the damn NETBIOS
Post by: thankful user on September 19, 2005, 08:14:52 PM
/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]
Post by: Guest on September 25, 2005, 03:40:09 AM
Post by: Lanadmin on October 04, 2005, 03:03:53 PM
[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]
Post by: Nick Matharu on October 07, 2005, 05:36:01 AM
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
/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]
Post by: Guest on October 10, 2005, 08:55:02 PM
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:
Post by: Guest_Stu_* on October 27, 2005, 07:36:46 PM
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.
Post by: HAKER on October 29, 2005, 06:51:27 AM
to jagexxcorporationEmail Removed. send this:
@@@@@@@@for@runescape@@!!!?+_+_+_+_+_+_+_+_!!!!!!!!???:':????::::...<<<<?????>>>>>your user name@@@@@@^^^^&&&&&""::}{|{|{|}{}|{}|
@@@@########$$$%^&^*()(*&&&&&"""""_+_+_+_+_+_++__*&**&#()#?>>?>?><:"":}{{}||{}}}|(*#($(^$#($(#^$#^&*$&$*(your user password _)(((((***(
:":}{)(()**()&)*(^^&*^^%^%^%**&*^^&**%%$^&$&%$%^^&*%^$^*&())()(*(&&^%#$#@@@@!!!!@@#$%$%%^&^&&^&&**&(*^*^&&$@%@#@%^%^#$#%$^%%&%
i want to help for people who play runescape!
Post by: down in france on November 01, 2005, 12:20:44 PM
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
Post by: Guest on November 02, 2005, 12:30:30 PM
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.
Post by: Goodrichmcse on November 09, 2005, 12:27:39 PM
/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
/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]
Post by: dark man852 on November 09, 2005, 12:49:56 PM
/laugh.gif\' class=\'bbc_emoticon\' alt=\':lol:\' />
Post by: LordLiverpool on November 09, 2005, 01:56:03 PM
/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!
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' />
Post by: Lord Roop on November 18, 2005, 07:44:26 PM
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
/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"
Post by: novice2 on December 04, 2005, 01:13:15 AM
Post by: jcappell on December 04, 2005, 11:37:43 PM
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. )
Post by: bowtie406cid on December 13, 2005, 10:47:07 PM
Searched for my computer and found it but if I go to Network Places view workgroup computers I cant see it... why??
Post by: drilldown on January 17, 2006, 02:11:13 AM
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 (http://\"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 (http://\"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 (http://\"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 (http://\"http://support.microsoft.com/default.aspx?scid=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 (http://\"http://www.microsoft.com/windowsxp/home/evaluation/overviews/xpindomain.asp\")
Why Windows XP Professional is Best for Domain-Based Networks
http://www.microsoft.com/windowsxp/home/ev...joindommore.asp (http://\"http://www.microsoft.com/windowsxp/home/evaluation/overviews/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 (http://\"http://support.microsoft.com/default.aspx?scid=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 (http://\"http://www.practicallynetworked.com/sharing/xp_filesharing/index.htm\")
HOW TO: Use Compressed (Zipped) Folders in Windows XP
http://support.microsoft.com/default.aspx?...kb;en-us;306531 (http://\"http://support.microsoft.com/default.aspx?scid=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 (http://\"http://www.practicallynetworked.com/sharing/xp_ics/networkbridge.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 (http://\"http://support.novell.com/cgi-bin/search/searchtid.cgi?/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.
Post by: drilldown on January 18, 2006, 02:20:59 AM
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.
Post by: philipms on January 31, 2006, 01:54:32 PM
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
Post by: kemelinux on February 15, 2006, 12:55:07 PM
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.
Post by: Donna Michelle Cappucio on February 28, 2006, 02:57:08 AM
I spent hours and hours on this and tried everything in these forums with no luck. A tech guy at my job was kind enough to help me with this issue. His advice:
With all computers on the network turned on, follow these steps on each computer.
1. Go to Start/ All Programs / Accessories /Command Prompt
2. Type ipconfig /flushdns and hit Enter. (ipconfig [space] /flushdns)
3. Type ipconfig /registerdns and hit Enter. (ipconfig [space] /registerdns)
Now, try viewing workgroup computers and accessing each. (Start/ My Newtwork Places/ View Workgroup Computers)
I hope this works for you, too! If not, try the advice from the previous threads (which I did), and then try this again.
Post by: nheero on March 14, 2006, 07:46:33 PM
I've tried a number of things. The thing that initiated the quest was loss of internet for one of my computers. I have four PCs on a linksys WRT54GS gateway. Three are working fine, the fourth can access the other computers as well as the gateway (192.168.1.1), but cannot find the internet for some reason. I tried installing the latest internet browser to no avail. Firewalls have been disconnected, leaving only the router firewall, which is apparently all that is needed fro a home network.
The PCs are all windows XP SP2.
I can ping any computer to any other computer and can connect from the problem computer to any other computer. But none of the other computers can connect to the problem computer, which leads me to suspect that this is related to the internet connection failure.
I've tried mapping the drive with connection to a different user, IRPStackSize, and a few other diagnostics, but haven't solved it yet. Any ideas?
Post by: pro edge on March 14, 2006, 08:02:43 PM
/happy.gif\' class=\'bbc_emoticon\' alt=\'^_^\' />
Post by: nheero on March 19, 2006, 08:43:05 PM
/biggrin.gif\' class=\'bbc_emoticon\' alt=\':D\' /> I reinstalled Windows XP SP2 via upgrade option in setup. It's nice when that works without having to reformat the disk to do a clean install.
Post by: bobb181818 on May 09, 2006, 06:26:50 PM
Post by: abcd200x on May 11, 2006, 11:08:55 PM
Thanks.
Post by: inkyfingers on August 31, 2006, 12:30:29 PM
[quote name=\'matterdaddy.com\' post=\'12029\' 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.[/quote]
Now, my desktop cant even see my laptop!! So i have gone a step backwards. Any advice on how to reverse this without wrecking my registry? (i'm jumpy about changing it in the first place, and this has proved me right)
thanks
Post by: Pureblood on August 31, 2006, 02:34:00 PM
Post by: price on September 02, 2006, 10:01:08 AM
along with my g net adsl modem
the problem im having is getting the connection to work for some reason i must have the router hooked up wrong casue it will show up on my pc that is wirelessly connected and it says its connected but i cant acces the internet or nothing
also on my access point pc it wont allow me to connect to the internet on this unless i discopnnect the wirrless router
any one can help maybe i got it hooked up wrong
from internet (phone jack)--------adsl modem (LAN)------wirless router(internet/WAN)-(1)---------pc (card)
i dont know if ull be able to understand that without seeing my modems but if u can maybe u can tell me what im doing wrong?
Post by: redwood on November 06, 2006, 05:03:07 PM
I have 3 XP Pro computers and a Mandriva 2007 computer on an Ethernet with an ADSL box. The problem was that one of the XP computers could access shares on all of the other computers but none of the others could access this particular one’s shares. All had the AVG anti-virus and the MS Firewall in operation.
I “rtfmâ€ed every thread I could find on the internet about this but none solved the problem.
NETBIOS, file & printer sharing were set on all, IPCONFIG gave similar results for all, all were in the same workgroup with different IP addresses and names. All had hosts and lmhosts files identical. Client for Microsoft Networks was loaded on all. I had been through every TCP/IP, network, firewall, Security Policy and every other parameter I could think of.
The main clue was that everything worked properly if the Microsoft Firewall was disabled on the XP system that would not allow the others to access its shares. Because of the ADSL box, leaving the Firewall off was not an option. So there was something wrong with the Firewall. But what? I compared every parameter in the “Exceptions†and “Advanced†tabs on the Firewall “cpl†(control panel applet) – nothing appeared awry. Incidentally, I could not “ping†the errant XP system but otherwise everything could “ping†everything else.
Eventually I noticed the “Restore Defaults†button on the advanced tab of the Firewall “cplâ€. Taking note of the current settings in the “exceptions†and the “advanced†tabs, I hit the “Restore Defaults†button. The problem was now solved. All I had to do was to put back manually (I could have reinstalled the relevant packages) the settings I had lost.
It would seem that the MS Firewall has the capability of getting its knickers in a twist without you being able to see the specific problem. I guess that the “Restore Defaults†has been put there for a reason.
Hope this is of use to someone out there.
Post by: Pureblood on November 06, 2006, 05:32:53 PM
Post by: keef on November 22, 2006, 06:05:48 PM
One more solution for the pile.
/tongue.gif\' class=\'bbc_emoticon\' alt=\':P\' />
Post by: advertiser on March 29, 2008, 11:42:17 AM
Sam Milby
-----------------------------------------------------
Tiscali broadband and phone deals in the UK. 8MB broadband from £6.49 with free uk and international phone calls. Now which Tiscali TV. Tiscali network, work from home, earn money and free to join. http://www.tiscali-network.com/fastbroadband (http://\"http://www.tiscali-network.com/fastbroadband\")