Problem with SB5101 - Printable Version

Problem with SB5101 - Printable Version

+- Haxorware Forums (http://www.haxorware.com/forums)
+-- Forum: General (http://www.haxorware.com/forums/forumdisplay.php?fid=6)
+--- Forum: Modems (http://www.haxorware.com/forums/forumdisplay.php?fid=7)
+--- Thread: Problem with SB5101 (/showthread.php?tid=1454)

Pages: 1 2 3 4

Problem with SB5101 - ijumanji - 01-03-2012

NEW UPDATE AS OF 4/3/2012

Okay so I have finally been able to access the haxorware configuration page.
I am connected via the usb connection. I have not purchased any extra things at the moment.

I was finally able to get a telnet log so here it is.
I don't know if I did it right, but please let me know.

Here is my log.
It just keeps doing this until I end it.
What does it mean?
Also, the sending light is the one where it's stuck at blinking when I turn it on now.

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2012.04.03 17:30:14 =~=~=~=~=~=~=~=~=~=~=~=
Haxorware integrated telnet daemon

Username: root
Password: *****
Welcome.

CM>
CM> run
CM>
CM> run_app

Instance: BFC System (0x807e57d4)

Running the system...

Beginning Cable Modem operation...

0x0000d9b2 [Scan Downstream Thread] BcmVendorCmDownstreamScanThread::ThreadMain: (Scan Downstream Thread) Scanning for a Downstream Channel...

mot_scanList: Setting override freq @ 0
Go back to 1st favorite
Attempting Downstream FEC lock @ freq= 90000000 Hz, QAM64

CM> Attempting Downstream FEC lock @ freq= 98000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 106000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 114000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 122000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 130000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 138000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 146000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 154000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 162000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 170000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 178000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 186000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 194000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 202000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 210000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 218000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 226000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 234000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 242000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 250000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 258000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 266000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 274000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 282000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 290000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 298000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 306000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 314000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 322000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 330000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 338000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 346000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 354000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 362000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 370000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 378000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 386000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 394000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 402000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 410000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 418000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 426000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 434000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 442000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 450000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 458000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 466000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 474000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 482000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 490000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 498000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 506000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 514000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 522000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 530000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 538000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 546000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 554000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 562000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 570000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 578000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 586000000 Hz, QAM64
Go back to 1st favorite
Attempting Downstream FEC lock @ freq= 594000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 602000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 610000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 618000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 626000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 634000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 642000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 650000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 658000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 666000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 674000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 682000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 690000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 698000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 706000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 714000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 722000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 730000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 738000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 746000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 754000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 762000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 770000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 778000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 786000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 794000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 802000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 810000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 818000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 826000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 834000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 842000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 850000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 858000000 Hz, QAM64
Attempting Downstream FEC lock @ freq= 90000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 98000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 106000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 114000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 122000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 130000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 138000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 146000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 154000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 162000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 170000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 178000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 186000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 194000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 202000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 210000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 218000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 226000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 234000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 242000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 250000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 258000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 266000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 274000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 282000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 290000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 298000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 306000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 314000000 Hz, QAM256
Go back to 1st favorite
Attempting Downstream FEC lock @ freq= 322000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 330000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 338000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 346000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 354000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 362000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 370000000 Hz, QAM256
Attempting Downstream FEC lock @ freq= 378000000 Hz, QAM256

RE: Problem with SB5101 - ABMJR - 01-03-2012

connect and ethernet cable to the router directly and bypass the modem, and see what the gateway IP addy is...and thats the IP of the router..

log in and do username and password

RE: Problem with SB5101 - ijumanji - 01-03-2012

The IP I have is 169.x.x.x
I have tried using that IP and still nothing. I even tried setting up a static ip and still nothing.
I connected just with ethernet cable and no coax cable and I am stuck at the receive portion.
I know I should post a telnet log, but can someone show me to do that?

RE: Problem with SB5101 - drewmerc - 01-03-2012

Before you start, download and install putty:
http://the.earth.li/~sgtatham/putty/late.../putty.exe

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 (XX).

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.

RE: Problem with SB5101 - ABMJR - 01-03-2012

the 169 IP is coming from what device connected? Modem? Router?

BTW

169 is used when Windows is configured to use DHCP and it cannot find a DHCP server to get an IP Address from.

Thus no DHCP. If this is from the modem, then your HFC MAC is bad and you wont get an IP from the DHCP server..

This is what happens when idiots tinker with stuff they have no idea of.....

If you want my opinion as to learn what to do..Take a basic networking course. Also, your modem maybe banned and it also maybe in new security..

RE: Problem with SB5101 - southernyankey1970 - 01-03-2012

Reflash it and try again with a new nic mac

RE: Problem with SB5101 - ijumanji - 02-03-2012

Like I said, I didn't do any of this, I paid someone to set it up for me and my brother fucked everything up, I appreciate the help from all of you though. Drewmerc, I will try your methods ASAP and post back!

Also, is this the adapter you are referring to? http://www.amazon.com/MAX232-RS232-Converter-Adapter-Board/dp/B00471S6MC

RE: Problem with SB5101 - drewmerc - 02-03-2012

http://www.ebay.com/sch/i.html?_trkparms=65%253A12%257C66%253A2%257C39%253A1%257C72%253A6068&rt=nc&_nkw=usb+ttl&_sticky=1&_trksid=p3286.c0.m14&_sop=15&_sc=1

RE: Problem with SB5101 - ijumanji - 02-03-2012

Thank you for the link, at the moment I am trying method 2 since that seems to require buying nothing, but if all else fails I will buy anything that is necessary. I appreciate your patience through all of this.

I can't connect with method 2 via Putty. it says "connection closed by remote host"

I assume I will have to buy that adapter, that is completely fine. I am interested in learning about this

http://www.ebay.com/itm/4pcs-cable-USB2-0-to-RS232-TTL-Converter-Module-PL2303-/250905004108?pt=LH_DefaultDomain_0&hash=item3a6b1a884c

Is that the correct one? Also, I am on windows 7 so would this be a problem?

RE: Problem with SB5101 - drewmerc - 02-03-2012

seems you picked the most expensive one?
just get the cheapest as they are all using the same PL2303 chip and yes it's fine with windows 7
http://www.ebay.com/itm/USB-2-0-UART-TTL-6PIN-Connector-Module-Serial-Converter-CP2102-New-/350499583299?pt=LH_DefaultDomain_0&hash=item519b673543