Hi Alan,
I went through the links. It looks like it is talking about 2 things.
The first link is talking about SMSINST (Which is more related to SMS
server), and I do not understand this part. As, I am talking about users
who
are printing to Windows Server 2003/Print Server and Windows 2000
Professional and Windows XP Pro.
The second link is talking about changing the registry settings and
values.
Does this need to happen on the workstation side or on the server side?
As, I had mentioned in my previous reply, that I have the "Enterprise
Domain
Controller Security Template". Is there something that this would be
causing
an issue and I need to change some settings on the security side.
Local Security Policy MMC snap-in
1. Click Start, point to Programs, point to Administrative Tools, and
then click Local Security Policy.
Note If you cannot perform this step because "Administrative Tools"
does not show up in the Program list, then click Start, point to Settings,
point to Control Panel, click Administrative Tools, and then click Local
Security Policy. Then proceed to step two.
2. Under Security Settings, double-click Local Policies, and then
click Security Options.
3. Double-click Additional restrictions for anonymous connections,
and
then click No access without explicit anonymous permissions under Local
policy setting.
4. Restart the member computer or domain controller for the change to
take effect.
Back to the top
RestrictAnonymous registry value
Use Registry Editor to view the following registry key, and then add the
following value to this key, or modify it if the value already exists:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\LSA
Value: RestrictAnonymous
Value Type: REG_DWORD
Value Data: 0x2 (Hex)
Restart the computer after any change to the RestrictAnonymous key in the
registry.
Felix said:
Hi Alan & Steve,
Thanks for the information and the reply. I have not done any modifications
yet. But, I would like to know something as this has been a political issue
in my organization. They are questioning me that all these were working fine
when were were in Windows 2000 Server and how after moving to Windows
2003
server, that these problems are coming up.
They think, that I am kinda not doing my job properly. I see that there are
many users who are having an issue and problems. But, people do not
understand that so many things need to be changed or it might be the OS
issue itself. They want an easy way to find something to point fingers at
you. So, I would suggest that Microsoft should give some clear instructions
saying that when we migrate from Windows 2000 to Windows Server 2003 we have
issues like this or some other permissions need to be checked or enabled.
Like Steve had mentioned, that you had changed the settings in the "Desktop
Group Policy" access this computer only from the network. Where is this
settings?
My Windows Server 2003 domain controllers have Enterprise Member Server
Security template installed also, so , I am wondering whether that might be
causing the problem. But, just a thought. And to provide more details that,
it is happening on both WinXP and Windows 2000 machines.
thanks in advance for your replies.
Alan Morris said:
there a a few things that can cause this. If the queue view of the printer
connection shows access denied but the users can print fine, this is
the
server getting access denied when attempting to update the job information
in the queue view.
http://support.microsoft.com/default.aspx?scid=kb;en-us;162695
SMSINST: "Access Denied" Error Message When You Try to Connect to a Shared
Network Printer
needs to be set to 1
http://support.microsoft.com/default.aspx?scid=kb;en-us;246261
How to Use the RestrictAnonymous Registry Value in Windows 2000
"Steve M" <> wrote in message
I think I found it. The desktop group policy has "Access this
computer from the network" set to only Administrators. When I added
Users it worked. So the User needs to be able to access his own PC
over the network. Who would think.
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
I am also experiencing the same issue from migrating my printers from
a
Windows 2003 standard server to another W2K3 Standard server using
the
printer migration utility 3.1.
I am curious of the fix that you stated from your previous reply? Thanks.
--
Thanks,
Mike
:
the spooler on the print server is getting access denied when connecting
to
the clients to update queue status
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no
rights.
Migrated printers from Windows 2000 to Windows Server 2003 using Print
Migrator 3.1. Everything went fine. Users when the click on the printer
or
connect to it, a message "access denied, cannot connect" appears
in
red,
which should usually be "ready" in green.
Users can print to the printer, but this is what is happening
after the
migration. Anything I am missing?
