mx-4071 1 ip address inop.

[bigdaddyooo]

192.168.1.192 will not work. I can type in any other address and it will function fine. I have tried pinging .192 in cmd box and received no response. The same thing with the cable disconnected from mfp. I change ip to .193 or .191 and it's working fine. I did a nic reset and it made no difference. Im at a loss.

[ihatefinishers13]

192.168.1.192 will not work. I can type in any other address and it will function fine. I have tried pinging .192 in cmd box and received no response. The same thing with the cable disconnected from mfp. I change ip to .193 or .191 and it's working fine. I did a nic reset and it made no difference. Im at a loss.

Probably something on their end is restricting it. Just change it and move on, have their IT handle it

[bigdaddyooo]

I would if i could. Im the set up guy for my company and EVERY color machine gets that address. B/W gets .201. for set up purposes. i want to know what could cause this. How can a machine reject an ip addy?

[Doug.P]

The router probably has that port blocked or reserved.

[bigdaddyooo]

No Doug. I have connected many other machines to that address and 1 just a few seconds ago. It's just this particular machine

[ihatefinishers13]

No Doug. I have connected many other machines to that address and 1 just a few seconds ago. It's just this particular machine

Well that would be good to know on the first post next time :P I haven't had a particular machine do that, just that it's usually the network. Did you happen to push backup data (clone) files on to the machine ahead of time? I've seen weird things happen with that. Since you already reset the NIC, the MFP/SCN PWB is pretty much the only thing you can replace, other than just factory resetting the machine.

[yurisan]

What your people do makes no sense to me. Networks change, routers get changed, and you are usually best served by leaving the machine in DHCP mode. That way, it never drops off the network, can always find the folders it needs to or the email server, NAS server, FTP server, Cloud Service, whatever.... Then you install the driver using the MAC address, which never changes, and always functions no matter what the machine's IP address is (as you are in Auto IP/DHCP mode).

[ihatefinishers13]

What your people do makes no sense to me. Networks change, routers get changed, and you are usually best served by leaving the machine in DHCP mode. That way, it never drops off the network, can always find the folders it needs to or the email server, NAS server, FTP server, Cloud Service, whatever.... Then you install the driver using the MAC address, which never changes, and always functions no matter what the machine's IP address is (as you are in Auto IP/DHCP mode).

While that sounds good for one single machine, in 4-5 years when they upgrade, you have to setup new drivers immediately because nobody could print. While you're going to end up changing the drivers at some point, when you first swap the machine, the old drivers will still work(most of the time). We use a static IP, get it reserved on their end, and swapping machines gets infinitely easier. You're just asking for trouble if you use Mac Address or Hostname.

In bigdaddy's case, I'm hoping he's referring to this in the office, because there are far too many different IP schemes that a customer's IT would use for that setup to work. Our office shop area has a VLAN set up so that the network jacks we plug in to will give you a range of 3-30, so that the IP is easier to get, and we have test print drivers setup. Machines default to DHCP already, so there is little that has to be changed.

[bigdaddyooo]

UPDATE... I was told the address was functional on other machine however I didn't see it. I should've checked it myself. Found out it is the router not letting us use that ip address any longer. We had the head of networking retire and I cant find the PW and UN for the router. ARGHHH. No lists of PW's or UN's. Anyways just wanted to end this saying "check it for yourself". LESSON LEARNED

[leo34staffs]

What your people do makes no sense to me. Networks change, routers get changed, and you are usually best served by leaving the machine in DHCP mode. That way, it never drops off the network, can always find the folders it needs to or the email server, NAS server, FTP server, Cloud Service, whatever.... Then you install the driver using the MAC address, which never changes, and always functions no matter what the machine's IP address is (as you are in Auto IP/DHCP mode).

I thought you reserved the IP address via MAC address on DCHP, not install the driver using the MAC address (i normally use the hostname) When setting up Sharps it lists IPv4 address and IPv6 address in the auto install driver.

[yurisan]

I thought you reserved the IP address via MAC address on DCHP, not install the driver using the MAC address (i normally use the hostname) When setting up Sharps it lists IPv4 address and IPv6 address in the auto install driver.

