340WGB HP JetDirect Printer lose MAC address/connectivity

iedwards · ‎01-29-2003

I have a 340 Workgroup Bridge that has two PC clients and an HP Laserjet 4000N (built-in jetdirect) Printer.

The printer intermittently, about 2-3 ties per day, drops out of the client/MAP list on the 340WGB.

If I leave the browaser page open of the 340WGB display the MAP/SID_ONLY, which constantly refreshes itself, then the printer keeps it's connection.

I have added the printers MAC address into the client list on the 340WGB but still the connection drops. I have also replaced the hub with a switch and the cat 5 cable/flylead.

Any ideas.

derwin · ‎01-29-2003

Does the printer answer an arp ?

What firmware are you running on the AP and what AP are you running

What firmware are you running on the WGB ?

My intial thoughts are that due to inactivity of the printer it is droping out of the list of MAC address but as this happens then a device tries to communicate to it then via the arp process it should answer and be back in the wgb's table.

Maybe you can wait for it to no longer be in the WGBs table and then put a sniffer on the ethernet side and see if the WGB is forwarding the arp and then if the printer answers that arp.

Maybe it is a combination of it aging out of the arp tables and that the printer goes into some sort of sleep/power save mode and does not wake on lan ??? I would try the sniffer and work from there Also try the latest firmware for both the AP and WGB just incase.

iedwards · ‎01-30-2003

Thanks for the response.

There are two p.c.'s connected on the same lan as the WGB and they can still print fine, so I guess the printer is answering the arp.

The 350WGB is V8.65.2 which is connected to an 350 Ethernet Bridge running V11.10T1 .

I have turned of any sleep options and it prints from local p.c.'s. but not from the remote p.c.s (these are at the Eth Bridge site.

From your comments I come to the conclusion that it is the WGB that isn't either sending or receiving the arp request/response.

I will try and put a sniffer on but if you have any further thoughts please advise. Thanks.

derwin · ‎01-31-2003

I would update that firmware before breaking out the sniffer.