Discussion Locked

UNIX Unable to See W2K Shared Printer

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a SCO UNIX server on our Windows NT 4.0 Network and we have set up local printers attached to Windows clients as Remote Windows Printers for the UNIX application to access the printers. I need to replace one our W95 clients with a Windows 2000 Pro PC, but I can't get the UNIX Server to see the shared printer on the Windows 2000 local port. I am guessing it is something in the Windows 2000 Pro security settings that is prohibiting the UNIX server from seeing the share, since the same scenario works if the client is a W98 or W95 PC. If anyone has any suggestions or solutions, it would be greatly appreciated.

11 replies

by qb

How are you setup to print to them, by URL? ie \\computername\printername or even \\ipaddress\printername. And I'm asuming that you right clicked on the printer and shared it right? Also there is a security setting in the properties of the printerin w2k, and I not quite sure how w2k is going authenticate a user that is not authenticated by your server, if you know what I mean. You might want to try adding users to the security tab ones like the group "anonymous logon" or "guest", I'm shooting in the dark but these are things that I would try.

by sgandenberger

Thanks for the input, but it did not help. The UNIX routes the printer output to a remote Windows printer as \\windowsclientname\printersharename. The printer is successfully shared in Windows as other Windows network client can access and printto the printer. I followed your suggestions for granting permissions to guest and anonymous logon, but I still could not access the printer from the UNIX Server. I even haded the windows client to /etc/hosts file. I believe the key is in your statement, " how w2k is going authenticate a user that is not authenticated by your server." If we new the answer to that question, I think we could get it to work.

by jwilczyn

I think, that first - you need to install Print Services for Unix and configure it. Then Unix clients can connect to the IP address of the Win2000 Unix print server and then to the specific queue.

by sgandenberger

Print Services are installed on the UNIX server and we are able to print to over 20 attached Windows Remote Printers as long as the host Windows machine is running W95 or W98.

by qb

I just wanted to let you know that I don't have any other ideas, sorry.

by jfjester

you would have to set up your windows security with exact name of the device connecting to- guest and annomous will not log on unless that is the name assigned - if you log onto a system with a name that is the security rights that have to be assigned. same with drive mappings and things- Windows 2000 is very security independent- try also loading the print services with unix drivers - this will push out options to unix when you log in

I hope this helps some

by michaelmeboy

As stated in other responses, the first thing to do is install file and print services for Unix in the Windows components setup.

I would print to the printer from SCO by using Internet Printing, are you running Samba? How does SCO resolve the Windows box names? Do you have a reverse lookup for the LPD in your DNS server? Are you using DNS? Once you install Unix Services, Win2K will want to use DNS for the printer so DNS has to be set right. This is how you should (IMHO) print to the Win2K box. If you are using SMB, I would look to WINS for answers. If you are running DNS then the problem most likely lies there.

This discussion is closed to new replies.