5G CPE router and Jetdirect printer/legacy devices

Hi guys

Has anybody here had issues conntecting a CPE router (supplied by Three) with legacy ethernet devices?

The reason I ask is that I am having difficulties in getting the router to recognise an old HP 4200n printer (using a jetdirect EIO card - I believe the card is a 600N based on the colour of the housing)

The green LED light up solid at both ends but the router configuration page does not show the printer as a connected device (or disconnected for that matter)

I'm confident that the printer settings in the EIO menu are correct as I can get the printer to connect to (and pick up an IP) an old TL-MR3420 router (this is what the CPE router is replacing)

Any ideas?

TIA

When you say not recognised, do you mean the JetDirect card is not being DHCP assigned an IP from the new router?

If so, for testing, in the JetDirect config you could static assign an IP in the same subnet, that doesn’t clash with any DHCP assignments.

That's right the router is not assigning an IP

I'll try a static IP and let you know

Thanks for the suggestion

Got a spare switch? As a an experiment, stick that between the printer and the CPE

Thanks for the input - I did think of that one as a last ditch attempt, I'm glad someone else has had the same idea! I'm going to try that too

Thanks for the suggestion. Static IP in the JetDirect menu worked absolutely fine, but for some weird reason it just wouldn't pick up an IP on DHCP with either a Three CPE router or a TalkTalk HG633 router (but it worked fine on DHCP with a TP Link TL3420)

It's deffo not a printer/jet direct card issue as swapped cards and printers in all sorts of permutations and couldn't get the darned thing to work on DHCP

Anyway, all is good now and the printers are happy on the network

Long, long time ago in a galaxy far away…but I do recall having similar weird DHCP issues with JetDirect cards in printers.

Whilst static assigned IP address may be seen as a bit of a hack by the purists, it works, which is the main thing.

Nice work.

Yep it works, so it's all good.

I was half expecting to find something online about this weird issue, but didn't find anything, and the youtube videos simply chose the DHCP option with no mention of issues. Oh well! At least documenting this here on the forum may help somebody else in another twenty years time...