printer installation with DHCP constant on

[Mark Bbb]

Just ping the host name to get the current IP.

If I'm not mistaken the newer drivers also have a button that will open WIM can't remember where exactly the button is because I usually just ping it quick.

If network discovery is enabled on PC you can also find the device under network places and right click there for the option to open in browser or something

Sent from my SM-A305F using Tapatalk

OK:
explorer, network, mpc3004 (f.i.), 2x click on it = WIM
Thank you!

[slimslob]

Unless the IT dept reserves the mac address for that device anytime the printer is turned off and on or a power failure the printer will could get a different ipaddress and the customer would not be able to print.

Static IPADDRESS is the norm

That would only be the case when the the power is off long enough for temporary reservation created by the DHCP server expires. There is a problem with static addresses is that if the DHCP server does not know to reserve that address, it could easily assign that address to another device.

Most quality corporate IT personnel that I have worked with have had me set the machine up using DHCP. They would then set a permanent reservation. That avoided both potential problems though there would still be the problem of devices, often laptops, that connected with static addresses that the IT did not know about.

[slimslob]

I've installed 100s of devices with DHCP...but then you print to host name and not IP address and you make sure you use the correct DNS.

Advantage of this is the user simply has to restart the device if they run into a printer offline issue due to duplicate IP and it will grab a new IP. Also makes upgrade installs quick and easy if you use custom host names ( ie RicohMFP1) because you simply clone the host name for new device.

Makes an install double easy if print driver has a custom name (ie Reception Printer) then you simply install new driver in existing driver on PC and no need to mess around with other software like pastel

Sent from my SM-A305F using Tapatalk

I have had customers that like to change their ISP on a regular basis and are small enough that they rely on the DHCP in the cable modem. DHCP on the printer and host name on the computers kept me from having to go there every 4 or 5 months.

[BillyCarpenter]

I've installed 100s of devices with DHCP...but then you print to host name and not IP address and you make sure you use the correct DNS.

Advantage of this is the user simply has to restart the device if they run into a printer offline issue due to duplicate IP and it will grab a new IP. Also makes upgrade installs quick and easy if you use custom host names ( ie RicohMFP1) because you simply clone the host name for new device.

Makes an install double easy if print driver has a custom name (ie Reception Printer) then you simply install new driver in existing driver on PC and no need to mess around with other software like pastel

Sent from my SM-A305F using Tapatalk

That's pretty slick and I just tried your setup here at the shop and it worked great. And you're correct that it would be quick to do an upgrade and simply use the hostname instead of the IP address because no matter the IP address of the MFP, it's gonna be resolved to the hostname.

The only potential problem you may run into is if the dns record get twisted up and then they wouldn't be able to print. That's the only advantage that a static IP would have over your config.

[slimslob]

Dear 8T2, but still, how can customer enter the WIM, if ip address is changing without knowing it well?

Yes as long as you know the host name. Or you can just do a net explore using file explorer. Once you have connected the first time you can then add it to your browser's favorites/short cuts.

[BillyCarpenter]

That would only be the case when the the power is off long enough for temporary reservation created by the DHCP server expires. There is a problem with static addresses is that if the DHCP server does not know to reserve that address, it could easily assign that address to another device.

Most quality corporate IT personnel that I have worked with have had me set the machine up using DHCP. They would then set a permanent reservation. That avoided both potential problems though there would still be the problem of devices, often laptops, that connected with static addresses that the IT did not know about.

That's an interesting scenario, but why would a laptop user be connecting with a static IP address? Are we talking about wireless or a physical connection?

[slimslob]

DHCP is only useful when the IP is reserved by the customer. Using a DHCP obtained address is risky as a device that already has that address assigned statically could be switched off, then conflicts arise when it is switched on again. On any network install you want either a static IP address or a reserved DHCP.

DHCP can also cause problems with strangely behaving network hardware. I had a huge customer who had a rogue switch they were unable to track down that issued incorrect domain information on DHCP stopping the machines scanning to email. Setting the machine to a static IP and inputting the correct domain sorted this.

Some customers will not allow you to use a static IP but that's just a bridge you have to cross when you come to it I'm afraid.

I had a county water agency that switched from using the county's IT to using a local service, county often took 2 or 3 days to send someone out and the local took 1 or 2 hours. We put in a new Ricoh color MFP and the next day they couldn't print. When i got there I noticed an IP conflict message on the bottom of the screen. With a little network searching I discovered that somewhere in the building was a VPN that the county used to access water usage reports that was using the IP address I was initially given plus the next 2 for remote access.

[8T2]

That's an interesting scenario, but why would a laptop user be connecting with a static IP address? Are we talking about wireless or a physical connection?

I've ran into it where the wired and wireless DHCP addresses don't sync up properly and you end up with a duplicate IP even though both devices are on DHCP... arguing with IT over issues like that is the best when they refuse to admit the issue is on their side and expect you to prove it to them before they consider lifting a finger

Sent from my SM-A305F using Tapatalk

[slimslob]

That's an interesting scenario, but why would a laptop user be connecting with a static IP address? Are we talking about wireless or a physical connection?

More often than not it will be a hacker. They don't want their MAC showing up in the DHCP database.

[BillyCarpenter]

It's been interesting reading about the different ways to configure a copier to print.


-DHCP reservations

-Print to hostname

-Static IP address

I think all of those are pretty rock solid options but if you put a gun to my head and forced me to pick the most reliable? I'm going with static IP address.


Disclaimer: In slim's scenario where the customer kept changing ISP providers, that wouldn't be ideal.