Re: Two-computer network, MSHOME is not accessible" on both

On Mon, 09 Apr 2007 18:52:28 -0700, Chuck <none@xxxxxxxxxxx> wrote:

It's a known problem. The error "The list of servers for this workgroup is not
currently available." comes from lack of browser SMBs...

Thanks for your assistance. With your guidance and some rummaging
around in Norton, I have almost got the thing to work.

At this point each computer can see the network, and can see the other
on the network. The desktop computer can access shared folders on the
portable, but the portable cannot access shared folders on the
desktop. When it tries, it gets the error message:

[systemname] is not accessible... Login failure: the user has not been
granted the requested logon type at the computer.

I am logged in with the same name on both computers, using the same
password on both, so I expected each computer to be able to access the
other without requiring me to enter a password.

I tried to research this myself, and concluded that the problem was my
setting for the "Access to this computer from the network..." policy
in the "User Rights Assignment" section of "Administrative Tools." On
the portable computer it is set to a long list of values which
includes "Everyone" and "Users." On the desktop computer it was set
to only "ASPNET."

I changed that policy on the desktop computer to include "Everyone."
It didn't help, though, even when I rebooted the portable. I then
tried adding "Users" and "Power Users" to the policy, but
Administrative Tools refused to accept those values, saying they did
not exist. Microsoft's documentation appears to say that they are
standard (predefined) group names, so I don't know what to make of
that.

I've got a couple of puzzles now. The first is why the portable still
can't access shared folders on the desktop computer.

The second is the ASPNET entry in "Access to this computer from the
network..." in the course of trying to duplicate the portable's
setting on the desktop I deleted this item and tried to redefine it,
and found that I could not! When I enter ASPNET, the policy applet
interprets it as "[systemname]\ASPNET". I have no idea what ASPNET is
-- it's certainly nothing of mine -- so I have no idea what the
significance of this problem is, much less how to correct it.
.

Loading