I have a question about Getting Network Neighborhood to recognize newly attached computers:

I have just built a new XP box and am tring to connect it to my old XP box. They are both connected through a Lyinksys router to a cable modem. I can get one computer to see the other in view workgroup computers but get the following message when trying to connect: \\"computer name" is not acessible, 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. I have check file and print sharing on the drives in both computers. I thought this home networking was easier with XP. I had my old XP box networked with a Win98SE box before with less problems than this.

[Reply or follow-up to this message]

This is a common thing with any NT based system.

For you to setup access, the username and password you log into each system must 
exist not only on the one you are logging into, but any other system must have the 
same username/password for you to be authenticated.  This is true for any machines 
not in a domain.

Windows 9x does not do this because it doesn't care and is not secure at all (it 
only uses passwords for desktops and some minor network functions).

Brian
Computer Tech






On Sunday, March 16, 2003 at 10:13 am, Olaf wrote:
>I have a question about Getting 
>Network Neighborhood to recognize newly attached computers:

>
>I have just built a new XP box and am tring to connect it to my old XP box.  They 
>are both connected through a Lyinksys router to a cable modem.  I can get one computer 
>to see the other in view workgroup computers but get the following message when 
trying 
>to connect:  \\"computer name" is not acessible, 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.
>
>I have check file and print sharing on the drives in both computers.  I thought 
this 
>home networking was easier with XP.  I had my old XP box networked with a Win98SE 
>box before with less problems than this.

[Reply or follow-up to this message]

Olaf, I have the same problem - were you able to find a solution? Thanks, Gene


On Sunday, March 16, 2003 at 10:13 am, Olaf wrote:
>I have a question about Getting
>Network Neighborhood to recognize newly attached computers:

>
>I have just built a new XP box and am tring to connect it to my old XP box. They
>are both connected through a Lyinksys router to a cable modem. I can get one computer
>to see the other in view workgroup computers but get the following message when trying
>to connect: \\"computer name" is not acessible, 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.
>
>I have check file and print sharing on the drives in both computers. I thought this
>home networking was easier with XP. I had my old XP box networked with a Win98SE
>box before with less problems than this.

[Reply or follow-up to this message]

Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT cockup. I had the same problem, and after trying 3,000 different solutions and this is the monkey idiot solution what worked for me. Go to "view network connections" Click on your local network. Click on properties (you should start at the "general" folder. Stay there or go there if not) Click the "install" button. You get the choice of client, service or protocol. Click protocol. Add yer protocols. NetBios and TCP/IP if they aren't there. Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just start with these components installed in the first place, since there doesn't seem to be any reason NOT to. &lemme know if this works for you, cheers, Toby

[Reply or follow-up to this message]

WORKED FOR ME! THANKS! This was driving me NUTS!


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

I would like to kiss you i mean it works flawlessely i cant belive that was microsoft 
screwed up on man its really wpecially since u spend hours on the phone with a technician 
who can even reset your TCP settings. Buncha idiots dont even know how to setup a 
802.11b wireless home network i wish they would get sum1 smart up there!!!
Thanx SOOOOOOO much
  Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT 
>cockup. I had the same problem, and after trying 3,000 different solutions and this 
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go 
there 
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just 
>start with these components installed in the first place, since there doesn't seem 
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

Thanks man ...you are the best!!!!


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

I'm finding my place in line with the others who want to kiss you. Had someone (as in, paid someone) here yesterday who spent about six hours trying to connect two computers before giving up. Thanks for your help, comrade. - J.B.


On Saturday, December 6, 2003 at 12:50 am, edi wrote:
>Thanks man ...you are the best!!!!
>

[Reply or follow-up to this message]

Bless you sir Toby.I stumbled on this post by spelling "accessible" wrong in a GOOGLE search. Two months of head banging is over. If i may ad a point. My networked functioned until I installed new drivers for my Nvidea video card.When I did, my XP went to a "you need to register with microsoft" mode. After calling MS with the numbers, my network quit and I couldn't get it back until now.Thanks again


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

