- WLUG - wlug.mailman3.com

Re: [Wlug] printer still sick

by Charles R. Anderson

On Sat, Feb 23, 2002 at 03:58:15PM -0500, Bill Mills-Curran wrote: subssn594> bcurran_newguy> nmblookup BERTHA subssn594> querying BERTHA on 192.168.1.255 subssn594> name_query failed to find name BERTHA subssn594> bcurran_newguy> nmblookup bertha subssn594> querying bertha on 192.168.1.255 subssn594> name_query failed to find name bertha subssn594> subssn594> But, ping works. (I'm using static ip's behind the firewall.) subssn594> subssn594> bcurran_newguy> ping 192.168.1.11 Be sure there is no firewall on the Red Hat box: /sbin/service ipchains stop /sbin/service iptables stop and also try these: nmblookup -R -U 192.168.1.11 BERTHA nmblookup -R -U 192.168.1.11 -A 192.168.1.11 nmblookup -R -A 192.168.1.11 nmblookup -R BERTHA

Feb. 23, 2002

Re: [Wlug] printer still sick

by Bill Mills-Curran

On Sat, 23 Feb 2002, Frank Sweetser wrote: > Date: Sat, 23 Feb 2002 15:39:11 -0500 > From: Frank Sweetser <fs(a)WPI.EDU> > Reply-To: wlug(a)mail.wlug.org > To: wlug(a)mail.wlug.org > Subject: Re: [Wlug] printer still sick > > > On occasion =) > > Try doing > > nmblookup BERTHA > > This should broadcast to see what IP address responds to the WINS name of > BERTHA. If nothing responsds, BERTHA isn't answering, or now thinks it has > a different name. > Failed... bcurran_newguy> nmblookup BERTHA querying BERTHA on 192.168.1.255 name_query failed to find name BERTHA bcurran_newguy> nmblookup bertha querying bertha on 192.168.1.255 name_query failed to find name bertha But, ping works. (I'm using static ip's behind the firewall.) bcurran_newguy> ping 192.168.1.11 PING 192.168.1.11 (192.168.1.11) from 192.168.1.12 : 56(84) bytes of data. Warning: time of day goes back, taking countermeasures. 64 bytes from 192.168.1.11: icmp_seq=0 ttl=128 time=455 usec > Another thought - you say you're behind a linksys firewall box. Is this box > set up to provide static addresses, or is it possible that it changed > BERTHA's IP address out from underneath the poor unsuspecting print clients > to something other than 192.168.1.11? > > -- > Frank Sweetser fs at wpi.edu, fs at suave.net | $ x 16 > Full-time WPI Network Tech, Part time Linux/Perl guy | > I have a great diet. You're allowed to eat anything you want, but you must > eat it with naked fat people. --Ed Bluestone > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > Bill Mills-Curran subssn594(a)charter.net 508 836-3160 (home)

Feb. 23, 2002

Re: [Wlug] printer still sick

by Bill Mills-Curran

On Sat, 23 Feb 2002, Frank Sweetser wrote: > Date: Sat, 23 Feb 2002 15:23:29 -0500 > From: Frank Sweetser <fs(a)WPI.EDU> > Reply-To: wlug(a)mail.wlug.org > To: wlug(a)mail.wlug.org > Subject: Re: [Wlug] printer still sick > > On Sat, Feb 23, 2002 at 03:28:40PM -0500, Bill Mills-Curran wrote: > > I updated a lot of stuff, including anything that had to do with printing, > > and I still can't print. > > > > I'm wondering if the virus scanner I put on the PC could be the problem -- > > I've disabled it (as much as I can) but I'm suspicious. > > > > This looks bad... > > > > > > bcurran_newguy> cat .login | smbclient '//BERTHA/CANON' -I 192.168.1.11 -N > > -c 'print -' > > added interface ip=192.168.1.12 bcast=192.168.1.255 nmask=255.255.255.0 > > session request to BERTHA failed (Called name not present) > > session request to *SMBSERVER failed (Called name not present) > > Aha - smbclient is unable to find a machine identifying itself with a windows > name of BERTHA. This virus scanner you mention may very well be the culprit - > a number of them also include some level of firewall functionality which may be > interfering. > > Can you browse 192.168.1.11 from any other machines on your network? > > -- > Frank Sweetser fs at wpi.edu, fs at suave.net | $ x 16 > Full-time WPI Network Tech, Part time Linux/Perl guy | > I have a great diet. You're allowed to eat anything you want, but you must > eat it with naked fat people. --Ed Bluestone > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug > Frank, Same result from a 6.2 RedHat machine. I did not install the McAfee firewall option because I'm already behind a linksys firewall. Do you offer phone support? :-) Bill Bill Mills-Curran subssn594(a)charter.net 508 836-3160 (home)

