Re: Access Denied, Cannot connect

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" <jfkind@xxxxxxxxxxx> wrote in message
news:%23y4VIGeTGHA.4600@xxxxxxxxxxxxxxxxxxxxxxx
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 [MSFT]" <alanmo@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eFrGdBTTGHA.4952@xxxxxxxxxxxxxxxxxxxxxxx
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
news:<eOSLaTbQFHA.2584@xxxxxxxxxxxxxxxxxxxx>...

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.

"Mike A." <manselmo@xxxxxxxxxxxxxxxxx> wrote in message
news:D427EADB-7B99-4F95-9604-DFAE60582937@xxxxxxxxxxxxxxxx
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


"Alan Morris [MSFT]" wrote:

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.

"Felix" <jfkind@xxxxxxxxxxx> wrote in message
news:eFEKUqGSGHA.2276@xxxxxxxxxxxxxxxxxxxxxxx
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?












begin 666 uparrow.gif
M1TE&.#EA"@`*`/<``````( ```" `(" ````@( `@ " @(" @,# P/\```#_
M`/__````__\`_P#______P``````````````````````````````````````
M````````````````````````````````````````````````````````````
M````,P``9@``F0``S ``_P`S```S,P`S9@`SF0`SS `S_P!F``!F,P!F9@!F
MF0!FS !F_P"9``"9,P"99@"9F0"9S "9_P#,``#,,P#,9@#,F0#,S #,_P#_
M``#_,P#_9@#_F0#_S #__S,``#,`,S,`9C,`F3,`S#,`_S,S`#,S,S,S9C,S
MF3,SS#,S_S-F`#-F,S-F9C-FF3-FS#-F_S.9`#.9,S.99C.9F3.9S#.9_S/,
M`#/,,S/,9C/,F3/,S#/,_S/_`#/_,S/_9C/_F3/_S#/__V8``&8`,V8`9F8`
MF68`S&8`_V8S`&8S,V8S9F8SF68SS&8S_V9F`&9F,V9F9F9FF69FS&9F_V:9
M`&:9,V:99F:9F6:9S&:9_V;,`&;,,V;,9F;,F6;,S&;,_V;_`&;_,V;_9F;_
MF6;_S&;__YD``)D`,YD`9ID`F9D`S)D`_YDS`)DS,YDS9IDSF9DSS)DS_YEF
M`)EF,YEF9IEFF9EFS)EF_YF9`)F9,YF99IF9F9F9S)F9_YG,`)G,,YG,9IG,
MF9G,S)G,_YG_`)G_,YG_9IG_F9G_S)G__\P``,P`,\P`9LP`F<P`S,P`_\PS
M`,PS,\PS9LPSF<PSS,PS_\QF`,QF,\QF9LQFF<QFS,QF_\R9`,R9,\R99LR9
MF<R9S,R9_\S,`,S,,\S,9LS,F<S,S,S,_\S_`,S_,\S_9LS_F<S_S,S___\`
M`/\`,_\`9O\`F?\`S/\`__\S`/\S,_\S9O\SF?\SS/\S__]F`/]F,_]F9O]F
MF?]FS/]F__^9`/^9,_^99O^9F?^9S/^9___,`/_,,__,9O_,F?_,S/_,____
M`/__,___9O__F?__S/___RP`````"@`*```(( `?"!Q(D*",@@,/'BRX\$%#
1AP(7/D2(<")%BA8O/@@(`#L`
`
end

.

Relevant Pages

  • SecurityFocus Microsoft Newsletter #164
    ... Got Storage Security Risks? ... MICROSOFT VULNERABILITY SUMMARY ... Chat Client FTP Server Default Username Credential Weak... ... NetServe Web Server is a compact web server for Microsoft Windows ...
    (Focus-Microsoft)
  • Re: im being held in memory
    ... How can I harden my computer or server to secure it from hackers? ... Use firewall software and hardware and antivirus software that is ... Follow the instructions for hardening Windows and IIS at ... Install all service packs and security fixes from Microsoft and otherwise ...
    (microsoft.public.security)
  • MS and security: good effort but no cigar
    ... build upon the progress it's already made in security. ... The low-hanging fruit of millions of insecure Windows machines ... Then there's the issue of poorly secured server applications. ... and execute external virus and filtering ...
    (microsoft.public.windowsxp.general)
  • SecurityFocus Microsoft Newsletter #167
    ... MICROSOFT VULNERABILITY SUMMARY ... Multiple Vendor XML Parser SOAP Server Denial Of Service Vul... ... Proactive Windows Security Explorer ...
    (Focus-Microsoft)
  • Re: Group Policy broke my DCs
    ... to be very careful with tweaking services on domain controllers. ... Group Policy - security policy at the OU level which makes it much easier to ... complied from the Windows 2003 Server Security guide for baseline core ... Server - automatic ...
    (microsoft.public.windows.group_policy)