"\\ip is not accessible"

Y

yerk5

In my place of business we have a PC, which is part of a domain, but
usually not logged on with a domain account (rather a local
administrative user account instead). We want to be able to set up
some shares from this PC.

Let's call it MachineA. From any other PC, we try to his \\MachineA to
see its list of shares and get the error:

\\MachineA 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 referenced account is
currently locked out and may not be logged on to.

It doesnt matter if I use netbios name or IP. The computer I'm using
when Im trying to access this (MachineB) is also logged in as a local
admin (not a domain user). So what is machine A talking about.. about
the referenced account being locked out? It should be prompting me for
a a domain user or local user account, instead of just spitting this
error at me.

I poked around the web and found that if I do from my machine:
net use \\MachineA\IPC$ /u:domain\user

and enter my domain account's password, then I can access \\MachineA
just fine. At least until the next time I log off my machine. But this
shouldn't be necessary anyway. If I'm logged in as a local admin on my
MachineB, and I walk over to MachineA and try: \\MachineB
I get prompted for a logon. If I supply a local or domain user
credentials, I get access. So it works one way, but not in reverse.
Why isn't this working on MachineA?

Thanks much in advance for any tips.
 
K

Kirrin Jones

What you should do is make sure that there is a domain group in the
local group of MachineA that contains the accounts of the users on the
domain that will be accessing the machine. So if you have a domain group
called Domain Users, that all users of the domain are members of, then
you need to add this group to the local group of MachineA (whether it be
the administrator group or some other group)

All should be well once you do that and then setup your shares to allow
those persons to access them.
 
Y

yerk5

Hmm, that makes very good sense. But I went into the "MachineA\Users"
local group and "MyDomain\Domain Users" was already added.

In fact I compared all local groups of both MachineA and MachineB and
theyre identical. But still getting the same message trying to hit \
\MachineA from B, but its ok vice versa. Still hunting...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top