[cpac]

Hello - wanted to check on the boards to see if anyone else has found that the SAMBA security update released yesterday broke their ability to print to windows network printers.

All was going well for me before, but I hadn't printed in a while and so I cant be positive it was the SAMBA update that broke the printing...

Anyone?

[RMXO]

Originally posted by cpac:
Hello - wanted to check on the boards to see if anyone else has found that the SAMBA security update released yesterday broke their ability to print to windows network printers.

All was going well for me before, but I hadn't printed in a while and so I cant be positive it was the SAMBA update that broke the printing...

Anyone?

yeap, i cant print via SMB either. shucks!

[masternew]

I can't print either, what's up wid that!. Does anybody figure out what is going on.

[cpac]

so any SAMBA gurus out there know how to fix it?

(The error Print Center encounters is "Unable to connect to SAMBA host, will retry in 60 seconds")

[mdc]

*omg* you guys gave me the biggest fright of my life, well next to the one i got yesterday when my computer said i was getting 60% for math

i have a paper due friday that i need to print out, and i read that the security update i installed yesterday disables samba printing.

i just printed from word and it printed fine.


so the question is, what is differnet on my setup that i can print with the update installed?

[cpac]

sorry for the scare - if you've got it working, then its good to know there's a way. I'm not sure what the difference could be. Here's a list of guesses?

So:
firewall on at all?
able to print from cocoa apps (e.g. TextEdit) as well as from carbon (Word)?
sort of printer/means of networking?

I set up printing initially by following these instructions:

Originally posted by The DJ:

...

SMB (Windows). This one is a tad harder. You need to type the following command in the Terminal.

code:

sudo ln -s `which smbspool` /usr/lib/cups/backend/smb ENTER


