Ticket Options
Question Details
TICKET ARCHIVE -> Windows 2003 Server & OSX 10.39
rboklewski - Mar 16, 2006 - 12:59 pm
Well ive tried everywhere, so i guess ill try here. We currently have a Windows NT print server supporting our macintosh osx and windows xp clients. There are no issues with this print server whatsoever. However, im testing printing through another server, but it is windows server 2003. I installed the printer using tcp/ip and turned on the mac printing services. I can see the printer in the appletalk window on my mac osx client and i go to install it and choose the same ppd file as i would if i were installing a printer from the current windows NT print server (I don't know if that is right, or if there is another ppd i should be using) But when i go to print from any website or QuarkXpress i get an error page.
%%[Error: syntax; OffendingCommand:-nostringval--]%%
%%[Flushing: rest of the job (to end of file)will be ignored]%%
When i go back to install the same printer from the NT server using the same ppd, it works perfectly. Can i not use 2003 server for printing with OSX? Or am i doing something wrong with appletalk on the 2003 server. Please Help!!
%%[Error: syntax; OffendingCommand:-nostringval--]%%
%%[Flushing: rest of the job (to end of file)will be ignored]%%
When i go back to install the same printer from the NT server using the same ppd, it works perfectly. Can i not use 2003 server for printing with OSX? Or am i doing something wrong with appletalk on the 2003 server. Please Help!!
stottm - Mar 19, 2006 - 11:27 am
You should not need AppleTalk at all. OS X can do TCP/IP and ActiveDirectory and Windows File & Printer Sharing. On the Mac look under /Applications/Utilities/Directory Access and unlock it then double-click on the Active Directory entry and configure it for the Win2k3 Active Directory domain. Then add the printer by selecting More Printers and Windows Printing and browse to the print queue and add it and select the PPD - print driver.
Alternatively, you can just go to the Printer Setup Utility and Option-Click on the More Printers button. Select Advanced then Windows Printer via Samba.
This is on Tiger 10.4.5 but it should be very close to Panther 10.3.9.
Alternatively, you can just go to the Printer Setup Utility and Option-Click on the More Printers button. Select Advanced then Windows Printer via Samba.
This is on Tiger 10.4.5 but it should be very close to Panther 10.3.9.
rboklewski - Mar 20, 2006 - 4:10 pm
Well..I tried hooking it up to active directory and it didn't work. It said domain name incorrect or something like that. I did some research and it said that if you have a .local attached to your domain name then you have to go through the process of running a script in the bash terminal. I tried, but the directions were shotty on the apple website. I got to the second line of the script and the code they give doesn't work after that. Anywho, im not really worried about the AD right now, i know it would be nice to have, but right now i just want to be able to use the printers on the 2003 print server through appletalk. I know its old, but that is the ideal way to do it right now for where we are. Let me know if you have any ideas on what i may be doing wrong with the appletalk.
stottm - Mar 21, 2006 - 9:24 am
"but right now i just want to be able to use the printers on the 2003 print server through appletalk. I know its old, but that is the ideal way to do it right now for where we are".
AppleTalk is all but obsolete. I don't know of anyone using it unless they are running old Mac OS 9 systems.
OS X can talk full Windows SMB/CIFS "Windows File and Printer Sharing" so you should be able to attach straight to the printers via Windows printer and sharing. Try turning off the AppleTalk and try it the Windows way.
i.e. perhaps, I confused you... You don't have to bind to the Active Directory to print to those printers, it will just make it easier. BTW, you may wish to consult with someone who administers the AD domain as you need to know how AD works in depth to connect a Mac properly. AD is confusing; I know people who had to take week long classes to learn how to properly set it up and configure it. That said, it should be easy to connect to AD if you are given the right information to connect and have an account on AD that has permissions to add computers to the domain. Joining the domain should be done if at all possible as it makes it much easier to administer the printers and the Mac's user accounts and their other network privileges.
Without using AD make sure the printers are shared under Win2k3. Click Print & Fax in System Preferences on the Mac. Click the plus button to add a printer. Click More Printers and choose Windows Printer. Browse Network Neighborhood for the server and printer shares. If you can't browse the server or printers hold down the Option(alt) button and click More Printers button again. Choose Advanced instead of Windows Printer. Drop down the device list and you have many more options. AppleTalk, AppSocket/HP JetDirect, LDP/LPR Host or Printer, and Windows Printer via Samba.
That last one you can specify the Windows printer via:
smb://servername/sharename
smb://workgroup/server/sharename
smb://workgroup@servername/sharename
smb://workgroup;username@servername/sharename
smb://user
assword@workgroup/server/sharename
smb://userassword@server/sharename
Substitute the AD Domain Name instead of Workgroup. Try using the fully qualified domain name if the short name doesn't work. Authenticate to the printer using an AD user name and password. If prompted for Workgroup, put the domain name there instead.
I'll reopen the ticket incase anyone else can help with the AppleTalk configuration. But you should know that it is not the mainstream solution.
AppleTalk is all but obsolete. I don't know of anyone using it unless they are running old Mac OS 9 systems.
OS X can talk full Windows SMB/CIFS "Windows File and Printer Sharing" so you should be able to attach straight to the printers via Windows printer and sharing. Try turning off the AppleTalk and try it the Windows way.
i.e. perhaps, I confused you... You don't have to bind to the Active Directory to print to those printers, it will just make it easier. BTW, you may wish to consult with someone who administers the AD domain as you need to know how AD works in depth to connect a Mac properly. AD is confusing; I know people who had to take week long classes to learn how to properly set it up and configure it. That said, it should be easy to connect to AD if you are given the right information to connect and have an account on AD that has permissions to add computers to the domain. Joining the domain should be done if at all possible as it makes it much easier to administer the printers and the Mac's user accounts and their other network privileges.
Without using AD make sure the printers are shared under Win2k3. Click Print & Fax in System Preferences on the Mac. Click the plus button to add a printer. Click More Printers and choose Windows Printer. Browse Network Neighborhood for the server and printer shares. If you can't browse the server or printers hold down the Option(alt) button and click More Printers button again. Choose Advanced instead of Windows Printer. Drop down the device list and you have many more options. AppleTalk, AppSocket/HP JetDirect, LDP/LPR Host or Printer, and Windows Printer via Samba.
That last one you can specify the Windows printer via:
smb://servername/sharename
smb://workgroup/server/sharename
smb://workgroup@servername/sharename
smb://workgroup;username@servername/sharename
smb://user
assword@workgroup/server/sharename smb://user
assword@server/sharename Substitute the AD Domain Name instead of Workgroup. Try using the fully qualified domain name if the short name doesn't work. Authenticate to the printer using an AD user name and password. If prompted for Workgroup, put the domain name there instead.
I'll reopen the ticket incase anyone else can help with the AppleTalk configuration. But you should know that it is not the mainstream solution.
rboklewski - Mar 21, 2006 - 11:03 am
I tried using the windows printing and i started printing a project in quark and it started printing a bunch of pages with garbage on it.
rboklewski - Mar 21, 2006 - 11:18 am
Okay, i could print from a website and microsoft programs, but not quark using windows printing, so it is working. How come quark is giving me issues. I have to have printing working for quark, because that is the application that is mainly used here. Yeah, i know i shouldn't be using appletalk, but that is what is being used and there are only 28 machines in our office, 11 being macs. I just don't understand why appletalk won't work on server 2003, i can see the printers in appletalk, but it just prints that stuff out i posted above.
rboklewski - Mar 21, 2006 - 5:18 pm
I was able to print using windows printing and changing the setting in the options tab---> Data tab, from binary to ASCII. It worked!! Wow this took forever. I hope this is a true fix and not just a quick fix.
TechSupport - Mar 24, 2006 - 5:30 pm
This ticket has been moved to the open forums for more exposure.
Please follow this link:
http://www.macosx.com/forums/showthread.php?t=270015
Please follow this link:
http://www.macosx.com/forums/showthread.php?t=270015
IF THIS IS YOUR QUESTION AND YOU WISH TO RESPOND, LOGIN HERE FIRST.
