[cisco-nas] Windows 10 with AS5400

Mon Jun 5 17:43:01 EDT 2017

Just got a chuckle from this..  

We have a 5300 still fired up but it only gets a hit maybe once every three
months..  

Gonna turn it down some day..  just waiting for the word.  I think we sent
the guy a letter.

I cant help but wonder how a dialup user would even get updates for
Windows10 (chuckle)..

The dialup world..

Ken

Valley Telecom Group

From: cisco-nas [mailto:cisco-nas-bounces at puck.nether.net] On Behalf Of
Joseph Mays
Sent: Monday, June 05, 2017 1:09 PM
To: cisco-nas at puck.nether.net
Subject: [cisco-nas] Windows 10 with AS5400

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.

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.

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.

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.

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.

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.

Here is the box in Indiana.

indyvoipMG#show ver

Cisco Internetwork Operating System Software

IOS (tm) 5400 Software (C5400-JS-M), Version 12.2(15)T17, RELEASE SOFTWARE
(fc1)

Technical Support:  <http://www.cisco.com/techsupport>
http://www.cisco.com/techsupport

Compiled Sat 13-Aug-05 07:51 by kehsiao

Image text-base: 0x6000895C, data-base: 0x61900000

ROM: System Bootstrap, Version 12.0(20000106:234457) [tombnyg-rommon_1_6
106], DEVELOPMENT SOFTWARE REV 1.6

BOOTLDR: 5400 Software (C5400-BOOT-M), Version 12.2(7b), RELEASE SOFTWARE
(fc1)

indyvoipMG uptime is 2 days, 2 hours, 59 minutes

System returned to ROM by reload at 13:05:26 EDT Sat Jun 3 2017

System restarted at 13:06:13 EDT Sat Jun 3 2017

System image file is "flash:c5400-js-mz.122-16.T17.bin"

cisco AS5400 (R7K) processor (revision T) with 262144K/65536K bytes of
memory.

Processor board ID JAB03510786

R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache

Last reset from IOS reload

Bridging software.

X.25 software, Version 3.0.0.

TN3270 Emulation software.

Primary Rate ISDN software, Version 1.1.

Manufacture Cookie Info:

EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x31,

Board Hardware Version 3.21, Item Number 800-5171-01,

Board Revision 017, Serial Number JAB03510786,

PLD/ISP Version 2.2,  Manufacture Date 5-Jan-2000.

Processor 0xFF, MAC Address 0x03096F816

Backplane HW Revision 1.0, Flash Type 5V

2 FastEthernet/IEEE 802.3 interface(s)

178 Serial network interface(s)

108 terminal line(s)

36 Channelized T1/PRI port(s)

1 Channelized T3 port(s)

512K bytes of non-volatile configuration memory.

32768K bytes of processor board System flash (Read/Write)

8192K bytes of processor board Boot flash (Read/Write)

Configuration register is 0x2102

Here is the box in Kentucky.

ArmoryPl-AS5400>show ver

Cisco Internetwork Operating System Software

IOS (tm) 5400 Software (C5400-JS-M), Version 12.3(3i), RELEASE SOFTWARE
(fc1)

Compiled Fri 12-Aug-05 22:07 by ssearch

Image text-base: 0x6000895C, data-base: 0x61900000

ROM: System Bootstrap, Version 12.2(1r)1, RELEASE SOFTWARE (fc1)

BOOTLDR: 5400 Software (C5400-BOOT-M), Version 12.1(1)XD1, EARLY DEPLOYMENT
RELEASE SOFTWARE (fc2)

ArmoryPl-AS5400 uptime is 6 days, 6 hours, 58 minutes

System returned to ROM by error - a Software forced crash, PC 0x60453E04 at
09:06:58 EDT Tue May 30 2017

System restarted at 09:07:56 EDT Tue May 30 2017

System image file is "flash:c5400-js-mz.123-3i.bin"

cisco AS5400 (R7K) processor (revision T) with 524288K/131072K bytes of
memory.

Processor board ID JAE09054U8M

R7000 CPU at 250Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache

Last reset from warm-reset

Bridging software.

X.25 software, Version 3.0.0.

TN3270 Emulation software.

Primary Rate ISDN software, Version 1.1.

Manufacture Cookie Info:

EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x31,

Board Hardware Version 3.34, Item Number 800-5171-02,

Board Revision C0, Serial Number JAE09054U8M,

PLD/ISP Version 2.2,  Manufacture Date 26-Jan-2005.

Processor 0x14, MAC Address 0x012801C6694

Backplane HW Revision 1.0, Flash Type 5V

2 FastEthernet/IEEE 802.3 interface(s)

428 Serial network interface(s)

432 terminal line(s)

64 Channelized T1/PRI port(s)

2 Channelized T3 port(s)

512K bytes of non-volatile configuration memory.

65536K bytes of processor board System flash (Read/Write)

16384K bytes of processor board Boot flash (Read/Write)

Configuration register is 0x2102

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-nas/attachments/20170605/da10cff7/attachment-0001.html>