Now restart the printing system. I did this by simply restarting my Mac (it's so fast these days ;-).
To add a windows networked printer follow the instructions for adding a LPD server. I the device list you will see "Windows printer via SAMBA" has been added. Use the following format for the printer address :

code:


smb://userass@workgroup/server/sharename


Only server and sharename (printername) are mandatory the others are optional.

Is this how you set it up?

Anything else you (or anyone) can think of?

[RMXO]

sudo ln -s `which smbspool` /usr/libexec/cups/backend/smb

thats what i typed in to redo my smb. not sure if it works yet. but will update once i get it to work. might have to re-install the update again.

[cpac]

wow - just checking using the "go" menu, it appears there's no "cups" folder in /usr/lib/

so will re-entering the above code recreate the necessary directories and things, or is the lack of this folder symptomatic of CUPS being screwed up in some basic way?

[cpac]

Two questions for those in the know:

should the proper terminal entry include

/usr/libexec/...

or

/usr/lib/...?

The libexec directory exists on my computer, but the lib doesn't (anymore?) and so entering the line of code I quoted above results in a "directory does not exist" error...

[pimephalis]

Interesting problem. I suspect it likely has something to do with your symlinks if you can't print.

I installed the security update, and can print just fine. My symlink wasn't wiped out by the update, and I apparently have no trouble printing from Safari, tex-edit or Preview.

Check your symlinks and the permissions on them to make sure you can actually run the smbspool program as a user.

[cpac]

Originally posted by pimephalis:
Check your symlinks and the permissions on them to make sure you can actually run the smbspool program as a user.

I'd love to - how do I do this?

[pimephalis]

Originally posted by cpac:
I'd love to - how do I do this?

Ah-ha! The famous ls-la command from the terminal.

You should check the permissions on both the symlink and on smbspool. Mine are as follows:

Code:
ls -la /usr/bin/smbspool

-rwxr-xr-x    1 root     wheel      637920 Mar 24 18:30 /usr/bin/smbspool

You can see, in the far left column, there are ten spaces. The first will be either blank or will contain a 'd' to represent files and directories, respectively. The next nine spaces are in fact three triplets of three which indicate the permissions available to the file's owner, the group and other people. So, on my system this line of ten spaces tells me that smbspool is a file, that the owner can read, write and execute the file, and that the 'group' members and other people can read and execute the file. Good, this means that myself (the Administrator), any other users and programs should be able to run smbspool.

Code:
ls -la /usr/libexec/cups/backend/smb

lrwxr-xr-x  1 root  wheel  17 Mar  5 15:29 /usr/libexec/cups/backend/smb -> /usr/bin/smbspool

OK, now we see that my symlink from /usr/lib.../smb to smbspool has the same permissions. Good again; so I should be able to use that program nicely, and thus I can print.

Try looking at those two files with the ls -la command, and see if some of the permissions are out of whack.

HTH

[cpac]

D'oh.

No differences at all - I get the *exact* same results you did back...

Other guesses?

[mitchell_pgh]

Ummm.... I blame Microsoft...

[masternew]

Are we the only ones having this problem?, I checked my permissions and they are correct. Are any of the guys having this problem on a Linksys Wireless Router?. For example I am using my iBook (Wireless), the PC is using ethernet. Does anybody have the same setup. I 'm just trying to see if we have something in common.

[pimephalis]

Originally posted by masternew:
Are we the only ones having this problem?, I checked my permissions and they are correct. Are any of the guys having this problem on a Linksys Wireless Router?. For example I am using my iBook (Wireless), the PC is using ethernet. Does anybody have the same setup. I 'm just trying to see if we have something in common.

I have the exact same setup, and it works fine. Can you produce pdfs? I mean, using print to file, does the pdf work alright? Can you mount shares on the PC connected to the printer? Can you ping that computer?

If you can mount shares, then it's certainly restricted to the printing subsystem.

Other thoughts: Are you using gimp-print drivers? Or native apple drivers? I use a gimp-print driver and it seems to work just fine.

[masternew]

I can mount shares, I can ping the PC fine, I can create PDF's. I still can't print. Pime please guide me through the procedure of setting the printer again. I have tried several ways and still nothing!. I had it working great but after the install I got nothing. Do you set up the printer thru the PRINT CENTER or do you use the localhost:631 managar to set it up?. Thank in advanced.

[RMXO]

i still cant print. i checked wut pinephalis typed & i have those links. sucks that i cant print.

this is the first time ever i updated & something broke. guess i had a good run. ehhehe

[masternew]

i still cant print. i checked wut pinephalis typed & i have those links. sucks that i cant print.

this is the first time ever i updated & something broke. guess i had a good run. ehhehe



_____

ME TOO !!!!!

[cpac]

I'm trying to print over wireless at my law school - I can connect to the internet, connect to a variety of shares, including (I believe) the share where the printer spool resides. I can create .pdfs, and I can print fine when I'm at home, it's just the SAMBA printing that's ge****d.

The error returned by print center is that it couldn't connect to the SAMBA host - does the security update prevent SAMBA from connecting to Windows machines that might not have been updated?

[RMXO]

****. stupid me killed my system while uninstalling the update. i had to archive & re-install. dumbass me was drinking while doing this & installed the dumb SMB update again. argh. never update your system while drunk. now i cant print again. argh. too lazy to redo system & not update that SMB patch.

u guys might want to try this out. its takened from the apple support site.

http://discussions.info.apple.com/We...PV.4@.3bc0decf

I too checked mine after reading this post and also could not print any longer to my shared printer on my XP box after samba update. I tried upgrading to a new version of print-gimp with no luck. I deleted my back end link and re-established it as described above with no luck. But I did get it to work again and this is what fixed it. Using the CUPs console at http://127.0.0.1:631/ to modify the printer I re-entered the Device url info which displayed this: smb://workgroupname/servername/devicename. I re-entered it just like this smb://loginassword@workgroupname/servername/devicename and then completed the rest of the process and a rebooted. I then could print again. It still displays the Device url as before less the user id and password smb://workgroupname/servername/devicename, but I guess it just needed the login info re-entered one time to work again. Try it.

sadly it didnt work for me. daym, now i have to transfer files over to my XP box then use RDC to print.

[pimephalis]

Originally posted by masternew:
I can mount shares, I can ping the PC fine, I can create PDF's. I still can't print. Pime please guide me through the procedure of setting the printer again. I have tried several ways and still nothing!. I had it working great but after the install I got nothing. Do you set up the printer thru the PRINT CENTER or do you use the localhost:631 managar to set it up?. Thank in advanced.

I used the print-center, then through a browser tweaked some settings using the cupsd daemon directly.

Just looking through my logs shows that I haven't had a job go bad in nearly a month, so I'm not sure what I'm doing differently than the rest of you. Someone mentioned usernames and passwords above, and I should point out that I'm printing to a publicly available (well, to the 3 computers in our house, anyway) printer that has no password protection.

Further information about my setup: I'm printing to an hp laserjet on a win 98 box. Perhaps some of you are printing to printers connected to XP?

I'd suggest that everyone try configuring their printers through http://localhost:631, seeing as you can more precisely fine-tune your settings. Also, check your error logs. They can be found in /var/log/samba

This is all very weird.

[cpac]

Originally posted by pimephalis:
I'd suggest that everyone try configuring their printers through http://localhost:631, seeing as you can more precisely fine-tune your settings. Also, check your error logs. They can be found in /var/log/samba

This is all very weird.

No such luck configuring printers that way.

Here's the last bit of the error log:

Samba name server 12-254-179-43 is now a local master browser for workgroup LAW on subnet 12.254.179.43

*****
[2002/09/07 08:21:46, 0] /SourceCache/samba/samba-21/source/libsmb/nmblib.c:send_udp(756)
Packet send failed to 12.254.179.255(138) ERRNO=No route to host
[2002/09/07 08:21:46, 0] /SourceCache/samba/samba-21/source/libsmb/nmblib.c:send_udp(756)
Packet send failed to 12.254.179.255(138) ERRNO=No route to host
[2002/09/07 08:21:46, 0] /SourceCache/samba/samba-21/source/nmbd/nmbd.c:reload_interfaces(259)
reload_interfaces: No subnets to listen to. Shutting down...
[2002/09/10 13:31:31, 0] /SourceCache/samba/samba-21/source/nmbd/nmbd.c:main(783)
Netbios nameserver version 2.2.3a started.
Copyright Andrew Tridgell and the Samba Team 1994-2002
[2002/09/10 16:21:05, 0] /SourceCache/samba/samba-21/source/nmbd/nmbd.c:sig_term(63)
Got SIGTERM: going down...

[pimephalis]

Originally posted by cpac:
No such luck configuring printers that way.

Here's the last bit of the error log:

'No route to host'. Ok, that's informative. That means that the samba spooler can't find the host you're trying to print to. Do you have the firewall on on your mac? Could it be blocking that port? You say you can ping the machine and event mount shares but not print, right?


Herm.....

[masternew]

Man, I am feeling so frustrated!, this is truly the first time I have ever had a problem with an update, I always thought of myself as lucky because of this. Well any way on to the problem. I look at the logs, and it seems that they are the same as everybody else.

No firewalls, no permission!, is there anyone who can figure this out, I know I can't.

[cpac]

Originally posted by pimephalis:
'No route to host'. Ok, that's informative. That means that the samba spooler can't find the host you're trying to print to. Do you have the firewall on on your mac? Could it be blocking that port? You say you can ping the machine and event mount shares but not print, right?


Herm.....

I can definitely mount shares no problem. I do have my firewall on, (but it worked before with it on). Is there a particular port number I need to open up to allow for SAMBA printing?

herm... indeed.

[pimephalis]

As for the ports samba uses, it should be 137-139 if I'm not mistaken.

Reading OSXhints.com today gave me an idea. Have you tried printing to the printer with its IP rather than samba name? I mean your entry in the Print Center would be like this:

smb://192.168.1.120/sharename

rather than

smb://tributary/sharename

The reason I think this may work is the strange 'no route to host' problem. I think that smbspool might be having some trouble finding the computer you're printing to by name, so try the IP address instead.

[masternew]

So I guess nobody else is having this problem, since we are ltting this thread die.

Update:

Still not able to print thru SMB, I email Apple to report the bug, I guess there is nothing much else I can do. Gurus Please help out!.

[RMXO]

Possible fix.

http://discussions.info.apple.com/We...i.12@.3bc0decf

go to the last post. he will tell you how to do it. basically u replace smbclient & smbspool with an older copy. or a copy before the update.

/usrbin/smbspool

/usr/bin/smbclient

i replaced it but havent reboot or logged out to test if it works yet. will post once i do.

[edddeduck]

Originally posted by mitchell_pgh:
Ummm.... I blame Microsoft...

Always a good excuse!!!!

Edwin

[cpac]

Originally posted by RMXO:
Possible fix.

Here's what the post says, for those that don't want to follow the link

Originally posted by Benjamin Iseman on Apple's Boards:
Here you go:

http://homepage.mac.com/beniseman/FileSharing3.html

Keep in mind that using these files will most likely re-introduce the security bug that the update was designed to fix. Accordingly, use these at your own risk.

The procedure I followed was to delete all of the samba printers on my machine via http://127.0.0.1:631/printers. I then logged in as root and made a copy of the newer smb files and saved them to the root desktop. Finally I replaced the smb files mentioned above and restarted. When I added the printers via http://127.0.0.1:631/printers everything worked right away.

HTH,

Ben

I'm going to give it a shot...

[cpac]

rather than going through the hassle of logging in as root to copy these files to the right directory - anybody in the unix world want to show us how to do it with a nice little sudo terminal command?

I'm new to UNIX, but my understanding would be that it would be something like:

sudo cp -f ~/Desktop/smbspool /usr/bin/

AND

sudo cp -f ~/Desktop/smbclient /usr/bin/

can somebody who knows more confirm that this is what ought to be done?

[RMXO]

okie. status update. i tried using his smbspool & smbclient & when trying to print my printer ended up rejecting every job. was bored & just did an archive & reinstall.

Im using a 800 DVI w/ gimp-print. i will post a link to smbclient & smbspool for ppl that want to use it. these 2 files are before the SMB patch.

actually i would back up those 2 files first.

go to the dir that those 2 files are located & do:

this backups the files

sudo cp smbspool smbspool.bak
sudo cp smbclient smbclient.bak

sudo cp smbclient smbspool /usr/bin
or
sudo cp smbclient /usr/bin
sudo cp smbspool /usr/bin

the -f is a force command. no need to force it there

or

if you dont want to use terminal then you can do this. use finder GO > go to folder > /usr/bin

then just make a copy of those 2 files then put in some where safe in another folder. then drag the new files into /usr/bin


okie go to this link to get pre-smb update smbclient & smbspool. my laptop is a 800 DVI.

http://homepage.rmxo.net/sonnyn/misc/files/

the file you want to get is smb-files.tgz & you are welcome to DL any other files in there if you want.

[cpac]

Originally posted by RMXO:
the -f is a force command. no need to force it there

or

if you dont want to use terminal then you can do this. use finder GO > go to folder > /usr/bin

then just make a copy of those 2 files then put in some where safe in another folder. then drag the new files into /usr/bin

You can't do this unless you're logged in as root - which is what I wanted to avoid doing.

Since I cant delete the files that are currently in /usr/bin, don't I need to force the copy to occur? (i.e. to overwrite the files that are there?

[RMXO]

you dont have to be root to do this. you have admin priviliges right?

sudo = super user when using terminal

rem to back them up

if ppl havent noticed i provided a link that you can DL my 2 smb files. this is from a fresh system that has all the updates except the SMB patch.

[cpac]

Originally posted by RMXO:
you dont have to be root to do this. you have admin priviliges right?

sudo = super user when using terminal

rem to back them up

Ok, figured that part out. I've replaced the files with the ones from your server, but no dice: here's what I've noticed:

(1) setting up the printer via print center (option-click add, select advanced) does not list "Windows Printer via SAMBA" as it used to, now it just lists "Unknown Network Device (smb)"

(2) Selecting this option allows you to set up a printer just like normal except now, the printer queue gets stopped every time you attempt to print. No error message appears, it just attempts to, and fails, to start the queue.

Does this help anyone in diagnosing things?

[ADDENDUM]

It doesn't fix things to set up the printer via the whole web page thing either...

[RMXO]

Originally posted by cpac:
Ok, figured that part out. I've replaced the files with the ones from your server, but no dice: here's what I've noticed:

(1) setting up the printer via print center (option-click add, select advanced) does not list "Windows Printer via SAMBA" as it used to, now it just lists "Unknown Network Device (smb)"

(2) Selecting this option allows you to set up a printer just like normal except now, the printer queue gets stopped every time you attempt to print. No error message appears, it just attempts to, and fails, to start the queue.

Does this help anyone in diagnosing things?

[ADDENDUM]

It doesn't fix things to set up the printer via the whole web page thing either...

yes i got that error too. tried so many things but to no avail. thats why i just put in my Jag CD & did an archive & install. everything works now.

sorry my files didnt work for u. i hoped it would since a few ppl from Apple Support Discussion board said it worked for them.

[nobitacu]

Hmmm... good info, at least now I can figure out how to print off our windows network printers...

Ming

[pimephalis]

Originally posted by RMXO:
you dont have to be root to do this. you have admin priviliges right?

sudo = super user when using terminal

rem to back them up

if ppl havent noticed i provided a link that you can DL my 2 smb files. this is from a fresh system that has all the updates except the SMB patch.

I'm sorry to hear that this hasn't worked for other people. I'd love to know what is going on here, seeing as I did the Security Update (I'm a bleeding edger), and I have had no problems printing to my home network.

As for the unix commands, instead of rem-ing files and cp -f stuff, you should be using the 'mv' command -- it moves the files and cuts out the 'delete' step.

For example:

Code:
 
sudo mv /usr/bin/smbspool /usr/bin/smbspool.bak
sudo mv ~/Desktop/smbspool /usr/bin/smbspool

As a final note, you might want to think about restricting the executable permissions on those files that you aren't using or might have a security hole. For example:

chmod a-x /usr/bin/smbspool.bak
chmod go-x /usr/bin/smbspool

HTH

[morrismh]

I installed the older versions of smbclient and smbspool and all is well again. Thanks to all who worked through this issue and found a solution!

[pimephalis]

Originally posted by morrismh:
I installed the older versions of smbclient and smbspool and all is well again. Thanks to all who worked through this issue and found a solution!

I'm glad someone got this working, but it would be nice to know what the actual problem was. Frustrating thing is that something must be broken in the code; I did all the troubleshooting I could think of and everything checked out fine.

Must be a broken line in the source code.