Service Request Ticket - # 49046

Service Request Information

CONTACT Name Lab Attendant, APSC   View open tasks   View tasks from last 30 days   Schedule Change Contact Date Dec 01, 2012 09:26 AM
Department University Computing Solutions Phone 88069
Location Email printerpaper@wou.edu Request for more information Send 'Keeping in touch' email Send 'I'm thinking of you' email

SR INFO Type WOU #
Priority Equipment Type
Status Flagged
Description

Computer Edit WOU # 20090119[Edit Inv] (opens in a new window) Bldg/Room OFF PDR
Service Tag Description Dell OptiPlex 960 SFF,Core2Duo, 3.0GHz,6M, 1333FSB
Serial No. HFM2CK1 Location PDR

CPU Intel Core 2 Duo E8400(3.0GHz, 6M, VT,1333MHz FSB)


OS Linux Software MS Office Pro Plus 2007 from P0071641

Wired NIC 00:24:E8:30:6B:DF


TECHS Submitted by Juliette Sprague Contact jsprague11@mail.wou.edu 88925
Primary Technician Contact bvonbrockdorff@wou.edu 88925

Tracking

Entered by Date Memo
Blake von Brockdorff
Email

Public

Entered by Date Memo
Blake von Brockdorff Dec 03, 2012 12:27 PM
Status changed from (1) Pending to (5) Completed
Add Attachment
Blake von Brockdorff Dec 03, 2012 12:27 PM
Task reassigned to Blake von Brockdorff.
Add Attachment
Blake von Brockdorff Dec 03, 2012 12:27 PM
Unable to locate the problem. Reimaged and
everything works fine
Add Attachment
Juliette Sprague Dec 01, 2012 09:26 AM
When an attempt is made to add the printers from
the \\krusty menu the following two dialog boxes
appear, the first reads "Windows cannot connect to
the printer. The specified port is unknown." The
second is a script error message that reads, "
Script:
\\Mash.wou.edu\SysVol\mash.wou.edu\Polocies\(3DAF8574-759F-4FDC-BF76-BDCBDF21CCF4)\Users\Logon\defaultprinters.vbs
Line: 7
Char: 1
Error: There is no printer called
"\\krusty\lab\apsc101".
Code 80020009
Source: WSHNetwork.SetDefaultPrinter"

Restarting the computer and three separate users
logged in made no difference the same errors
occurred all three times. All network cables
appear to be plugged in properly, the printer is
running without trouble and only one computer
appears to be displaying this issue. Moving to a
new work station seemed to work just fine.  
Add Attachment