Yeah its all evil Microsofts fault?? man thats dumb How bout the router maker? Not a freakin word about it their docs. There is a reason not to have it installed--most people will never use it anyway too.

[Reply or follow-up to this message]

It worked. Thank you so much. It was the linksys netbios protocol that was missing for me. I also had been struggling trying 10,000 different things. Cheers, you are awesome!!!!!


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

Hey it worked for me too. I cant believe I wasted two whole days trying to get this simple wireless network going. You would think that Microsoft would have something about this on their site ... And you would think they would install ALL protocols by default on every LAN connection... No wonder Apple's stock is up...


On Thursday, June 17, 2004 at 7:08 am, KevinK wrote:
>It worked. Thank you so much. It was the linksys netbios protocol that was missing
>for me. I also had been struggling trying 10,000 different things.
>
>Cheers, you are awesome!!!!!
>
>
>

[Reply or follow-up to this message]

While I know the NetBios thing is working for everyone, I think the issue may be the routers you have installed. On mine I had the domain as "domain" when on my machines it was now "MyDomain". While I relize not everyone is on a domain I think you need to put the right workgroup name in there. I am pretty sure most routers have a domain or network name option.


On Tuesday, July 20, 2004 at 5:04 pm, Doug Smith wrote:
>Hey it worked for me too. I cant believe I wasted two whole days trying to get this
>simple wireless network going.
>
>You would think that Microsoft would have something about this on their site ...
>And you would think they would install ALL protocols by default on every LAN connection...
>
>No wonder Apple's stock is up...
>
>

[Reply or follow-up to this message]

Sir Toby, Please permit me to kiss your feet if you are ever in town. It has taken 3 days to get this working! I have XP running on two machines connected via a crossover cable, so the router manufacturer is not to blame - definitely looks like a Microsoft goof - bless 'em. File sharing has never felt so good! DCtalk


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

Err.. Sir Toby, didnt work for me. any more tricks up yer sleeves?


On Tuesday, October 26, 2004 at 8:33 am, DCtalk wrote:
>Sir Toby,
>
>Please permit me to kiss your feet if you are ever in town. It has taken 3 days to
>get this working! I have XP running on two machines connected via a crossover cable,
>so the router manufacturer is not to blame - definitely looks like a Microsoft goof
>- bless 'em. File sharing has never felt so good!
>
>DCtalk
>
>
>

[Reply or follow-up to this message]

Didn't work for me either. Then again, NETBIOS was not one of my choices. My network was working fine last weekend. This past week I ran the "security updates" from Microsoft on both computers. Ever since then, chaos. The security updates turned on all the microsoft stuff I had turned off and seems to have forever destroyed my network. David Hall


On Sunday, March 6, 2005 at 12:28 pm, SirThinkAlot wrote:
>Err.. Sir Toby, didnt work for me. any more tricks up yer sleeves?
>
>
>

[Reply or follow-up to this message]

Hey, I added all the protocols i could find, but i still have access problems. I want to be able to be completly free of permission probels and stuff. I want to be able to share between my three comp IP addresses. Some files I can access, other I cannot. Please help.


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

My network worked for months, then "Local Network" disappeared from Network Neighborhood. I could still connect to other computers, but could not see them. I renamed the workgroup and everything works.


On Sunday, March 16, 2003 at 10:13 am, Olaf wrote:
>I have a question about Getting
>Network Neighborhood to recognize newly attached computers:

>
>I have just built a new XP box and am tring to connect it to my old XP box. They
>are both connected through a Lyinksys router to a cable modem. I can get one computer
>to see the other in view workgroup computers but get the following message when trying
>to connect: \\"computer name" is not acessible, 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.
>
>I have check file and print sharing on the drives in both computers. I thought this
>home networking was easier with XP. I had my old XP box networked with a Win98SE
>box before with less problems than this.

