Archived from groups: microsoft.public.win2000.setup_deployment (More info?)
I have a Windows 2003 SBS server with one Win2000 Advanced Server on our
domain in the office that's just been set up. (no Win2K3 SP1, but it's
up-to-date on fixes etc.)
1) I can access INTO the Win2K3 server from any workstation or server
2) I can't access any workstation FROM (out of) the Win2K3 server. I can't
copt/paste TO the workstation/server from the Win2K3 server.
When attempting to access the Win2K server, \\OtherServer, we get this
message:
"\\OtherServer 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: the user has not been granted the requested logon type at
this computer."
The Microsoft website response on the 'logon failure' message says:
"User Action:
Change your logon location. Try to log on either locally (interactively) or
remotely (over the network), as appropriate. You may want to ask the person
who administers computer security to change the security database so you can
log on either locally or remotely. "
I don't quite understand the message and if a change needs to be made on the
user-level or computer name level. We're using Active Directory services and
I'm not too sure what to change or where to change it. I've checked
Computers and Users under Active Directory and reviewed the Services that are
started.
The issue on 'outbound access errors from the Win2K3 server' is valid for
all computers on the network and all users, even the Administrator user on
the workstations, the Win2K3 server or logging on via Remote Desktop
Connection.
There seems to be a 'little checkbox' or permissions that we're missing.
All folders on the Win2K3 server are Full Control. The error message occurs
whether the 'copy/paste' via Explorer is a single file or a folder. We can't
copy/move anything FROM the Win2K3 server to any other workstation. We can
copy/move into but not from the Win2K3.
Let me know what direction to use. I'll be reviewing the posts and working
via Remote Desktop Connection on your ideas.
Tom
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.