Feb. 23, 2002

Re: [Wlug] printer still sick

by Frank Sweetser

On Sat, Feb 23, 2002 at 03:42:55PM -0500, Bill Mills-Curran wrote: > On Sat, 23 Feb 2002, Frank Sweetser wrote: > > Aha - smbclient is unable to find a machine identifying itself with a > > windows name of BERTHA. This virus scanner you mention may very well be > > the culprit - a number of them also include some level of firewall > > functionality which may be interfering. > > Frank, > > Same result from a 6.2 RedHat machine. I did not install the McAfee > firewall option because I'm already behind a linksys firewall. > > Do you offer phone support? :-) On occasion =) Try doing nmblookup BERTHA This should broadcast to see what IP address responds to the WINS name of BERTHA. If nothing responsds, BERTHA isn't answering, or now thinks it has a different name. Another thought - you say you're behind a linksys firewall box. Is this box set up to provide static addresses, or is it possible that it changed BERTHA's IP address out from underneath the poor unsuspecting print clients to something other than 192.168.1.11? -- Frank Sweetser fs at wpi.edu, fs at suave.net | $ x 16 Full-time WPI Network Tech, Part time Linux/Perl guy | I have a great diet. You're allowed to eat anything you want, but you must eat it with naked fat people. --Ed Bluestone

Feb. 23, 2002

printer still sick

by Bill Mills-Curran

