Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '10.4: Fix an NT_STATUS_LOGON_FAILURE printing error' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
10.4: Fix an NT_STATUS_LOGON_FAILURE printing error
Authored by: imageworx on May 30, '05 07:46:24AM

Hey, this worked! I was getting "NT_STATUS_NO_MEMORY" error prior as it couldn't print to the domain. I changed my Domain to default "WORKGROUP" and tried this listed procedure and viola! It printed out this solution.
Note: I hadn't tried this since 10.4.1 updater. And as a resolution, I made my mac share my HP1200 USB to my PC, rather than other way around.

Side Note: I couldn't get the localhost:CUPS access to work as it asked for password. It doesn't allow me to login and reading the CUPS dox, it requires the root password to be setup and used. Great tip though (the CUPS port and info)!

---
To BeOS or Not to BeOS



[ Reply to This | # ]
10.4: Fix an NT_STATUS_LOGON_FAILURE printing error
Authored by: bdz on Apr 18, '06 12:59:51PM

I was getting NT_STATUS_LOGON_FAILURE sometimes and sometimes NT_STATUS_NO_MEMORY when I tried to print to a Windows shared printer from a domain. I found out that the fact that my windows account password had a ^ (caret) in it and this was making printing impossible. To get it working I went into my keychain and deleted my smb entry, deleted the printer and readded it with a different user's credentials, and although it did not work right away it ended up working as soon as I restarted my computer (the keychain stuff was probably being cached from before). I read in an AppleCare document that if a Windows resource has a "special character" or space in its name (be it a user, a machine, or unbelievably a password) then you can get the NT_STATUS_ kinds of errors. I hope this helps someone.



[ Reply to This | # ]