ok for this to work,

the account the person is logged in as username and password needs to exist
on the other machine your mapping to as well

They both have to have the same workgroup name

They both have to be using the same submnet mask, ip class a,b,c ip address
and gateway

A folder needs to be shared on the one computer with the appropriate
permissions in the security tab for the user of the OTHER computer names.

Michael Evanchik
www.MichaelEvanchik.com

"Aidan" wrote:

> I am having the exact same error message. I have tried resetting the
> tcp/ip stack, and flushing the dns ...
>
> > netsh int ip reset c:\resetlog.txt
> > ipconfig /flushdns
> > ipconfig /registerdns
>
> .... mostly because the microsoft help center seemed to think it would
> solve my probs. But alas, no dice...
>
> I've also tried disabling windows firewall.
>
> My situation is this:
> 5 *brand new* computers have been purchased by my company. They are
> running XP Pro 2002 SP 2. This morning, all of them could connect to
> our file server by using a run command: "\\fileserver", or
> "\\fileserver\share". This afternoon, my computer cannot successfully
> run this command. When I don't specify a share (eg "\\fileserver") I
> get the error:
>
> "\\fileserver 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.
> Logon failure: user account restriction. Possible reaons are blank
> passwords not allowed, logon hour restrictions, or a policy restriction
> has been enforced."
>
> When I *do* specify a share (eg "\\fileserver\share"), I am repeatedly
> prompted with a username/password dialog ("Connect to fileserver").
>
> I can circumvent this problem by mapping a network drive to the share
> on the fileserver, and supplying the appropriate username and password.
> Once the map is established, I can then access all the shares on the
> fileserver with the run command! However, even if I set 'reconnect at
> logon' checkbox, the connection is NOT restored after a restart, so
> this solution isn't satisfactory for me. I know it's a small thing, and
> it sounds petty, but it drives me crazy having to enter the
> username/password after *every* restart.
>
> The strange thing is, that this error has only been occuring since *I*
> have been using the computer. My colleague was able to install some
> programs from the fileserver just before this started happening to me,
> so I must have made some change to the network settings... I just don't
> know what I could have changed to cause this behaviour! (I think it
> hates me)
>
> Not only are the other four computers are still able to access the
> server without creating a mapped drive, but I am able to access shares
> on those computers without a mapped drive! Which makes me wonder if its
> a setting on the server that is the problem...
>
> Has anyone got any idea what I've/we've done wrong?
>
>
> Kevan wrote:
> > XP in a workgroup. I try to access the XP machine with
> > local account created at both machines. Also put
> > credentials in the connect as box. I get the same
> > message. "\\Computer is not accessible. You might not
> > have permissions..... Logon failure: user account
> > restriction. Possible reasons are blank passwords not
> > allowed, logon hours restrictions, or a policy
> > restriction has been enforced." I removed the welcome
> > screen and disabled simple file sharing and verified the
> > users authenticate as themselves as well as removed the
> > restriction to the guest account to access the computer
> > over the network. Still the only account that seems to
> > get on without the above error message is the guest
> > account. HELP!!!
> > .
>
>