<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="background-color: rgb(255, 255, 255); color: rgb(102, 0,
0); font-family: Verdana; font-size: 13px;" text="#660000"
bgcolor="#FFFFFF">
<div class="QCMcontainer"
style="font-family:Verdana;font-size:13px;">Hiya Joseph,<br>
<br>
Good to see some activity on this mailer ... I suppose this is the
first in a year or two ... it's nice to see that some of the good
ol' AS5400s are still in service out there.<br>
<br>
Let me hazard a guess as to what the problem reported below is ...
as we've seen this sort of complaint a bit recently. Windows 10
recently came out with an update called "Creators Update". It
seems to have some kind of bug / design problem with path MTU
discovery. See for example this thread:<br>
<br>
<a class="moz-txt-link-freetext" href="https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/wifi-issues-with-creators-update/4a20ba4f-33dc-4397-9823-e12dcb2607ba">https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/wifi-issues-with-creators-update/4a20ba4f-33dc-4397-9823-e12dcb2607ba</a><br>
<br>
The simple workarounds are:<br>
<br>
<ul>
<li>turn down the MTU on the client adapter, to maybe 1300 or
1400 B. (Simple for me to day, maybe not simple for the
client.)</li>
<ul>
<li>or disable Receive Segment Coalescing on the client (I
believe that this is the feature that causes the problem.)<br>
</li>
</ul>
<li>on the infrastructure side, if a router in the affected
network path is a Cisco IOS router, then turn on TCP MSS
Adjust (set it to 1250 or 1360 or so.)</li>
</ul>
<p><br>
</p>
I suppose maybe you could turn down the interface MTU for your
dialup users (this is negotiated in LCP, right), and that might be
a nice easy effective workaround too.<br>
<br>
Hope this helps,<br>
<br>
Aaron<br>
<br>
<hr size="2" width="100%"><br>
<span class="headerSpan" style="color:#000000; font-family:Arial;
font-size:12px; font-weight:normal">
<div class="moz-cite-prefix">On 6/5/2017 1:08 PM, <a class="moz-txt-link-abbreviated" href="mailto:mays@win.net">mays@win.net</a>
(Joseph Mays) wrote:<br>
</div>
</span>
<blockquote type="cite"
cite="mid:379CF36B05E144CDB27EE0D8F95869FF@Gantry"
style="border-left: 2px solid #009900 !important; border-right:
2px solid #009900 !important; padding: 0px 15px 0px 15px;
margin: 8px 2px;"><!--[if !IE]><DIV style="border-left: 2px solid #009900; border-right: 2px solid #009900; padding: 0px 15px; margin: 2px 0px;"><![endif]-->
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<div dir="ltr">
<div style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR:
#000000">
<div>I kind of never expected to have another question for
this list. I'm not even sure it's still operational. But I
guess we'll see.</div>
<div> </div>
<div>We have two AS5400's providing dialup services, one in
Kentucky, and one across the river in Indiana. The one in
Kentucky has no problems at all.<br>
<br>
Recently, a user in Indiana switched to Windows 10, and
found that her dialup connection there no longer worked.
She gets connected and logged in, but then gets 80-90%
packet loss. She still has her Windows 8 computer, and
that still works fine with her dialup connection. We went
over with a windows 10 unit, a windows 7 unit, and a linux
box, and tried dialup up with all three. The windows 7 and
linux boxed worked fine, the windows 10 unit had the same
problem she did.<br>
<br>
We then tried calling another user in Indiana whom we
thought had switched to Windows 10 a while ago. Turns out,
he told us, that his dialup connection never worked with
Windows 10, so he switched back to Windows 8.5.</div>
<div> </div>
<div>Our memory is that a year ago we were helping a partner
in Canada who had some dialup services with an AS5400, and
he found that Windows 10 users didn't work for him with
it, but he just figured it was something with Windows 10
and didn't worry about it.<br>
<br>
Like I said, Windows 10 works fine with the AS5400 in
Kentucky, so I tried isolating differences between those
boxes, to the point of making them identical with IOS,
modem setup strings, modem firmware, etc. No difference.
In fact, it made things worse. Many people were failing to
connect, including the woman with the initial problem. Now
the Indiana box is back to the way it was, and just that
woman who is trying to use Windows 10 has her problem of
getting connected then being unable to do anything.<br>
<br>
Here is the box in Indiana.<br>
<br>
</div>
<div><font face="Courier New">indyvoipMG#show ver</font></div>
<div><font face="Courier New">Cisco Internetwork Operating
System Software</font></div>
<div><font face="Courier New">IOS (tm) 5400 Software
(C5400-JS-M), Version 12.2(15)T17, RELEASE SOFTWARE
(fc1)</font></div>
<div><font face="Courier New">Technical Support: </font><a
href="http://www.cisco.com/techsupport"
moz-do-not-send="true"><font face="Courier New">http://www.cisco.com/techsupport</font></a></div>
<div><font face="Courier New">Copyright (c) 1986-2005 by
cisco Systems, Inc.</font></div>
<div><font face="Courier New">Compiled Sat 13-Aug-05 07:51
by kehsiao</font></div>
<div><font face="Courier New">Image text-base: 0x6000895C,
data-base: 0x61900000</font></div>
<div> </div>
<div><font face="Courier New">ROM: System Bootstrap, Version
12.0(20000106:234457) [tombnyg-rommon_1_6 106],
DEVELOPMENT SOFTWARE REV 1.6</font></div>
<div><font face="Courier New">BOOTLDR: 5400 Software
(C5400-BOOT-M), Version 12.2(7b), RELEASE SOFTWARE (fc1)</font></div>
<div> </div>
<div><font face="Courier New">indyvoipMG uptime is 2 days, 2
hours, 59 minutes</font></div>
<div><font face="Courier New">System returned to ROM by
reload at 13:05:26 EDT Sat Jun 3 2017</font></div>
<div><font face="Courier New">System restarted at 13:06:13
EDT Sat Jun 3 2017</font></div>
<div><font face="Courier New">System image file is
"flash:c5400-js-mz.122-16.T17.bin"</font></div>
<div> </div>
<div><font face="Courier New">cisco AS5400 (R7K) processor
(revision T) with 262144K/65536K bytes of memory.</font></div>
<div><font face="Courier New">Processor board ID JAB03510786</font></div>
<div><font face="Courier New">R7000 CPU at 250Mhz,
Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache</font></div>
<div><font face="Courier New">Last reset from IOS reload</font></div>
<div><font face="Courier New">Bridging software.</font></div>
<div><font face="Courier New">X.25 software, Version 3.0.0.</font></div>
<div><font face="Courier New">SuperLAT software (copyright
1990 by Meridian Technology Corp).</font></div>
<div><font face="Courier New">TN3270 Emulation software.</font></div>
<div><font face="Courier New">Primary Rate ISDN software,
Version 1.1.</font></div>
<div><font face="Courier New">Manufacture Cookie Info:</font></div>
<div><font face="Courier New">EEPROM Type 0x0001, EEPROM
Version 0x01, Board ID 0x31,</font></div>
<div><font face="Courier New">Board Hardware Version 3.21,
Item Number 800-5171-01,</font></div>
<div><font face="Courier New">Board Revision 017, Serial
Number JAB03510786,</font></div>
<div><font face="Courier New">PLD/ISP Version 2.2,
Manufacture Date 5-Jan-2000.</font></div>
<div><font face="Courier New">Processor 0xFF, MAC Address
0x03096F816</font></div>
<div><font face="Courier New">Backplane HW Revision 1.0,
Flash Type 5V</font></div>
<div><font face="Courier New">2 FastEthernet/IEEE 802.3
interface(s)</font></div>
<div><font face="Courier New">178 Serial network
interface(s)</font></div>
<div><font face="Courier New">108 terminal line(s)</font></div>
<div><font face="Courier New">36 Channelized T1/PRI port(s)</font></div>
<div><font face="Courier New">1 Channelized T3 port(s)</font></div>
<div><font face="Courier New">512K bytes of non-volatile
configuration memory.</font></div>
<div><font face="Courier New">32768K bytes of processor
board System flash (Read/Write)</font></div>
<div><font face="Courier New">8192K bytes of processor board
Boot flash (Read/Write)</font></div>
<div> </div>
<div><font face="Courier New">Configuration register is
0x2102</font></div>
<div><br>
Here is the box in Kentucky.<br>
<br>
</div>
<div><font face="Courier New">ArmoryPl-AS5400>show ver</font></div>
<div><font face="Courier New">Cisco Internetwork Operating
System Software</font></div>
<div><font face="Courier New">IOS (tm) 5400 Software
(C5400-JS-M), Version 12.3(3i), RELEASE SOFTWARE (fc1)</font></div>
<div><font face="Courier New">Copyright (c) 1986-2005 by
cisco Systems, Inc.</font></div>
<div><font face="Courier New">Compiled Fri 12-Aug-05 22:07
by ssearch</font></div>
<div><font face="Courier New">Image text-base: 0x6000895C,
data-base: 0x61900000</font></div>
<div> </div>
<div><font face="Courier New">ROM: System Bootstrap, Version
12.2(1r)1, RELEASE SOFTWARE (fc1)</font></div>
<div><font face="Courier New">BOOTLDR: 5400 Software
(C5400-BOOT-M), Version 12.1(1)XD1, EARLY DEPLOYMENT
RELEASE SOFTWARE (fc2)</font></div>
<div> </div>
<div><font face="Courier New">ArmoryPl-AS5400 uptime is 6
days, 6 hours, 58 minutes</font></div>
<div><font face="Courier New">System returned to ROM by
error - a Software forced crash, PC 0x60453E04 at
09:06:58 EDT Tue May 30 2017</font></div>
<div><font face="Courier New">System restarted at 09:07:56
EDT Tue May 30 2017</font></div>
<div><font face="Courier New">System image file is
"flash:c5400-js-mz.123-3i.bin"</font></div>
<div> </div>
<div><font face="Courier New">cisco AS5400 (R7K) processor
(revision T) with 524288K/131072K bytes of memory.</font></div>
<div><font face="Courier New">Processor board ID JAE09054U8M</font></div>
<div><font face="Courier New">R7000 CPU at 250Mhz,
Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache</font></div>
<div><font face="Courier New">Last reset from warm-reset</font></div>
<div><font face="Courier New">Bridging software.</font></div>
<div><font face="Courier New">X.25 software, Version 3.0.0.</font></div>
<div><font face="Courier New">SuperLAT software (copyright
1990 by Meridian Technology Corp).</font></div>
<div><font face="Courier New">TN3270 Emulation software.</font></div>
<div><font face="Courier New">Primary Rate ISDN software,
Version 1.1.</font></div>
<div><font face="Courier New">Manufacture Cookie Info:</font></div>
<div><font face="Courier New">EEPROM Type 0x0001, EEPROM
Version 0x01, Board ID 0x31,</font></div>
<div><font face="Courier New">Board Hardware Version 3.34,
Item Number 800-5171-02,</font></div>
<div><font face="Courier New">Board Revision C0, Serial
Number JAE09054U8M,</font></div>
<div><font face="Courier New">PLD/ISP Version 2.2,
Manufacture Date 26-Jan-2005.</font></div>
<div><font face="Courier New">Processor 0x14, MAC Address
0x012801C6694</font></div>
<div><font face="Courier New">Backplane HW Revision 1.0,
Flash Type 5V</font></div>
<div><font face="Courier New">2 FastEthernet/IEEE 802.3
interface(s)</font></div>
<div><font face="Courier New">428 Serial network
interface(s)</font></div>
<div><font face="Courier New">432 terminal line(s)</font></div>
<div><font face="Courier New">64 Channelized T1/PRI port(s)</font></div>
<div><font face="Courier New">2 Channelized T3 port(s)</font></div>
<div><font face="Courier New">512K bytes of non-volatile
configuration memory.</font></div>
<div><font face="Courier New">65536K bytes of processor
board System flash (Read/Write)</font></div>
<div><font face="Courier New">16384K bytes of processor
board Boot flash (Read/Write)</font></div>
<div> </div>
<div><font face="Courier New">Configuration register is
0x2102</font></div>
<div> </div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
cisco-nas mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-nas@puck.nether.net">cisco-nas@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-nas">https://puck.nether.net/mailman/listinfo/cisco-nas</a></pre>
<!--[if !IE]></DIV><![endif]--></blockquote>
<br>
</div>
</body>
</html>