XP home network issue

  • Thread starter Thread starter nyc_sud
  • Start date Start date
N

nyc_sud

I have 2 computers (XP home) connected to a wireless network. I was
able to share files between the computers and share a printer as well.


Up until a few days ago, I noticed that one of the computers (desktop)
does not show "My Network Places" in the Start menu. When I look at "My
Computer" >> "My Network Places" there are no folder/shared places
listed. The laptop still shows the shared files/folders.

Both computers are hooked up to a Netgear wireless router and can
access the net without issue. I believe that when I set it up I used
the default name of 'Mshome' as the network name. When I click "View
workgroup computers" desktop machine give me the following message
"Mshome is not accessable. You might not have permission to use this
network resource. Contact the admin......."

What did I do to disable the access on the desktop machine? Any help
would be greatly appreciated.
 
I have 2 computers (XP home) connected to a wireless network. I was
able to share files between the computers and share a printer as well.


Up until a few days ago, I noticed that one of the computers (desktop)
does not show "My Network Places" in the Start menu. When I look at "My
Computer" >> "My Network Places" there are no folder/shared places
listed. The laptop still shows the shared files/folders.

Both computers are hooked up to a Netgear wireless router and can
access the net without issue. I believe that when I set it up I used
the default name of 'Mshome' as the network name. When I click "View
workgroup computers" desktop machine give me the following message
"Mshome is not accessable. You might not have permission to use this
network resource. Contact the admin......."

What did I do to disable the access on the desktop machine? Any help
would be greatly appreciated.
Click to expand...

One of the most common causes of this problem would be a misconfigured or
overlooked personal firewall, but there are other possibilities too. What
antivirus products are you using?
<http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html>
http://nitecruzr.blogspot.com/2005/10/irregularities-in-workgroup-visibility.html

What is the complete and exact error message? Sometimes that will provide a
clue.
<http://nitecruzr.blogspot.com/2006/01/look-at-complete-detail-in-error.html>
http://nitecruzr.blogspot.com/2006/01/look-at-complete-detail-in-error.html

If no help yet, provide "browstat status" and "ipconfig /all" from each
computer, so we can diagnose the problem. Read this article, and linked
articles, and follow instructions precisely:
<http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp>
http://nitecruzr.blogspot.com/2005/05/troubleshooting-network-neighborhood.html#AskingForHelp
 
nyc_sud said:
I have 2 computers (XP home) connected to a wireless network. I was
able to share files between the computers and share a printer as well.


Up until a few days ago, I noticed that one of the computers (desktop)
does not show "My Network Places" in the Start menu. When I look at "My
Computer" >> "My Network Places" there are no folder/shared places
listed. The laptop still shows the shared files/folders.

Both computers are hooked up to a Netgear wireless router and can
access the net without issue. I believe that when I set it up I used
the default name of 'Mshome' as the network name. When I click "View
workgroup computers" desktop machine give me the following message
"Mshome is not accessable. You might not have permission to use this
network resource. Contact the admin......."

What did I do to disable the access on the desktop machine? Any help
would be greatly appreciated.
Click to expand...


