 You don't need to be an 'investor' to invest in Singletrack: 6 days left: 95% of target - Find out more
New printer/MFD delivered and installed today at the office. In same place, on same network cable and socket, on same small hard wired office network as before. TP Link wifi acess and 2x netgear ports into a building wide broadband supplied by our landlord. Fixed IP.
I can 'see' it on the network, I can access the machine control panel by typing in the IP address, I can login to the printer and see all the IP/Subnet/etc. I can add it as a printer through windows.
It will not print - document just sits in the printer queue.
The machine is displaying a 'check IPv4, Subnet Mask and Gateway' message - but in the settings they are all there and correct.
The machine cannot connect to the internet. I cannot remember if the old machine could/did.
Suggestions?
When you say "fixed IP" can I assume that it's outside the DHCP scope?
An MFD isn't just a printer. Is it expecting to be managed in some way perhaps? Like, it's waiting for you to go up to it and go "I'll have my printout now, please"? Is it defaulting to looking for something like Uniflow which doesn't exist on your network and it needs to be configured to just print and stop being clever?
... back to basics,
Has the driver defaulted to Letter and it's sat there going "load paper" because it's full of A4?
So, much faffage later.
For some reason it did not like the port it was plugged into. I swapped it with one of the PC's and it just immediately 'found' the internet and sorted itself.
The PC is working just fine on internet.
hmmmmmm.
I Am Not A Network Engineer.
What speed does the PC connect at? 1Gbps or 100Mbps?
It's a printer, they are the cats of the IT world.
I suspect the lack of a heavy object hammer-shaped close to hand and a menacing attitude were lacking in the initial set-up.
What speed does the PC connect at? 1Gbps or 100Mbps?
It could be as simple as that. Half our sockets run a voip phone system, half the PC connections.
I wonder if the old printer did not need internet connection, just the LAN, wheras this new one needs it?
Still does not explain why the PC internet works just fine after the swap. Sorry Cougar, not sure of speed.
Where I was going with that is,
There was a tendency for a time to "nail up" ports, explicitly specifying speed and duplex. Gigabit Ethernet auto-negotiates both so this problem goes away; but in the Fast Ethernet world you could either set a port to Auto or to 100/full, and if one end was set one way and the other the other then the port flaps up and down and everything goes orange.
Things may have changed since I last dealt with them and as above IANANE, but I've never seen an MFD that isn't FE. So if it's out of the box and plugged into a nailed-up port, it's going to have a bad day. A modern PC maybe won't care.
(IANANE but I have spent some time in a room full of network engineers telling them "this is madness, stop it." 😁)