dpc2100 flash with haxorware11rev39-LITE, page not found shows

[ABMJR]

I know your ISP. Your a Sub re-seller of Rogers/Cogeco right? If I remember, your a D3 network with D2 ENABLED AND NO channel bonding until later this year..

[tester2]

I know your ISP. Your a Sub re-seller of Rogers/Cogeco right? If I remember, your a D3 network with D2 ENABLED AND NO channel bonding until later this year..

yes yes he is a re-seller of Rogers. so is there any way i can run my hexwre on one line with spliter.

thanks

[ABMJR]

Post a TELNET log of the h
Haxorware modem trying to come on-line

[tester2]

when i connect hexwre modem, 192.168.100.1, shows below. if this is not, then where i can go to use TELNET command to get Log.....thanks

Task Status
Acquire Downstream Channel In Progress
Obtain Upstream Parameters Waiting
Upstream Ranging Waiting
Establish IP Connectivity Waiting
Retrieve Time of Day Waiting
Negotiate security Waiting
Receive configuration Waiting
Register connection Waiting
Cable modem status Scanning

Event Log
Time Priority Code Description
1970-01-01 00:00:29 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:29 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:05 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:05 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:05:05 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:05:04 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:14 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:14 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:04 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:02 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:02 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:10:02 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:10:02 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:10:00 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

[ABMJR]

TELNET log. Not an "Event" Log

[tester2]

how to get this TELNET Log. which progran can allow me to get this TELNET Log.

thanks

[ABMJR]

Please read and search. It has been answered here 100's of times...

[tester2]

hi there, i will take few more days to read more threads, once i understand TELNET LOG then i post my Log.

thanks for giving your time to reply my thread, i will back soon.

thanks

[ABMJR]

From one of our Members
Mohitmosh

Method 1 is preferred in all cases, method 2 looks worse than it is lol.


Method 1) Using MAX232

Remove power from the modemConnect your MAX232 adapter to the modem header and the PC. This guide assumes you're using COM1.

Open Putty. Click the logging section of the settings panel. Select the following options:

Session logging: All session output
Click 'browse' and browse to your desktop folder.
Filename: putty.txt
'Always overwrite it'
Untick 'flush log file frequently'

Click back onto the 'session' section of the settings panel:

Connection type: Serial
Serial line: COM1
Speed: 115200
Close window on exit: Never

Click 'open', then plug the power into the modem.
You should see the boot process and connection attempt appear.

Wait for about 20s after the connection has reached the failure point, then close putty and it'll save the txt log as putty.txt on your desktop.


Method 2) Using ethernet or USB (USB requires that USB drivers are correctly installed)

Remove power from the modem.

Set manual NIC IP 192.168.100.10.

Open Putty. Click the 'session' section of the settings panel:

Connection type: Telnet
Host Name: 192.168.100.1
Port: 23
Close window on exit: Never

Power up the modem. Wait 15 seconds, then click 'open' in putty.
Enter username and password, press enter.

Ignore any crap coming up in the window, it may look like you can't type but you can. May help if you just don't look at the screen

Type this, pressing enter at the end of each line:

cd doc
up_dis

cd /
cd n/b
auto_console 1
write

Note: The lines above are correct for modems based on the BCM3349 (A250/A255/A256/SB5101/Webstar 2100). If you're using a BCM3348 modem (A200/SB5100) the line 'cd n/b' changes to 'cd n/c'.

This tells the modem to halt at the console. Close putty and reboot modem using power cable.

When you reboot it, it won't try to connect at first, so you have time to set putty to log all console output to txt before connecting.


Open Putty. Click the logging section of the settings panel. Select the following options:

Session logging: All session output
Click 'browse' and browse to your desktop folder.
Filename: putty.txt
'Always overwrite it'
Untick 'flush log file frequently'

Click back onto the 'session' section of the settings panel:

Connection type: Telnet
Host Name: 192.168.100.1
Port: 23
Close window on exit: Never


Click 'open', enter username and password and press enter. Type 'run' and press enter. The modem will try to connect.

Wait for about 20s after the connection has reached the failure point, then close putty and it'll save the txt log as putty.txt on your desktop.

Once you've finished you'll need to set auto_console back to 0 in telnet, or you'll have to type 'run' every time you reboot modem.

[tester2]

hi there, thanks for your helpfull post about telnet log.

i am still trying by using METHOD#2, i stuck on this commands
cd n/b -- this command it partly working.
auto_console 1 -- this command when i type i am getting error BAD COMMAND, totally not accept.
so once i passed this 2 command successfully then i will do the rest all COMMANDS to obtain successfull TELNET LOG.

in case if i did not success by METHOD#2 then i will go for METHOD#1, so i have to place an order to buy MAX232 ADAPTER, so this is going to be little longer time for me to get this TELNET LOG File, if i follow METHOD#1.

So still currently i am keep on testing METHOD#2, untill i get my luck.

thanks.