"\\ip is not accessible"

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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.

.

Relevant Pages

  • Re: "\ip is not accessible"
    ... local group of MachineA that contains the accounts of the users on the ... administrative user account instead). ... a a domain user or local user account, ...
    (microsoft.public.windowsxp.general)
  • Re: "\ip is not accessible"
    ... 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. ... administrative user account instead). ...
    (microsoft.public.windowsxp.general)
  • IUSR account replication outside Active Directory
    ... My ASP pages, published in IIS 5.0 on MachineA, are trying to read ... server. ... Microsoft Access Driver] The Microsoft Jet database engine cannot open the ... account in MachineB I cannot do it because MachineA is not in the Active ...
    (microsoft.public.inetserver.iis.security)
  • Re: ADAM SP1 on Win2K3 SP1
    ... Assuming SSL on ADAM is working fine and i want to use antoher domain user account as the ADAM service account. ... Do i only need to grant that account READ permission to machine keys and use dsdbutil to change the ADAM service account? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Workaround for 0x8007045A (!)
    ... works if you log on to the administrator account of a workstation attached to ... in a fit of social conscience that might help other WU5 ... domain account under previous versions of SBS were now missing. ... on as domain user and WU5 doesn't work. ...
    (microsoft.public.windowsupdate)