How to Access a Windows Shared Printer from Puppy 4
-
- Posts: 2
- Joined: Tue 23 Sep 2008, 20:49
Access a windows shared printer
I am using the shared name. I even tried inserting the workgroup name after:smb://. It did not work. I communicate via a Orinoco wireless PC card to a Linksys wireless access point, which uses encryption. I connect to the internet, so I should be able to connect to the printer.
Any other suggestions?
Any other suggestions?
Do you mean that you want to connect a printer to a Puppy machine and make it available to other networked Puppy machines?I would prefer this, then most likely I can connect a puppy to a puppy machine with no issue for printing.
If this is your intent, you don't need to do anything! Once you have CUPS running, it will automatically broadcast its presence to other Puppy computers.
No go.
I can't see my HP on the host.
Host ->wired
client ->wireless
Interesting I can see a printer on the host cups that is on my client, although I can't communicate with it.
So summary
Host can see client printers but can't communicate
Client can't see Host printers at all.
Wonder if the firewall is doing something.
I can't see my HP on the host.
Host ->wired
client ->wireless
Interesting I can see a printer on the host cups that is on my client, although I can't communicate with it.
So summary
Host can see client printers but can't communicate
Client can't see Host printers at all.
Wonder if the firewall is doing something.
Just for the record, for those who keep getting "Cannot connect to CIFS host", I've got my printer going in Puppy 4.1 with the printer address set to:
smb://Administrator@windows_IP_address/printer_share_name
That is literally "//Administrator@", you don't have to put anything else instead.
Took a lot of Googling.....
Gerry
smb://Administrator@windows_IP_address/printer_share_name
That is literally "//Administrator@", you don't have to put anything else instead.
Took a lot of Googling.....
Gerry
Okay puppy to puppy is still not working through wireless.
Interesting enough when I do nbtscan for the IP of the host nothing comes up even though it does have a static IP.
Is it a port thing?
If I made computer a samba server, would I have better luck getting into the host from puppy (wireless of course).
Interesting enough when I do nbtscan for the IP of the host nothing comes up even though it does have a static IP.
Is it a port thing?
If I made computer a samba server, would I have better luck getting into the host from puppy (wireless of course).
Well, it stopped working AGAIN.
After a lot of work, during which I found in Puppy 4.1.1 that smb.conf in /etc/ is a symlink to /opt/samba/smb.conf which neither Pfind nor I could find, I eventually hit on the solution. Having done all the above, and copied smb.conf across from Puppy 3.01, all to no avail, I found that Pnethood is the answer.
Do Menu > Network > Pnethood Samba Shares
Make sure "Use cifs" box is ticked.
If all is well, you should see a line with print$ in it. Click on Connect.
Now go to the application that you wish to print from, and print!
The "cannot connect to cifs host" messages in cups are banished.
I have not tried removing the smb.conf file- so it may or may not be needed. EDIT: it is not needed, I removed it to see.
EDIT: Of course, this Pnethood connection is not permanent, and needs to be re-connected every time you boot.
Gerry (who is keeping his fingers crossed that this time it will keep on working, instead of being a flash in the pan.)
After a lot of work, during which I found in Puppy 4.1.1 that smb.conf in /etc/ is a symlink to /opt/samba/smb.conf which neither Pfind nor I could find, I eventually hit on the solution. Having done all the above, and copied smb.conf across from Puppy 3.01, all to no avail, I found that Pnethood is the answer.
Do Menu > Network > Pnethood Samba Shares
Make sure "Use cifs" box is ticked.
If all is well, you should see a line with print$ in it. Click on Connect.
Now go to the application that you wish to print from, and print!
The "cannot connect to cifs host" messages in cups are banished.
I have not tried removing the smb.conf file- so it may or may not be needed. EDIT: it is not needed, I removed it to see.
EDIT: Of course, this Pnethood connection is not permanent, and needs to be re-connected every time you boot.
Gerry (who is keeping his fingers crossed that this time it will keep on working, instead of being a flash in the pan.)
What worked for me
After much frustration trying to connect to my Canon PIXMA IP4000 on a Windows XP computer the following worked.
smb://work-group-name/computer-name/CanonPIX%20IP4000
The share name on the XP is CanonPIXIP4000. Being a new Puppy user, I don't know what the "%20" is doing, but I found it by using a Live CD for XUBUNTU and browsing for available shared printers.
smb://work-group-name/computer-name/CanonPIX%20IP4000
The share name on the XP is CanonPIXIP4000. Being a new Puppy user, I don't know what the "%20" is doing, but I found it by using a Live CD for XUBUNTU and browsing for available shared printers.
Good work! The %20 suggests that that there is an embedded space in the Windows name of the printer. It looks like Windows drops the space when it displays the name, but Linux needs to use it.
I wonder what would happen if you went back to Windows and shortened the name to just eight letters, like CANONPIX?
Also, is the work-group-name necessary to connect on your system?
I wonder what would happen if you went back to Windows and shortened the name to just eight letters, like CANONPIX?
Also, is the work-group-name necessary to connect on your system?