"An error occurred in network provider Microsoft Windows Network. Error240:
The user is not allowed to log on from this workstation."
The user id that we are attempting to connect with is part of the Users group
on the Server, and both the Users group and this particular user id have read
capabilities on the directory we are trying to reach on the server.
Also, when we try and log on to the server locally (at the server workstation)
with that particular id, the following error message is returned:
"Your account is configured to prevent you from using this workstation. Please
try another workstation."
Any user accounts that are in the Administrators group have no problem
accessing the server, but users in the Users group can't get to shared
directories when they have the correct permissions on them. The Users group
has the User Right: "Access this workstation from teh Networ" and "Log on
Locally" ... so this problem is mystifying me ... I'm starting to think that
some of the information in the Users database may have been corrupted somehow
... Any suggestions?
Jeff Arsenault
p8...@unb.ca
-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum
It appears to have started on Aug 25, with one user receiving the Networking
Error: "You are not allowed to log on at this workstation". Since that time
the problem has spread to five users. The problem only seems to pop up when
the user first logs on and requires them to log on several times before
validating them. I verified that users have been granted the log on to all
workstation permission in User Manager for Domains.
As a work around to allow users to log on to their machines, I have created a
Global Group called LocalLogon with the Log on Locally rigtht and placed the
affected users in this group. This seems to fix the problem, but at their
current workstaion only. When an affected user tries to log on at a different
Win 95 machine they get the same Networking Error.
Any thoughts would be useful.
Chris Romeo
chris...@rgsinc.com
In article <6qnbi0$kki$1...@nnrp1.dejanews.com>,