access denied, unable to connect

[Jason Gallas]

I receive this message when trying to view current print jobs on my windows
2000 server shared printers.

 

[Alan Morris\(MSFT\)]

This is the server getting access denied talking to the spooler on the
client.

If you have rolled out some additional security on the clients you can see
this.

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
--
Alan Morris
Microsoft 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.

 

[Jason Gallas]

Hmm, that is strange. I looked at the registry for the server in question
and it already has the value set to 1 for the second link that you gave me.
The first website link referred to SMS which I don't have. I did however
look at the registry keys and for nullsessionpipes I had the following:

COMNAP
COMNODE
SQL\QUERY
SPOOLSS
EPMAPPER
LOCATOR
TrkWks
TrkSvr
TMRPC\AgentRPC
CERT
TMRPC\SPNTSVC

for nullsession shares I have:

COMCFG
DFS$
inventory$

What else would I need to change to resolve client systems not being able to
see print jobs on the shared printers on the server?

This is the server getting access denied talking to the spooler on the
client.

If you have rolled out some additional security on the clients you can see
this.

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
--
Alan Morris
Microsoft 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 receive this message when trying to view current print jobs on my windows
2000 server shared printers.

 

[Alan Morris\(MSFT\)]

You need to check this on the client. The spooler service on the server is
getting denied access when it contacts the spooler on the client. The
clients displays the information that is returned by the spooler on the
server when one opens the queue view on the client. In this case the server
gets access denied to the client and that is what you see on the client.

Make a file share on the client and connect to it from the server and see if
that gets the authentication stream corrected.

--
Alan Morris
Microsoft 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.

Hmm, that is strange. I looked at the registry for the server in question
and it already has the value set to 1 for the second link that you gave me.
The first website link referred to SMS which I don't have. I did however
look at the registry keys and for nullsessionpipes I had the following:

COMNAP
COMNODE
SQL\QUERY
SPOOLSS
EPMAPPER
LOCATOR
TrkWks
TrkSvr
TMRPC\AgentRPC
CERT
TMRPC\SPNTSVC

for nullsession shares I have:

COMCFG
DFS$
inventory$

What else would I need to change to resolve client systems not being able to
see print jobs on the shared printers on the server?

This is the server getting access denied talking to the spooler on the
client.

If you have rolled out some additional security on the clients you can see
this.

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
--
Alan Morris
Microsoft 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 receive this message when trying to view current print jobs on my windows
2000 server shared printers.

 

[Jason Gallas]

This is happening on every client though! It is a systemwide problem, not
just limited to one client. I have read elsewhere on the web that this has
to do with some new security patch but don't know if that is bogus or not.
I suppose I can connect to the default share on each client to hopefully
resolve this but it seems kind of ridiculous that it is all of the sudden
happening out of nowhere.

You need to check this on the client. The spooler service on the server is
getting denied access when it contacts the spooler on the client. The
clients displays the information that is returned by the spooler on the
server when one opens the queue view on the client. In this case the server
gets access denied to the client and that is what you see on the client.

Make a file share on the client and connect to it from the server and see if
that gets the authentication stream corrected.

--
Alan Morris
Microsoft 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.

Hmm, that is strange. I looked at the registry for the server in question
and it already has the value set to 1 for the second link that you gave me.
The first website link referred to SMS which I don't have. I did however
look at the registry keys and for nullsessionpipes I had the following:

COMNAP
COMNODE
SQL\QUERY
SPOOLSS
EPMAPPER
LOCATOR
TrkWks
TrkSvr
TMRPC\AgentRPC
CERT
TMRPC\SPNTSVC

for nullsession shares I have:

COMCFG
DFS$
inventory$

What else would I need to change to resolve client systems not being

able

to
see print jobs on the shared printers on the server?

This is the server getting access denied talking to the spooler on the
client.

If you have rolled out some additional security on the clients you can see
this.

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
--
Alan Morris
Microsoft 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 receive this message when trying to view current print jobs on my
windows
2000 server shared printers.

 

[Alan Morris\(MSFT\)]

When the client sees access denied in the queue view but can still print,
the server is really the one that is getting denied access. I had not heard
this related to a security patch. Did you check the lsa reg key on one of
the clients?

--
Alan Morris
Microsoft 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.

This is happening on every client though! It is a systemwide problem, not
just limited to one client. I have read elsewhere on the web that this has
to do with some new security patch but don't know if that is bogus or not.
I suppose I can connect to the default share on each client to hopefully
resolve this but it seems kind of ridiculous that it is all of the sudden
happening out of nowhere.

You need to check this on the client. The spooler service on the server is
getting denied access when it contacts the spooler on the client. The
clients displays the information that is returned by the spooler on the
server when one opens the queue view on the client. In this case the server
gets access denied to the client and that is what you see on the client.

Make a file share on the client and connect to it from the server and

see

if
that gets the authentication stream corrected.

