On 2006.04.27 23:29, Wayne Stallwood wrote:
On Thu, 2006-04-27 at 21:09 +0000, Barry Samuels wrote:
Yes I managed to work that out but I still cannot ping the printer so I've assumed I must be doing something wrong or there is
something obvious I haven't though of doing.
Install traceroute if you don't have it already.
traceroute 'ipaddress of printer' and post it here along with output of route on machine B
I think at least one of those will narrow it down.
At the back of my mind I can't help thinking that because we are not masquerading on machine A we need to tell the printer about how to get back to the network on the first card.
On your printers IP config in the jetdirect menu there is an option to set the default gateway, this in your case should be the address of the network card the printer is plugged into on machine A
That was part of the problem. The gateway on the printer wasn't set and setting that means that when I now ping the printer from Computer B I get a reply.
BUT...
If I try to print from computer B the job isn't sent and the status is 'waiting for (printer IP) to come up'.
Traceroute gets as far as computer A but then I get lines of asterisks. Do I need any sort of routing on computer A?
Incidentally what do I have to do to make the route I've added on computer B become permanent rather than add it every time the computer is booted?
I really don't have a need for more network ports at the moment and I'd rather make use of the ports I have than spend another £25.00.
I suppose I'll get there in the end but it becomes pretty frustrating at times.
Barry Samuels http://www.beenthere-donethat.org.uk The Unofficial Guide to Great Britain