Lost Printing with Dept ID management

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • seantydingco
    Technician
    • Sep 2008
    • 20

    #1

    Lost Printing with Dept ID management

    Device: iRC3380
    Status: Lost printing with dept ID management on
    Network status: Peer to Peer, no server, not outside IT consulting.
    Last know change: No change to network and no software installed since copier installion.

    History:
    This copier was working normally for over a year. Customer moved the copier from the front office to the rear office, network still the same no changes at all.

    About a week ago after they moved the copier they all lost printing. Dept ID Management was on and was working up until this time, as per customer description.

    I went to their office and tried everything I know, the only way that their copier will print normally is if I turn off Dept ID Management.

    They have Norton 360 on two of the PC's I was working on and I turned them off and all windows based firewalls.

    Still no printing and unable to get "Device Status" from the copier on either PC.

    I suspect some software is blocking but I have no idea what, and what get me is that all four pc's went down at the same time in a peer to peer enviornment.

    Anyone have any ideas?
  • teckat
    Field Supervisor

    Site Contributor
    10,000+ Posts
    • Jan 2010
    • 16092

    #2
    Originally posted by seantydingco
    Device: iRC3380
    Status: Lost printing with dept ID management on
    Network status: Peer to Peer, no server, not outside IT consulting.
    Last know change: No change to network and no software installed since copier installion.

    History:
    This copier was working normally for over a year. Customer moved the copier from the front office to the rear office, network still the same no changes at all.

    About a week ago after they moved the copier they all lost printing. Dept ID Management was on and was working up until this time, as per customer description.

    I went to their office and tried everything I know, the only way that their copier will print normally is if I turn off Dept ID Management.

    They have Norton 360 on two of the PC's I was working on and I turned them off and all windows based firewalls.

    Still no printing and unable to get "Device Status" from the copier on either PC.

    I suspect some software is blocking but I have no idea what, and what get me is that all four pc's went down at the same time in a peer to peer enviornment.

    Anyone have any ideas?

    see if u can get Device Status from a Laptop connected to the 3380
    **Knowledge is time consuming, exhausting and costly for a trained Tech.**

    Comment

    • SCREWTAPE
      East Coast Imaging

      Site Contributor
      2,500+ Posts
      • Jan 2009
      • 3396

      #3
      Originally posted by seantydingco
      Device: iRC3380
      Status: Lost printing with dept ID management on
      Network status: Peer to Peer, no server, not outside IT consulting.
      Last know change: No change to network and no software installed since copier installion.

      History:
      This copier was working normally for over a year. Customer moved the copier from the front office to the rear office, network still the same no changes at all.

      About a week ago after they moved the copier they all lost printing. Dept ID Management was on and was working up until this time, as per customer description.

      I went to their office and tried everything I know, the only way that their copier will print normally is if I turn off Dept ID Management.

      They have Norton 360 on two of the PC's I was working on and I turned them off and all windows based firewalls.

      Still no printing and unable to get "Device Status" from the copier on either PC.

      I suspect some software is blocking but I have no idea what, and what get me is that all four pc's went down at the same time in a peer to peer enviornment.

      Anyone have any ideas?
      Connect a laptop with a crossover directly and confirm if indeed its the machine. Seems like a network issue.

      Comment

      • seantydingco
        Technician
        • Sep 2008
        • 20

        #4
        Yeah thats what we decided to do tomorrow to make sure its not on the machine side. We shall see.

        Comment

        Working...