--
Alan Morris
Microsoft 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.

Hmm, that is strange. I looked at the registry for the server in question
and it already has the value set to 1 for the second link that you

gave
me.

The first website link referred to SMS which I don't have. I did however
look at the registry keys and for nullsessionpipes I had the following:

COMNAP
COMNODE
SQL\QUERY
SPOOLSS
EPMAPPER
LOCATOR
TrkWks
TrkSvr
TMRPC\AgentRPC
CERT
TMRPC\SPNTSVC

for nullsession shares I have:

COMCFG
DFS$
inventory$

What else would I need to change to resolve client systems not being

able

to
see print jobs on the shared printers on the server?

This is the server getting access denied talking to the spooler on the
client.

If you have rolled out some additional security on the clients you

can
see

this.

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
--
Alan Morris
Microsoft 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 receive this message when trying to view current print jobs on my
windows
2000 server shared printers.

 

[Glenn-David Lind]

I have just the same problem.

On all my clients and on my terminal servers I get the same message as you.
The message does not appear on the domain controller...
The problem occurred after installing some security updates on the print
server and on the domain controllers.


GDL

This is happening on every client though! It is a systemwide problem, not
just limited to one client. I have read elsewhere on the web that this has
to do with some new security patch but don't know if that is bogus or not.
I suppose I can connect to the default share on each client to hopefully
resolve this but it seems kind of ridiculous that it is all of the sudden
happening out of nowhere.

You need to check this on the client. The spooler service on the server is
getting denied access when it contacts the spooler on the client. The
clients displays the information that is returned by the spooler on the
server when one opens the queue view on the client. In this case the server
gets access denied to the client and that is what you see on the client.

Make a file share on the client and connect to it from the server and

see

if
that gets the authentication stream corrected.

--
Alan Morris
Microsoft 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.

Hmm, that is strange. I looked at the registry for the server in question
and it already has the value set to 1 for the second link that you

gave
me.

The first website link referred to SMS which I don't have. I did however
look at the registry keys and for nullsessionpipes I had the following:

COMNAP
COMNODE
SQL\QUERY
SPOOLSS
EPMAPPER
LOCATOR
TrkWks
TrkSvr
TMRPC\AgentRPC
CERT
TMRPC\SPNTSVC

for nullsession shares I have:

COMCFG
DFS$
inventory$

What else would I need to change to resolve client systems not being

able

to
see print jobs on the shared printers on the server?

This is the server getting access denied talking to the spooler on the
client.

If you have rolled out some additional security on the clients you

can
see

this.

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
--
Alan Morris
Microsoft 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 receive this message when trying to view current print jobs on my
windows
2000 server shared printers.

 

[Jason Gallas]

Actually it was a DNS issue. I had made some changes to the DHCP server and
how it reports to DNS. I changed it from "dynamically update dns only if
requested" to "always update dns" and I had problems. I then deleted the
client DNS records and set it to the default "dynamically update dns" in
the dhcp settings. The problem revolved around the IP of the client being
incorrectly set in DNS, so the print server could not verify the client
name. Now that all of the clients dns names and ip addresses are resolved
it is working fine.

When the client sees access denied in the queue view but can still print,
the server is really the one that is getting denied access. I had not heard
this related to a security patch. Did you check the lsa reg key on one of
the clients?

--
Alan Morris
Microsoft 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.

This is happening on every client though! It is a systemwide problem, not
just limited to one client. I have read elsewhere on the web that this has
to do with some new security patch but don't know if that is bogus or not.
I suppose I can connect to the default share on each client to hopefully
resolve this but it seems kind of ridiculous that it is all of the sudden
happening out of nowhere.

You need to check this on the client. The spooler service on the

server
is

getting denied access when it contacts the spooler on the client. The
clients displays the information that is returned by the spooler on the
server when one opens the queue view on the client. In this case the server
gets access denied to the client and that is what you see on the client.

Make a file share on the client and connect to it from the server and

see

if
that gets the authentication stream corrected.

--
Alan Morris
Microsoft 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.

Hmm, that is strange. I looked at the registry for the server in question
and it already has the value set to 1 for the second link that you gave
me.
The first website link referred to SMS which I don't have. I did however
look at the registry keys and for nullsessionpipes I had the following:

COMNAP
COMNODE
SQL\QUERY
SPOOLSS
EPMAPPER
LOCATOR
TrkWks
TrkSvr
TMRPC\AgentRPC
CERT
TMRPC\SPNTSVC

for nullsession shares I have:

COMCFG
DFS$
inventory$

What else would I need to change to resolve client systems not being able
to
see print jobs on the shared printers on the server?

This is the server getting access denied talking to the spooler on the
client.

If you have rolled out some additional security on the clients you can
see
this.

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
--
Alan Morris
Microsoft 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 receive this message when trying to view current print jobs on my
windows
2000 server shared printers.