DHCP and printing IP to a fiery in Panther

[knowmad]

hello all,

more interesting printing issues to report this time closely related to DHCP under Panther.

It seems that if i am using DHCP on a machine running panther (2 G4s and 8 G5s) than i must use AppleTalk to print to a canon Fiery (z-40E attached to an 1100). If i use IP Printing, whether it be standard LPR/LPD or using the advanced pane, i get errors and no prints. As soon as I gave the machine a static IP printing worked fine using IP. I had two canon techs in the cleint office with me and they blamed it on apple saying apple had written a bad DHCP stack and that there was nothign they could do. They printed just fine from IP from a pc using DHCP, and just fine from a mac using static, but no luck when that same mac was using DHCP.

Also oddly enough the G5s (related office but not the same one, so these issues are not overlapping) won't accept DHCP from a router when the address being served starts with 192.168.24.X instead of 192.168.1.X I spent a great deal of time talking to apple about this one and the most they would tell me is that they do not support troubleshooting DHCP when it is served by a router or wintel box. If I wanted to install an OSX Server then they will gladly help me. They ran through sevral re-installs and tweaking of options on the client macs though.
Useless.

anyone got any ideas?

knowmad

[yellow]

What errors are you getting?

I cannot understand why the printer would give a rat's @$$. it's job is to sit there and listen for print requests on 515, not be picky about what address it's coming from.
What id you set it's static IP to the exact same IP it got dynamically. Does it still print properly?

[knowmad]

ok, once again i think i am saying everything when in fact i am mostly thinking it and only saying the last part.... or typing it as it were.

I personally believe the problem is on the mac side not the printer side. something about how the mac sends the info to the Fiery.... or maybe how it appends its return info... not really certain. the worst part is that I do not get an error. it simply won't print. I get a message "retrying in X seconds" where X is a multiple of ten.

If I set the G5/G4 to have a static IP, I get no issues, if i set it to DHCP, I get no print.

does that make it clearer? I can post the cups logs but they say almost nothing.

knowmad

[yellow]

Quote: Originally posted by yellow What id you set it's static IP to the exact same IP it got dynamically. Does it still print properly?

I realized that I didn't make sense here.

What I want to know is, if you take the IP address that you get dynamically (DHCP) and insert it as a static IP address, can you still get the machine to print. Personally I suspect that there's some sort of firewall/address range issue here. I suspect your DHCP range and your static range are in opposite ends of the subnet's addresses, or even in different subnets. If the fiery will only accept print requests from those int he static range, then there is your problem. If it prints with a static IP that you took from the DHCP range. Well, I'm stumped. That's weird.

Is the Fiery in the same subnet as the Mac?

Have you taken a look at the Fiery's WebTools™ to see what it thinks about address ranges?

[knowmad]

the fiery is in the same subnet as the mac. 192.168.1.51 is the fiery and 192.168.1.112 id the DHCP assigned addy for the mac both in the tried and true 255.255.255.0 subnet. I did not think to use the exact same address that was dhcp assigned for the static test. instead i gave it an addy i knew was unassigned and empty (192...50) for the static test. same subnet though. if you hang around your comp for a few minutes I will test the .112 number as a static. report to follow.
knowmad

[knowmad]

Ok, so i just ran the suggested test and guess what........ it don't work.
which is to say that something you figured out is correct but i am still confused. When I set the static number to be 192.168.1.112 i was unable to print, but when I set the static number to be 192.168.1.50 I could print. Explain to me please how, if they atr in the same subnet, they are having this problem..... and shouldn't ip printing be able to cross subnets?

oh, and for the record, this is the cups error log from the failed printing attempt as .112:

I [12/Jan/2004:17:05:54 -0500] Printer 'print_on_192.168.1.51' started by ''.
I [12/Jan/2004:17:05:54 -0500] Started filter /usr/libexec/cups/filter/cgpdftops (PID 454) for job 133.
I [12/Jan/2004:17:05:54 -0500] Started filter /usr/libexec/cups/filter/pstops (PID 455) for job 133.
I [12/Jan/2004:17:05:54 -0500] Started backend /usr/libexec/cups/backend/lpd (PID 456) for job 133.
E [12/Jan/2004:17:05:55 -0500] Started backend /usr/libexec/cups/backend/lpd (PID 456) for job 133.
I [12/Jan/2004:17:05:55 -0500] Started backend /usr/libexec/cups/backend/lpd (PID 456) for job 133.

I am just gonna sit here and wait till my confusion goes away..... or I get bored

[yellow]

Quote: Originally posted by knowmad Explain to me please how, if they atr in the same subnet, they are having this problem..... and shouldn't ip printing be able to cross subnets?

So it's not just that it has to be set to a static IP, it appears that it has to be an IP within a certain range. This would be something on the Fiery's side, or possibly with the router itself, that doesn't pass traffic to the Fiery when within a certain IP range. This is just a guess, but seems closer to the problem to me.
Where to go from here? Check the Fiery out to see if it does have a limit on the ranges it accepts request from. See if there something on the router that doesn't pass traffic from the DHCP range to the static range. Perhaps setting one Mac to DHCP, make sure it can get out on the internet, and set another to a static IP, making sure it can get out on the internet, and then see if they can talk to each other.

[knowmad]

I will run tests tomorrow.
will keep you posted.
thanks for the help, this is a route of troubleshooting I wouldnot have taken on my own.
knowmad