Exactly the same thing happened to me several months ago, and I've been
looking intermittently for a solution. Yesterday I finally solved it by
installing NETBUI (see http://support.microsoft.com/kb/301041/EN-US/ ).

Worked like a charm.

Neil
 
Exactly the same thing happened to me several months ago, and I've been
looking intermittently for a solution. Yesterday I finally solved it by
installing NETBUI (see http://support.microsoft.com/kb/301041/EN-US/ ).
Click to expand...

Neil,

Installing NetBEUI is a good workaround, when you have a problem with TCP/IP and
NetBIOS Over TCP/IP. There are numerous other problem that folks can have with
Windows Networking, and your problems need to be diagnosed before you apply
workarounds. And NetBEUI is limited in effect. Know what you're doing, and
what its limitations are, before applying it.
<http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html>
http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html

If you've been "looking intermittently for a solution", you haven't been looking
here, have you? You certainly haven't posted here, under "neil tupper", asking
for help.
<http://groups.google.com/group/micr...il+tupper"&qt_g=1&searchnow=Search+this+group>
http://groups.google.com/group/micr...il+tupper"&qt_g=1&searchnow=Search+this+group

To the OP:
Anybody can give advice here. Beware of accepting advice from folks who post
once, about a change that they made yesterday, as a magical fix to your
problems. Diagnose your problems first. And note the caveat in the cited
article:
Microsoft has discontinued support for the NetBEUI network protocol in Windows
XP.
 
It's good advice, Chuck. It took me a while, but here's all teh extra
detail you advised was necessary for a proper debug to an older post I made:

Windows Firewall off on both machines.
Norton Antvirus prevented from loading on Machine 1, not present on Machine
2
In 'View Network Computers', both machines can see the icon of the other.
Machine 1 can read from and write to Machine 2 perfectly.
On double-clicking the icon for Machine 1 from Machine 2, teh exact error
message is:

'\\Machine 1 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. Access is denied.'

Machine 2 CAN read from and write to a 3rd machine connected wirelessly to
the network via the same wireless router to which Machine 1 & Machine 2 are
connected by cable.

All machines see the internet perfectly.

The ipconfig/all files are attached. Neither machine recognised the
'browstat' command.

Much appreciated.

Thanks,

Steven
 
It's good advice, Chuck. It took me a while, but here's all teh extra
detail you advised was necessary for a proper debug to an older post I made:

Windows Firewall off on both machines.
Norton Antvirus prevented from loading on Machine 1, not present on Machine
2
In 'View Network Computers', both machines can see the icon of the other.
Machine 1 can read from and write to Machine 2 perfectly.
On double-clicking the icon for Machine 1 from Machine 2, teh exact error
message is:

'\\Machine 1 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. Access is denied.'

Machine 2 CAN read from and write to a 3rd machine connected wirelessly to
the network via the same wireless router to which Machine 1 & Machine 2 are
connected by cable.

All machines see the internet perfectly.

The ipconfig/all files are attached. Neither machine recognised the
'browstat' command.

Much appreciated.

Thanks,

Steven
Click to expand...

Thanks for the feedback, Steven. Using alternative solutions is a good idea,
sometimes, but it needs to be done intelligently, not in shotgun fashion.

Anyway, I found your attachments in your other post (I never would look for them
normally, please read this article):
<http://nitecruzr.blogspot.com/2006/01/providing-diagnostic-data.html>
http://nitecruzr.blogspot.com/2006/01/providing-diagnostic-data.html
 
Chuck said:
Installing NetBEUI is a good workaround, when you have a problem with
TCP/IP and
NetBIOS Over TCP/IP. There are numerous other problem that folks can have
with
Windows Networking, and your problems need to be diagnosed before you
apply
workarounds. And NetBEUI is limited in effect. Know what you're doing,
and
what its limitations are, before applying it.
<. . .>
If you've been "looking intermittently for a solution", you haven't been
looking
here, have you? You certainly haven't posted here, under "neil tupper",
asking
for help.
. . .
To the OP:
Anybody can give advice here. Beware of accepting advice from folks who
post
once, about a change that they made yesterday, as a magical fix to your
problems. Diagnose your problems first. And note the caveat in the cited
article:
Microsoft has discontinued support for the NetBEUI network protocol in
Windows
XP.
Click to expand...


Well let's not get snotty here. I'm just saying what worked for me. I've
spent several hours working on this problem, and I found something that
fixed it. If I chose to share that information with someone who appears to
have a similar problem, I should not have to be flamed by an "MVP". No-one
is forcing anyone to follow a particular route to a fix, and regardless,
installing NetBUI is not a particularly course of action.

Workarounds are exactly that. If they fix a problem with little degradation
in performance - good. If they don't, what have you lost? Most computer
users have other things to do than run diagnostics.

Neil
 
Well let's not get snotty here. I'm just saying what worked for me. I've
spent several hours working on this problem, and I found something that
fixed it. If I chose to share that information with someone who appears to
have a similar problem, I should not have to be flamed by an "MVP". No-one
is forcing anyone to follow a particular route to a fix, and regardless,
installing NetBUI is not a particularly course of action.

Workarounds are exactly that. If they fix a problem with little degradation
in performance - good. If they don't, what have you lost? Most computer
users have other things to do than run diagnostics.

Neil
Click to expand...

Neil,

I'm not flaming you. I am trying to help the other folks who use this forum for
help.

NetBEUI has been around for a while, and it's used occasionally by folks who
can't get TCP/IP working on their LAN, when their problem relates to TCP/IP.
But, since you didn't ask for help here, we have no way of knowing what your
problem really was. Maybe you could have been helped, maybe not.

I'm trying to advise folks who need help to ask for help, not to blindly follow
the advice in posts offering a miracle solution. It's a lot easier to help
someone with a problem before they try to solve it with solutions that may not
be related to the problem.

Please read my article about alternative transports, and understand the
limitations of your advice. It will do you, and us, some good if you do.
<http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html>
http://nitecruzr.blogspot.com/2005/07/windows-networking-and-alternate.html

And realise that NetBEUI is no longer supported by Microsoft, so, as time goes
on, it will be harder to find relevant and up to date documentation. It will be
better for you, if you can figure out what your problem with TCP/IP was.

Solve the problem, not just the symptom.
 
Back
Top