<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:x = "urn:schemas-microsoft-com:office:excel" xmlns:p = "urn:schemas-microsoft-com:office:powerpoint" xmlns:a = "urn:schemas-microsoft-com:office:access" xmlns:dt = "uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s = "uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs = "urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b = "urn:schemas-microsoft-com:office:publisher" xmlns:ss = "urn:schemas-microsoft-com:office:spreadsheet" xmlns:c = "urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc = "urn:schemas-microsoft-com:office:odc" xmlns:oa = "urn:schemas-microsoft-com:office:activation" xmlns:html = "http://www.w3.org/TR/REC-html40" xmlns:q = "http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D = "DAV:" xmlns:mt = "http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 = "http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois = "http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir = "http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds = "http://www.w3.org/2000/09/xmldsig#" xmlns:dsp = "http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc = "http://schemas.microsoft.com/data/udc" xmlns:xsd = "http://www.w3.org/2001/XMLSchema" xmlns:sub = "http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec = "http://www.w3.org/2001/04/xmlenc#" xmlns:sp = "http://schemas.microsoft.com/sharepoint/" xmlns:sps = "http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs = "http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf = "http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p = "http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf = "http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss = "http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi = "http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi = "http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver = "http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m = "http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels = "http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp = "http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t = "http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m = "http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl = "http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl = "http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService" XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=utf-8">
<META content="MSHTML 6.00.2900.3492" name=GENERATOR>
<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;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
mso-believe-normal-left:yes;}
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;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US style="MARGIN: 3pt 3pt 0.75pt" vLink=purple link=blue>
<DIV> First of all thanks to everyone for your responses, this is a great group and I have found it to be a very valuable resource.</DIV>
<DIV> </DIV>
<DIV> Now....isn't the switch in an IP telephone a true switch and not a hub? So if the phone port that goes to the closet switch is set to auto and the closet switch port is set to auto it should negotiate and transmit data independently of the PC port which is hard coded to 100/Full to match the 1000's of NIC cards that we have out there that are already set that way?</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>
<DIV><FONT face=Arial color=#006600 size=2>Please consider the impact on our environment before printing this e-mail.</FONT> </DIV><BR><BR>>>> "Jason Aarons (US)" <jason.aarons@us.didata.com> 2/24/2009 2:39 PM >>><BR></DIV>
<DIV class=Section1>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Cisco’s recommendation with technical explanations<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><A href="http://www.cisco.com/en/US/tech/tk389/tk214/technologies_tech_note09186a0080094781.shtml">http://www.cisco.com/en/US/tech/tk389/tk214/technologies_tech_note09186a0080094781.shtml</A><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Fuermann, Jason<BR><B>Sent:</B> Tuesday, February 24, 2009 1:52 PM<BR><B>To:</B> 'STEVEN CASPER'; James Buchanan; cisco-voip@puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip] PC Port on Phone Fails During Large Data Transfer<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">WHOA, that’s some weird setup.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Everything should work fine on auto/auto. If not both sides of the link need to at least match, or you will get duplex mismatches which will cause a lot of problems<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>STEVEN CASPER<BR><B>Sent:</B> Tuesday, February 24, 2009 12:12 PM<BR><B>To:</B> James Buchanan; cisco-voip@puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip] PC Port on Phone Fails During Large Data Transfer<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">This is our standard at the moment<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">Switch ---------Phone Switch Port---------Phone PC Port------- PC NIC<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">Auto/Full Auto/Auto 100/Full 100/Full <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt">There is a long convoluted history behind these settings but we have not had any issues until recently.<o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"> <o:p></o:p></P></DIV>
<DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: #006600; FONT-FAMILY: 'Arial','sans-serif'">Please consider the impact on our environment before printing this e-mail.</SPAN> <o:p></o:p></P></DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><BR><BR>>>> "James Buchanan" <jbuchanan@ctiusa.com> 2/24/2009 12:07 PM >>><o:p></o:p></P></DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">When you hardcoded to 100/Full, did you hardcode on the switch end and inside the phone?<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"><o:p> </o:p></SPAN></P>
<DIV>
<DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> cisco-voip-bounces@puck.nether.net [mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>STEVEN CASPER<BR><B>Sent:</B> Tuesday, February 24, 2009 9:49 AM<BR><B>To:</B> 'cisco-voip@puck.nether.net'<BR><B>Subject:</B> [cisco-voip] PC Port on Phone Fails During Large Data Transfer<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> Has anyone run across the following scenario - <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> When large amounts of data are transferred between an IP Phone and an attached PC such as during a Microsoft Office update the update fails. When the failure occurs the phone shows the status of port 2 (PC Port) as no link. it was working fine prior to the update starting. This fails consistently when the phone PC port and the PC NIC is set for 100/full, always seems to work when both are set to Auto/Auto or when the phone is bypassed and the PC is plugged directly into the switch port.<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">Tried multiple phones 7941/61/11s. Current phone under test is running phone load is 41.8-3-3SR2S and we are connected to a 3750 running 12.2.25 SEE2. Going to do more testing but wondering if any one else may have run across this.<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">Thanks<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'">Steve<o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV>
<DIV>
<P class=MsoNormal style="MARGIN: 0in 0in 0pt"><SPAN style="FONT-SIZE: 10pt; COLOR: #006600; FONT-FAMILY: 'Arial','sans-serif'">Please consider the impact on our environment before printing this e-mail.</SPAN><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Tahoma','sans-serif'"> <o:p></o:p></SPAN></P></DIV><PRE>************************************<o:p></o:p></PRE><PRE>This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.<o:p></o:p></PRE><PRE>There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.<o:p></o:p></PRE><PRE>************************************<o:p></o:p></PRE>
<P><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: 'Arial','sans-serif'">No virus found in this incoming message.<BR>Checked by AVG - www.avg.com<BR>Version: 8.0.237 / Virus Database: 270.11.3/1966 - Release Date: 02/22/09 17:21:00</SPAN><o:p></o:p></P><PRE>************************************<o:p></o:p></PRE><PRE>This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.<o:p></o:p></PRE><PRE>There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.<o:p></o:p></PRE><PRE>************************************<o:p></o:p></PRE></DIV>
<P>
<HR SIZE=1>
<P></P>
<P><STRONG>Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. </STRONG></P><pre>************************************
This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.
There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.
************************************
</pre></BODY></HTML>