Re: Cannot print from OS X 103 to windows 2003 print server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Chris Inacio (inacio+msnews_at_ece.cmu.edu)
Date: 11/05/04

  • Next message: Tony: "Re: Cannot print from OS X 103 to windows 2003 print server" 
    Date: Fri, 05 Nov 2004 09:44:49 -0500

     From your CUPS configuration, what did you use as your SMB UNC type
    path name. It would have to include your username/password in order to
    authenticate to the server to print. That error message seems to
    indicate that you haven't authenticated to the server and are trying to
    print. At least that's what I make of it.

    I think this version of the address

      smb://winuser:password@workgroup/server/printer

    where you actually have to fill in "winuser" and "password" would be
    required.

    I'm mostly guessing here, since I've only tried doing this to Win XP
    (Home/Pro) not any of the server editions, and no domain controllers
    present.....

    Let me know if this helps at all, and I'll update that web page.

    Chris

    Tony wrote:
    > I tried following:
    > http://users.adelphia.net/~inacio/Printing_Mac_OSX_To_Windows.html
    >
    > to print to a printer setup on my windows 2003 server. I am trying to use
    > SMB but no luck.
    >
    >
    > The security log error on win2k3 box is
    >
    > Event Type: Failure Audit
    > Event Source: Security
    > Event Category: Logon/Logoff
    > Event ID: 529
    > Date: 11/4/2004
    > Time: 9:31:51 AM
    > User: NT AUTHORITY\SYSTEM
    > Computer: win2k3
    > Description:
    > Logon Failure:
    > Reason: Unknown user name or bad password
    > User Name: user
    > Domain: DOMAIN
    > Logon Type: 3
    > Logon Process: NtLmSsp
    > Authentication Package: NTLM
    > Workstation Name: MACOSX
    > Caller User Name: -
    > Caller Domain: -
    > Caller Logon ID: -
    > Caller Process ID: -
    > Transited Services: -
    > Source Network Address: x.x.x.x
    > Source Port: 0
    >
    >
    > For more information, see Help and Support Center at
    > http://go.microsoft.com/fwlink/events.asp.
    >
    >
    > Any ideas? I cannot print. Also our DOmain is setup to use only NTLM v2 and
    > above. Is that a problem with OS X?
    >
    >

  • Next message: Tony: "Re: Cannot print from OS X 103 to windows 2003 print server"

    Relevant Pages

    • Re: Native Mode possible problems...help!
      ... their password will still be able to logon to an NT 4.0 - but using their ... Windows 2003/2000/NT ... > They NT 4.0 domain controllers will still be able to authenticate users, ... > Why not just upgrade the BDCs to Windows 2000 Server? ...
      (microsoft.public.windows.server.general)
    • How to prevent user from logon?
      ... How do I set up a policy within Active Directory that will only authenticate ... how do I prevent a user account from having logon ... with a specialized server on our end. ...
      (microsoft.public.win2000.security)
    • Re: Advanced Digest Authentication Failure
      ... An IIS 6.0 server setup on a Windows Server 2003 Domain Controller is no ... authenticate clients using Advanced Digest Authentication, ... : Logon Failure: ... : Caller User Name: - ...
      (microsoft.public.inetserver.iis.security)
    • Re: Win2K and NT4 question
      ... During logon, the client ... What OS is running on these clients? ... >from the NT4 server. ... >What I would like to do is have everyone authenticate to the NT4 server ...
      (microsoft.public.win2000.security)
    • Re: Requiring User Name and Password for Connection to Network Res
      ... If you don't have a matching account on the server, and if the Guest account on ... then the server should request that you authenticate ...
      (microsoft.public.windowsxp.network_web)