Not exactly. The newer Sharp driver installation program doesn't even offer the choice to create a TCP/IP port. Under "Standard Installation", ofter it finds the MFP, it gives you 2 choices - create a port using the MAC address, or create one using the machines host name (something like "SC3B2444"). Yes, technically the interface is still TCP/IP, but the driver is finding the device via its MAC address or host name. Apple's influence is profound. That is why AirPrint works so flawlessly. Our techs have gotten away from using TCP/IP ports. They are subject to often becoming invalid (e.g. when routers on different subnets come on board), or when an IP conflict occurs. If we are swapping out an older machine (we just swapped out 6 machines all at once, recently), we are going to install the correct, latest driver - that's what we get paid for, not to bring in new machines, give them the same IP address (like someone mentioned), and leave, having the customer continue to use the old drivers (yes, the old driver will probably work, as the PCL6 language has not really changed much over the years), but that sounds crazy to me.....

[ihatefinishers13]

Not exactly. The newer Sharp driver installation program doesn't even offer the choice to create a TCP/IP port. Under "Standard Installation", ofter it finds the MFP, it gives you 2 choices - create a port using the MAC address, or create one using the machines host name (something like "SC3B2444"). Yes, technically the interface is still TCP/IP, but the driver is finding the device via its MAC address or host name. Apple's influence is profound. That is why AirPrint works so flawlessly. Our techs have gotten away from using TCP/IP ports. They are subject to often becoming invalid (e.g. when routers on different subnets come on board), or when an IP conflict occurs. If we are swapping out an older machine (we just swapped out 6 machines all at once, recently), we are going to install the correct, latest driver - that's what we get paid for, not to bring in new machines, give them the same IP address (like someone mentioned), and leave, having the customer continue to use the old drivers (yes, the old driver will probably work, as the PCL6 language has not really changed much over the years), but that sounds crazy to me.....

We update drivers any chance we get, but most of the time we need the customers IT to do it because of credentials, or worse, they refuse to install new drivers because they don't have a fast way to deploy drivers. 50 machine install recently, BP70C55's replacing 5071's (which replaced the MXM565, and MXM503 before that), across 20+ locations, with over 200+ PC's to install. Their IT said they're not changing drivers, we have to make it work with what's there, which could have been any of the previous 3 machine's drivers (5071,565,503). It's a massive account and because of another thing I won't mention, we couldn't really push back unfortunately. It works, they don't complain, so I'm not worried about it... But I'm sure they would love to have the latest driver so the print would be as dark as it should be.

With that install as well, IP's on all machines in their locations stayed the same, so that installing them was simple, and their IT didn't have to lift a finger. The second that they were plugged in, IP was set, and anyone could start printing immediately. Especially if we go to bring a different machine in because it's down and needs a loaner, once again, instant printing. I don't love the idea of not switching drivers, but it sure makes their IT happy.

[Hart]

That where you're supposed to use JobAccouting/Kayleigh or PaperCut

For a very small company I use the hostname (they'll probably change ISP and so router during the lease), for the bigger ones I use the IP.

[boutn]

Not exactly. The newer Sharp driver installation program doesn't even offer the choice to create a TCP/IP port. Under "Standard Installation", ofter it finds the MFP, it gives you 2 choices - create a port using the MAC address, or create one using the machines host name (something like "SC3B2444"). Yes, technically the interface is still TCP/IP, but the driver is finding the device via its MAC address or host name. Apple's influence is profound. That is why AirPrint works so flawlessly. Our techs have gotten away from using TCP/IP ports. They are subject to often becoming invalid (e.g. when routers on different subnets come on board), or when an IP conflict occurs. If we are swapping out an older machine (we just swapped out 6 machines all at once, recently), we are going to install the correct, latest driver - that's what we get paid for, not to bring in new machines, give them the same IP address (like someone mentioned), and leave, having the customer continue to use the old drivers (yes, the old driver will probably work, as the PCL6 language has not really changed much over the years), but that sounds crazy to me.....

You mean IPv6 instead of mac-address i think...

[yurisan]

You mean IPv6 instead of mac-address i think...

Yes, you are correct. The driver program is offering you a chance to create a simplied 6 set IPV6 address which will be seen on your IPV4 network. Virtually no chance of a conflict. I mostly work in the MAC world, where once the device joins the network, there really isn't a formal driver installation necessary - it's just becomes immediately available.