Error 405 accessing Bizhub web interface
I have a client who is having trouble accessing the web interface on two different Konica Minolta Bizhub printers. The symptoms aren't identical but may be related.
On his Bizhub Pro 920, he is able to access it from IE8 on XP without problems. He's tried Windows 10 (IE, I presume) but gets a 405 error.
He is unable to get to the web interface on a Color Bizhub C7000 at all, even with the XP computer.
In both cases, he is able to ping, scan, and print using the IP address of the printer.
I'm trying to get better details from him but was hoping for some feedback as to whether there's something different about these printers as far as browser requirements for the web interface.
The computers and printers are connected to the same unmanaged switch. The KM tech came out to look at them but wasn't successful at sorting it out.
Suggestions would be appreciated!
On his Bizhub Pro 920, he is able to access it from IE8 on XP without problems. He's tried Windows 10 (IE, I presume) but gets a 405 error.
He is unable to get to the web interface on a Color Bizhub C7000 at all, even with the XP computer.
In both cases, he is able to ping, scan, and print using the IP address of the printer.
I'm trying to get better details from him but was hoping for some feedback as to whether there's something different about these printers as far as browser requirements for the web interface.
The computers and printers are connected to the same unmanaged switch. The KM tech came out to look at them but wasn't successful at sorting it out.
Suggestions would be appreciated!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
As is all too often the case, once I pressed the client further, the information changed significantly. The C7000 has a Fiery controller and it's web interface is the one causing him trouble. The other one doesn't have an external controller.
I walked him through ensuring that the Firey's web interface is enabled (even tried it with it disabled) and have had no success.
I did check the TLS settings, enabled what was disabled, and had no better success.
I suggested that he look into upgrading the firmware on all of the devices.
I appreciate the help but have reached the limit of what I can do with him remotely.
I walked him through ensuring that the Firey's web interface is enabled (even tried it with it disabled) and have had no success.
I did check the TLS settings, enabled what was disabled, and had no better success.
I suggested that he look into upgrading the firmware on all of the devices.
I appreciate the help but have reached the limit of what I can do with him remotely.
ASKER
Suggestions were excellent.
I find it fascinating that those useful little details are revealed to the troubleshooter only once he's on the clock and the meter is running. Before that point it's 'Let's Play "I've Got A Secret" ' (if you're old enough to remember the show).
ASKER
Yes... I'm old enough!
I find that communication with clients is the trickiest part of troubleshooting. It takes a skill that is very different from the technical skills needed to do the actual troubleshooting. It's something I emphasize to teens/young adults that are trying to get into the field.
I find that communication with clients is the trickiest part of troubleshooting. It takes a skill that is very different from the technical skills needed to do the actual troubleshooting. It's something I emphasize to teens/young adults that are trying to get into the field.
ASKER