Bizhub 350 in a 2003 Win Domain

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • DocuSystems
    Service/IT/Integrator

    50+ Posts
    • Jan 2007
    • 54

    #1

    Bizhub 350 in a 2003 Win Domain

    This one has me scratching my head!

    Can't print or open internal webpage on the client's network. MFP has a static IP. I can ping, login to ftp, and scan to SMB. As soon as a print is sent, the machine displays the usual ! in the bottom right of the display, but never goes to the printing screen. At this point, scans (either for faxing or SMB scanning) stop working as well. I think the NIC is locking up. I've done the hub/packet capture thing, and noticed that if I remove the customers network cable and boot the MFP, all works as it should. Printing, scanning, etc. If I then momentarily connect the customers network to the hub, wait a couple of minutes, and then disconnect their network and try a test print, it fails the same way as if it were still connected. IP in use is free on their network, so no conflict there. Web Page responds with a 500 Internal Server Error. Even tried DHCP enabled with no joy. Also tried running to another network jack connected to a working workstation in a different room, same failure.
    Gonna look at the packets and try to learn how to decipher what I see, but wondered if anyone has seen these odd symptoms before. The clients IT guy says he can't find anything, but then he didn't find the bad cable either... still no luck after replacing the cable, btw. Same symptoms. I'm pretty sure the problem is with their equipment, but it's the "I've got HP printers connected to the same switch with no problems" catch 22!!
  • Mr Spock
    Vulcan Inventor of Death

    1,000+ Posts
    • Aug 2006
    • 2064

    #2
    Have the network check the settings on the main server/switches. He may have not added the mac address to the firewall/router/switch so even though it is on the network(login to scan and ftp via user name) it may be disabled for other protocols such as print an http. It may be a uni-directional port settings not bi-directional (it can send to server but can not have info sent to the machine).

    I have seen the above cause strange issues. Also the machine may have had the ipfiltering turned on or windows printing turned off.
    And Star Trek was just a tv show...yeah right!

    Comment

    Working...