Re: Network printing from Mac OSX 10.4.9
- From: "Richard Perry" <RichardPerry@xxxxxxxxxxxxxxxx>
- Date: Sat, 5 May 2007 16:09:59 -0700
Yes, I know it is a GPO that is affecting this.
Yes, I created another GPO, applied it to the OU that holds the server and enforced it.
Yes, I used RSOP to verify that the server was using the expected settings.
The server showed everything correctly, however the problem persists. Therefore, the only conclusion that I can come to is that I am using the wrong settings. The settings that I am using are documented in the following article:
http://simultaneouspancakes.com/Lessons/archives/2004/12/how_to_disable.shtml
I would like to point out that our Mac clients are able to connect to file shares just fine as we are prompted for credentials at the time of connection. However, the adding of a printer remains another story.
Richard
"Charlie" <baboon@xxxxxxxxxxxxxx> wrote in message news:BBED59FC-B844-4175-B9C3-9353A690436C@xxxxxxxxxxxxxxxx
You say that as soon as you join the print server to the domain, you have the
problem, so you have figured out that there must be a GPO applied to the
domain or an OU that affects this.
You also say that you applied a test policy that overrides the SMB signing
policy. Where did you create the policy? If it was a local policy, that
won't hold up to a domain or OU applied policy. If you want to make sure
that the correct policy is applied, then apply the policy that disables SMB
signing to the OU that the server is directly a member of.
Most importantly though, you need to run rsop.msc to see what policies are
actually being applied to the server and from where.
"Richard Perry" wrote:
I have several Mac OS X clients on our network, and they are joined to our
2003 AD domain.
About a year ago when I first tested this, I was able to print from the Mac
client directly to the Server 2003 print shares without issue. These are IP
printers on the Server 2003 print server then shared as AD printers.
A few weeks ago, when we actually installed a printer in our Mac lab, it was
discovered that the Mac clients were unable to print. The message varies,
but regularly displays the message 'nt_status_access_denied' on the Mac
client.
I have read several articles that all point to SMB signing on the default
domain policy as being the problem. However, when I create a test policy
that counteracts the SMB signing requirement, and apply it to a test print
server, I am still having the same problem with the Mac clients.
On a stand-alone Server 2003 (aka not joined to the domain), I am able to
print just fine from the Mac client to the server. As soon as I join this
server to the domain, printing stops.
Can anyone please help me zero in on the exact problem and exact fix?
Richard
.
- Follow-Ups:
- Re: Network printing from Mac OSX 10.4.9
- From: Baboon
- Re: Network printing from Mac OSX 10.4.9
- From: "Ken Zhao [MSFT]"
- Re: Network printing from Mac OSX 10.4.9
- Prev by Date: Re: Tape Backup Failing
- Next by Date: Re: how to map a drive remotely-monitor disk
- Previous by thread: Re: Remote Control through Sonicwall
- Next by thread: Re: Network printing from Mac OSX 10.4.9
- Index(es):
Relevant Pages
|
