X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C841A1.717347EE@onstor-exch02.onstor.net>; Tue, 18 Dec 2007 10:11:42 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C841A1.717347EE"
Content-class: urn:content-classes:message
Subject: Mightydog Windows file server (CIFS) Problem
Date: Tue, 18 Dec 2007 10:11:42 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E07201F3C@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Mightydog Windows file server (CIFS) Problem
Thread-Index: AchBoXE7OJk8RNeaTaaZmq2lRV+QpA==
From: "Brian Baker" <brian.baker@onstor.com>
To: "org-All Employees" <org-all@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C841A1.717347EE
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

There as a problem with windows file access on  Mightydog starting
around 1:00am this morning. QE was able to  identify the issue and they
are filing a defect(thx May!). CIFS access has been restored and windows
clients should be able to access their shares.


------_=_NextPart_001_01C841A1.717347EE
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>There as a problem with windows file access =
on&nbsp; Mightydog
starting around 1:00am this morning. QE was able to &nbsp;identify the =
issue and
they are filing a defect(thx May!). CIFS access has been restored and =
windows
clients should be able to access their shares.<o:p></o:p></p>

</div>

</body>

</html>

------_=_NextPart_001_01C841A1.717347EE--
