How to Access a Windows Shared Printer from Puppy 4

How to do things, solutions, recipes, tutorials
Message
Author
stevetimar
Posts: 2
Joined: Tue 23 Sep 2008, 20:49

Access a windows shared printer

#31 Post by stevetimar »

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?

newbie314
Posts: 127
Joined: Tue 19 Aug 2008, 05:35

#32 Post by newbie314 »

I've got this working, but I can only do it with the name of the computer.
I would like to do that by IP number instead.
I've tried but smb doesn't seem to connect that way.

I would prefer this, then most likely I can connect a puppy to a puppy machine with no issue for printing.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#33 Post by rcrsn51 »

I would prefer this, then most likely I can connect a puppy to a puppy machine with no issue for printing.
Do you mean that you want to connect a printer to a Puppy machine and make it available to other networked Puppy machines?

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.

newbie314
Posts: 127
Joined: Tue 19 Aug 2008, 05:35

#34 Post by newbie314 »

Okay I didn't know that.
I thought I needed to set the samba server.
So how do I access the network printer (on a Puppy Machine) from the CUPS (on another Puppy Machine)?
How does it show up?

Also, I would still like to connect from Puppy->Win printer, but through IP and not name. Can I do this?

newbie314
Posts: 127
Joined: Tue 19 Aug 2008, 05:35

#35 Post by newbie314 »

So how do I see the networked printer in CUPS?
Network printer is on a puppy machine.
The machine I'm trying to connect from is a puppy machine.
Do I use IP? What option in the CUPS configuration?
Thanks

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#36 Post by rcrsn51 »

Go to CUPS admin on the Puppy client machine and open the Printers list. The networked printer on the host machine should be there automatically. You don't need to go through an install procedure. Just make that printer the default for the client machine.

newbie314
Posts: 127
Joined: Tue 19 Aug 2008, 05:35

#37 Post by newbie314 »

Okay I'll check if it's there, maybe tonight.
I'm running on 4.0 and the client is on wireless.

Do I have do to the SMB fix in the beginning of the post?

newbie314
Posts: 127
Joined: Tue 19 Aug 2008, 05:35

#38 Post by newbie314 »

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.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#39 Post by rcrsn51 »

Other Puppy users have reported problems with wireless printing and were unable to get it working. Please report back if you find a solution.

newbie314
Posts: 127
Joined: Tue 19 Aug 2008, 05:35

#40 Post by newbie314 »

Nothing yet.
Can I use IP for printer access and how?

Is this fixed in 4.1?

I find it surprising that wireless should be any different as it's just a network.

gerry
Posts: 986
Joined: Thu 26 Jul 2007, 21:49
Location: England

#41 Post by gerry »

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

newbie314
Posts: 127
Joined: Tue 19 Aug 2008, 05:35

#42 Post by newbie314 »

Would that IP work for puppy to puppy linking

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#43 Post by rcrsn51 »

@gerry: Thanks for that suggestion. I have added it to the original post. Hopefully, it will help other users with printing problems. By any chance, are you printing over a wireless network?

newbie314
Posts: 127
Joined: Tue 19 Aug 2008, 05:35

#44 Post by newbie314 »

Looks like it works on wireless to the win machine
Took out Admin and it still worked.

Will have to try puppy to puppy again :S

gerry
Posts: 986
Joined: Thu 26 Jul 2007, 21:49
Location: England

#45 Post by gerry »

@rcrsn51- sorry, no. Still good old wires...

Gerry

newbie314
Posts: 127
Joined: Tue 19 Aug 2008, 05:35

#46 Post by newbie314 »

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).

newbie314
Posts: 127
Joined: Tue 19 Aug 2008, 05:35

#47 Post by newbie314 »

Needed Adminstrator for Puppy to Windows

gerry
Posts: 986
Joined: Thu 26 Jul 2007, 21:49
Location: England

#48 Post by gerry »

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.)

george.mf
Posts: 2
Joined: Wed 31 Dec 2008, 16:08

What worked for me

#49 Post by george.mf »

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.

User avatar
rcrsn51
Posts: 13096
Joined: Tue 05 Sep 2006, 13:50
Location: Stratford, Ontario

#50 Post by rcrsn51 »

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?

Post Reply