<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (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;
        font-family:"Calibri","sans-serif";}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Good morning,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>In addition to the excitement of the first day of class yesterday, the college also experienced computing challenges in the form of networking issues yesterday. Many folks in Engineering 1 reported “IP conflict” messages on their computers, which was brought about by an incorrectly configured personal network switch. The rogue switch was identified late in the day and networking was restored, but not after wasting time and effort by everyone affected. Unfortunately, this happens about every semester.<o:p></o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Central IT networking group discourages the use of personal network switches and routers for this and other reasons. Ideally, every wired network device should be plugged in to its own network port in the wall. A work order should be filled out if additional network ports are needed and not currently available. Please communicate this to students and researchers in your areas to make sure they also understand the importance of this policy. If a network switch/router is identified in your area, I will be contacting you to discuss alternative solutions.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you for your assistance in addressing this chronic issue. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> <o:p></o:p></p><p class=MsoNormal>Kiet Luong<o:p></o:p></p><p class=MsoNormal>Director of Engineering Computing<o:p></o:p></p><p class=MsoNormal>College Information Security Officer<o:p></o:p></p><p class=MsoNormal>Cullen College of Engineering<o:p></o:p></p><p class=MsoNormal>University of Houston<o:p></o:p></p><p class=MsoNormal>Email: KietL@uh.edu<o:p></o:p></p><p class=MsoNormal>Voice: 713.743.9974<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>