I updated a lot of stuff, including anything that had to do with printing, and I still can't print. I'm wondering if the virus scanner I put on the PC could be the problem -- I've disabled it (as much as I can) but I'm suspicious. This looks bad... bcurran_newguy> cat .login | smbclient '//BERTHA/CANON' -I 192.168.1.11 -N -c 'print -' added interface ip=192.168.1.12 bcast=192.168.1.255 nmask=255.255.255.0 session request to BERTHA failed (Called name not present) session request to *SMBSERVER failed (Called name not present) I don't know what this problem is. Ok, and the status.bertha from the print queue, too, at the end I'm floundering. TIA, Bill **************************************************************** IF filter 'mf_wrapper' filter msg - '<</PrintQuality(Normal)>>setpagedevice' at 2002-02-23-15:01:05.862 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter msg - '<</BitsPerPixel 24>>setpagedevice' at 2002-02-23-15:01:05.862 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter msg - '<</ProcessColorModel /DeviceCMYK>>setpagedevice' at 2002-02-23-15:01:05.862 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter msg - '<</PrintColors 15>>setpagedevice' at 2002-02-23-15:01:05.863 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter msg - '<</HWResolution[360 360]>>setpagedevice' at 2002-02-23-15:01:05.863 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter msg - 'foomatic-gswrapper: gs '-dBATCH' '-dSAFER' '-dQUIET' '-dNOPAUSE' '-sDEVICE=bjc600' '-sOutputFile=/dev/fd/3' '-' 3>&1 1>&2' at 2002-02-23-15:01:05.872 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter msg - 'closing *main::KID3' at 2002-02-23-15:01:06.714 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter msg - 'closed *main::KID3' at 2002-02-23-15:01:06.714 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter msg - 'tail process done writing data to *main::STDOUT' at 2002-02-23-15:01:11.524 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter msg - 'KID4 finished' at 2002-02-23-15:01:11.524 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter msg - 'KID3 finished' at 2002-02-23-15:01:11.525 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter msg - 'Main process finished' at 2002-02-23-15:01:11.525 ## A=<NULL> number=102 process=3162 IF filter 'mf_wrapper' filter finished at 2002-02-23-15:01:11.539 ## A=<NULL> number=102 process=3162 printing finished at 2002-02-23-15:01:11.539 ## A=<NULL> number=102 process=3162 LP filter msg - 'cat: write error: Broken pipe' at 2002-02-23-15:01:11.539 ## A=<NULL> number=102 process=3162 waiting for printer filter to exit at 2002-02-23-15:01:11.539 ## A=<NULL> number=102 process=3162 accounting at end at 2002-02-23-15:01:11.540 ## A=<NULL> number=102 process=3162 finished 'cfA102newguy.mills.curran', status 'JFAIL' at 2002-02-23-15:01:11.540 ## A=<NULL> number=102 process=3162 subserver pid 3162 exit status 'JFAIL' at 2002-02-23-15:01:11.541 ## A=<NULL> number=0 process=3103 job 'cfA102newguy.mills.curran', attempt 3, allowed 3 at 2002-02-23-15:01:11.542 ## A=<NULL> number=102 process=3103 send_failure_action 'JREMOVE' at 2002-02-23-15:01:11.542 ## A=<NULL> number=102 process=3103 job 'cfA102newguy.mills.curran', removing job - status JREMOVE at 2002-02-23-15:01:11.542 ## A=<NULL> number=102 process=3103 removing job 'cfA102newguy.mills.curran' - JREMOVE at 2002-02-23-15:01:11.543 ## A=<NULL> number=102 process=3103

Feb. 23, 2002

Re: [Wlug] printer still sick

by Frank Sweetser

On Sat, Feb 23, 2002 at 03:28:40PM -0500, Bill Mills-Curran wrote: > I updated a lot of stuff, including anything that had to do with printing, > and I still can't print. > > I'm wondering if the virus scanner I put on the PC could be the problem -- > I've disabled it (as much as I can) but I'm suspicious. > > This looks bad... > > > bcurran_newguy> cat .login | smbclient '//BERTHA/CANON' -I 192.168.1.11 -N > -c 'print -' > added interface ip=192.168.1.12 bcast=192.168.1.255 nmask=255.255.255.0 > session request to BERTHA failed (Called name not present) > session request to *SMBSERVER failed (Called name not present) Aha - smbclient is unable to find a machine identifying itself with a windows name of BERTHA. This virus scanner you mention may very well be the culprit - a number of them also include some level of firewall functionality which may be interfering. Can you browse 192.168.1.11 from any other machines on your network? -- Frank Sweetser fs at wpi.edu, fs at suave.net | $ x 16 Full-time WPI Network Tech, Part time Linux/Perl guy | I have a great diet. You're allowed to eat anything you want, but you must eat it with naked fat people. --Ed Bluestone

Feb. 23, 2002

Re: [Wlug] HELP!! printer woes

by Tom Guilderson

> > And as for printing - it's kind of a bad example. They revamped the printing > system because it included suport for a *whole* lot more printers. And > while yeah, there were some issues with it (mostly related to specific printer > drivers, IIRC) they are updates out there for them. > I did notice that the number of printers supported appeared to be significantly greater. I also liked the newer set up utilities etc. - I thought they were definitely better and I think that long term it is the right direction - maybe they should have released both the old and new - giving the user the option to try the latest or use a known stable version. That way they can get the latest version out there for those that want and need it, and also provide a known stable version for those that do not have the time "try" a new version, but just need to get stuff done. Especially for what is to many people a core utility such as printing.