[Reply or follow-up to this message]

thankyou, it solved half of my problem. I can only access files one way but hey it's better than nothing. no thanks to MS


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

This worked for me, spent 2 days trying to get this to work. I can't believe this is still going on. Thanks a lot


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

Thank you Toby. It is almost two years since you posted your fix and I used that fix successfully today. There are some smart people at Microsoft. Why have they not yet picked up on this flaw in their system and fixed it on their end? tnt


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

YOU ARE BRILLANT. THANKYOU SO MUCH


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

I too am simply blown away, I spent some 7 days straight trying to configure two machines a pc and laptop using a wireless adaptor and dial-up, I dont think it gets much simpler (slow but cheap).I thought I was in hell NO ONE could figure this out.....until I arrived here. Like the guy said before almost three years and MS has not included the fix. Thank God for the Toby's of this world. Hihar


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

I have 6 resources shared from a primary workstation. All workstations can access this one. Everything works except accessing the CD-RW. I can surf and even create a shortcut to the drive from any workstations but for the CD-RW.


On Wednesday, May 4, 2005 at 8:14 pm, Jim Bohanon wrote:
>My network worked for months, then "Local Network" disappeared from Network Neighborhood.
> I could still connect to other computers, but could not see them. I renamed the
>workgroup and everything works.
>
>
>

[Reply or follow-up to this message]

You are an absolute lege!! After god knows how much stuffing around and reading Microsoft generated BS with the most useless instructions, you are the man ... whatever those protocol things are, they def should be standard! Susanne


On Saturday, November 22, 2003 at 6:46 am, toby wrote:
>Hi. You know this is going to boil down to some completely fricking ridiculous MICROSOFT
>cockup. I had the same problem, and after trying 3,000 different solutions and this
>is the monkey idiot solution what worked for me.
>
>Go to "view network connections"
>
>Click on your local network.
>
>Click on properties (you should start at the "general" folder. Stay there or go there
>if not)
>
>Click the "install" button.
>
>You get the choice of client, service or protocol. Click protocol.
>
>Add yer protocols. NetBios and TCP/IP if they aren't there.
>
>Enjoy the feeling of sharing files, and scream out the Window that MSFT didn't just
>start with these components installed in the first place, since there doesn't seem
>to be any reason NOT to.
>
>&lemme know if this works for you,
>
>cheers,
>
>Toby

[Reply or follow-up to this message]

Thank you TOBY of the world I have had this problem ever since a power outtage did something weird to my USB port on my host computer that was attached to my external back up hard drive qdisk 60GB discontinued by Archos so I had to switch the host computer to be the roaming one and the roaming one to be a host on the wireless network..basically you need a medal man and MS suck


On Monday, November 7, 2005 at 2:46 am, Susanne wrote:
>You are an absolute lege!! After god knows how much stuffing around and reading Microsoft
>generated BS with the most useless instructions, you are the man ... whatever those
>protocol things are, they def should be standard!
>Susanne
>
>
>

[Reply or follow-up to this message]

"Add yer protocols" -> what are "yer protocols"

[Reply or follow-up to this message]

"The fix" doesn't work for me. When I try to add Microsoft TCP/IP version 6, I get the error: "Could not add the requested component. The error is: An extended error has occurred." Any ideas? Thanks.

[Reply or follow-up to this message]

you ROCK!!! for those having a problem with the fix.. you do not have to add TCP/IP 6 (or whatever it's called) Just the two protocols named.. it works GREAT.. but only worked for me after I installed it on every machine on the network!! Thanks again :)


On Monday, January 22, 2007 at 10:10 am, CzekM8 wrote:
>"The fix" doesn't work for me. When I try to add Microsoft TCP/IP version 6, I get
>the error: "Could not add the requested component. The error is: An extended error
>has occurred." Any ideas?
>
>Thanks.

[Reply or follow-up to this message]

• Search this forum
• Start a new thread on a different subject

• Report abuse of the forum