RH 7.2 LPAR, which I'd like to do printserving for windows clients. New to windows networking, limited knowledge of samba and print, but have been reading. I'm using samba 2.2.5-1 installed via RPM. Ideally the print administrator would manage access to the print-queues remotely from his win2k box.
Am I understanding correctly, that if I hand-off user/group checks to winbind in my nsswitch.conf, that NT ACL's can be enforced without jumping through hoops on the linux system? So that print admin can restrict access to some printers based on already established NT groups? Can print admin manage the actual samba print shares from his win2k box? If the only way is with swat, can this be done as non-root? Also, need to be able to reroute print queues to a different printer without losing jobs in queue, so the print jobs can go to a printer at a different ip while the original destination of the queue gets serviced. Best I can come up with right now is firing up printconf, modifying the ip address for the queue and restarting lpd. So queue names stay the same and only the destination ip changes without jobs getting lost... but is there a better way? If they print to an alias for a queue and the alias gets switched to point to a different queue, do jobs already sitting in the queue get redirected appropriately? I'm definitely still just getting my feet wet... have yet to add a machine account for the linux server yet, but I have authentication to the NT PDC, and am able to use samba shared printers (though no cover page for some reason). From what I've read, looks like for winbind I will need to have NT Admin add machine account to PDC. Or is there a way to experiment with winbind without bothering NT admins yet? How much will lack of broadcast hurt? In smb.conf I went with the interface=a.b.c.d/24. The tests at http://us1.samba.org/samba/docs/DIAGNOSIS.html that rely on broadcast fail as you'd expect TEST 6: # nmblookup -d 2 '*' added interface ip=a.b.c.d bcast=a.b.c.255 nmask=255.255.255.0 querying * on a.b.c.255 name_query failed to find name * TEST 10: # nmblookup -M TCS_MAIN_DOM querying TCS_MAIN_DOM on a.b.c.255 name_query failed to find name TCS_MAIN_DOM#1d I just want to make sure I don't bark up any wrong trees. Thanks to anyone who takes the time to answer anything, ~ Daniel