Feb. 23, 2002

Re: [Wlug] HELP!! printer woes

by Tom Guilderson

If I remember correctly - RedHat switched from Aladdin ghostscript to GNU ghostscript from 7.1 to 7.2. When I gave 7.2 a test drive I could not get it to print postscript to an HP printer. This was several months ago. I ended up uninstalling all the 7.2 printing utilities and installing the utilities from 6.2 - and everything worked. It's a solution that saved me a lot of time. Rip out ghostscript, lpd, the print filters, and set up utilities and put the old RPMS's that worked you earlier for a quick solution. Then when you have some time - you can try to get the latest version working after you have gotten your real work done. That is why I have become wary of RedHat lately - in their desire to ship the latest and greatest and keep up with Suse and Mandrake etal in the distro wars - sometimes things are not ready for production environments - if it were a .0 release - maybe.... but not in the third iteration! Good Luck! > > > My printer setup has gone south as a result of the upgrade from 7.1 to > > > 7.2 at the install fest. I need help because I have real work to do > > > and no time... > > > > Generic canned answer - have you applied all updates? There have been > > quite a few updates that went by for printing in particular. > >

Feb. 23, 2002

Re: [Wlug] HELP!! printer woes

by Frank Sweetser

On Sat, Feb 23, 2002 at 01:31:07PM -0500, Tom Guilderson wrote: > That is why I have become wary of RedHat lately - in their desire to ship the > latest and greatest and keep up with Suse and Mandrake etal in the distro > wars - sometimes things are not ready for production environments - if it > were a .0 release - maybe.... but not in the third iteration! Speaking in defence of RedHat - I can't say anything specific as I'm a beta tester and under NDA, but RedHat has refused to update packages to newer versions if they decide those newer versions are sufficiently stable yet. And as for printing - it's kind of a bad example. They revamped the printing system because it included suport for a *whole* lot more printers. And while yeah, there were some issues with it (mostly related to specific printer drivers, IIRC) they are updates out there for them. -- Frank Sweetser fs at wpi.edu, fs at suave.net | $ x 16 Full-time WPI Network Tech, Part time Linux/Perl guy | In school, every period ends with a bell. Every sentence ends with a period. Every crime ends with a sentence. -- Stephen Wright

Feb. 23, 2002

Re: [Wlug] HELP!! printer woes

by Bill Mills-Curran

Frank, Good suggestion. I'll try that and (after I take my son shopping for a friend's birthday present) get back to the list. Pollyana that I am, I was not expect bugs from something as basic as printing. Sigh. No time. Thanks, Bill On Sat, 23 Feb 2002, Frank Sweetser wrote: > Date: Sat, 23 Feb 2002 11:37:01 -0500 > From: Frank Sweetser <fs(a)WPI.EDU> > Reply-To: wlug(a)mail.wlug.org > To: wlug(a)mail.wlug.org > Subject: Re: [Wlug] HELP!! printer woes > > On Sat, Feb 23, 2002 at 11:47:08AM -0500, Bill Mills-Curran wrote: > > HELP HELP HELP > > > > My printer setup has gone south as a result of the upgrade from 7.1 to > > 7.2 at the install fest. I need help because I have real work to do > > and no time... > > Generic canned answer - have you applied all updates? There have been > quite a few updates that went by for printing in particular. > > -- > Frank Sweetser fs at wpi.edu, fs at suave.net | $ x 16 > Full-time WPI Network Tech, Part time Linux/Perl guy | > In school, every period ends with a bell. Every sentence ends with a > period. Every crime ends with a sentence. -- Stephen Wright > _______________________________________________ > Wlug mailing list > Wlug(a)mail.wlug.org > http://mail.wlug.org/mailman/listinfo/wlug >

Feb. 23, 2002