Can't access server's network drives after crash

Hi all,

	Our department's Windows 2003 Server crashed earlier today
and gave  
me a blue screen of not-quite-death yabbering on about a
device  
failure (possibly due to my plugging in a USB 2.0 transfer
drive into  
a USB 1.x port by mistake).  I rebooted the server and
everything  
seems to have recovered OK, except now workstations can't
access the  
two network drives (called I: and T that our
museum's catalog and  
linked images are served from.  Things here have ground to a
halt and  
there are a lot of annoyed stares being thrown in my
direction — so  
please help!

	I ran a "ping anubis.berkeley.edu"
(=128.32.209.52) command from the  
cmd window, and it returned four "Request timed
out" messages.  Thus,  
it would seem to be a network or IP address problem, but
everything  
was in working order until the server crashed.  Furthermore,
I can  
access the internet just fine from this server.

	I checked the Services to see if something was stopped that
should  
have been started, but all appears to be in order.

	I've restarted and re-logged on numerous times as well, to
no avail.

	I just joined this list and I don't know if I'll be able
to receive  
answers through the list, so please email me directly (or
cc: me) at  
mtblackberkeley.edu

Thanks!

Michael

	FYI, I'm a Mac user who was hired very recently to design
databases,  
but by default I've become our department's Windows system
 
administrator.  So it would be wise to assume I know next to
nothing  
about system administration or Windows servers....

------------------------------------------------------------
------------
The following was automatically added to this message by the
list server:

For information about Micronet, including subscribing to
or unsubscribing from its mailing list and finding out
about upcoming meetings, please visit the Micronet Web site:
<http://micronet.be
rkeley.edu/>.