Bug 2216813
| Summary: | Samba don't shared printer by documentation Fedora | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mike <mixask8> | ||||||||||
| Component: | samba | Assignee: | Guenther Deschner <gdeschner> | ||||||||||
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 38 | CC: | abokovoy, aboscatt, anoopcs, asn, gdeschner, jstephen, lmohanty, pfilipen, sbose, ssorce | ||||||||||
| Target Milestone: | --- | Keywords: | Documentation, Question, Reopened, WorkAround | ||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2023-07-04 12:15:49 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Mike
2023-06-22 18:13:09 UTC
Created attachment 1972134 [details]
samba config
Section home and tmp created for testing working samba
Created attachment 1972136 [details]
cups config
I think it is better to take a look at the RHEL documentation. The Fedora one is out of date and we are investigating if we could sync it with the RHEL one. Here is the link: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/configuring_and_using_network_file_services/assembly_using-samba-as-a-server_configuring-and-using-network-file-services#assembly_setting-up-samba-as-a-print-server_assembly_using-samba-as-a-server Does that help? Documentation has been updated, please check https://docs.fedoraproject.org/en-US/fedora/latest/system-administrators-guide/servers/File_and_Print_Servers/ I read RHEL documantation. I don't understand what changes on Fedora docs (have old screenshot - section Printer Configuration) On Fedora Server config smb the out of box have all settings. Printer is sharing, but gnome observer don't find printer until then ip address entry. I successfully added printer without manually configure in smb, but i can't printed. In queue created job with message - SpliX Cannot open job. I hide section print$ and set `use client driver` for printer. But nothing sense. On laptop driver have. I have same issue when i try printed via ipp, but after change drivers on ipp evertwhere all works fine (it's will be on another machine), but this case i have corrected drivers. Even manual sharing didn't help Hi Mike, Thanks for getting back. Can you please elaborate further? It is quite hard to follow your previous message. In summary, what is the issue, what have you done and the current status? Did you allow samba browsing in the firewall rules? Kind regards I installed Fedora Server 38 on my miniPC Installed CUPS, Splix (needed for my printer), SAMBA. Entered to cockpit and disable firewall and SELinux - easy way. SAMBA settings have all needed settings out of the box. I just change workgroup. In CUPS i don't changes anything. Now if i try added my printer my laptop where stay Fedora Workstation 38 i can find my printer if i enter ip-address my miniPC in gnome printer observer. Printer added fine, but now if i try send to print i have error on CUPS in queue - SpliX Cannot open job. In previous my approach my printer needed shared to manually in samba but print working. Now if i does set manually sharing in SAMBA printing too don't working. May be something in CUPS? My new current config in attachment. Created attachment 1975634 [details]
samba 2 config
Created attachment 1975635 [details]
cups 2 config
What you describe in comment #7 seems to be an unrelated issue to the documentation. I would suggest to open a new bug for this. Please provide log level 10 logs reproducing the issue, see: https://hackmd.io/@asn/SkHk8rXBz |