Foros ZackYFileS

Foros ZackYFileS (http://foros.zackyfiles.com/index.php)
-   CABLE-MODEMs - Hard / Soft (http://foros.zackyfiles.com/forumdisplay.php?f=423)
-   -   SB5100 (http://foros.zackyfiles.com/showthread.php?t=566244)

jjeje02 15/03/2008 14:39

SB5100
 
hola amigos, tengo un sb5100 que funcionaba de maravilla, pero desde ayer, lo conecto y se quedan todas las luces fijas, osea que conecta, pero de no deja navegar, alguien me podria ayudar, estube leyendo pero la verdad no encuentro de que puede ser.:D

jjeje02 19/03/2008 07:59

como puedo saber si es por culpa de los certificados, es que hay con macs que se me quedaan las luces encendidas osea coje linea, pero no me deja navegar.
por algun lado lei que puede ser del dchp de la tarjeta de red, alguien me podia indicar como cambiarlo, o si puede ser de esto. saludos.

jjeje02 20/03/2008 23:48

despues de mil pruebas, cambios de macs validas de 1.0 de ponerle los valores de fabrica, sigue igual, se conecta, se quedan las cuatro luces verdes fijas, me da ip al ordenada pero no navega, alguna ayuda porfa :D

rafa333 21/03/2008 21:10

usa bpi version 0
y mete una m*c docsis 1.0
debe navegar.
http://forum.zackyfiles.com/showthre...539809&page=10

jjeje02 23/03/2008 21:40

gracias rafa333. ya esta el bpi a 0 y la mac de las wenas, pero no me deja navegar
si que coje linea, porque las luces se le quedan todas fijas pero no me deja navegar, ya le hice un reset y tampoco, probe con dos ordenadores distintos y tampoco.

luisan1977 24/03/2008 01:37

pues a mi me ocurre lo mismo, me navegaba bien y de repente lo mismo que a jjeje02 las 4 luces fijas y no navega y no tengo ni idea de lo que puede ser, yo lo tengo con el firm stealth edition 12.2 y sigm x2 y cambio la mac poniendo 192.168.100.1:1337 como puedo cambiar eso del bpi bueno me respondo a mi mismo lo he cambiado a traves de telnet pero no se si lo he hecho bien pues estaba todo el rato saliendo como parrafos con letras, el caso que he hecho eso del bpi pero sigue igual, bueno miento no sigue igual ahora la luz de online ni se enciende se queda parpadeando en la tercera la de send

gracias

jjeje02 29/03/2008 14:37

sigo sin poder navegar a continuacion os pongo el estatus y los logs

status
Acquire Downstream Channel Done
Obtain Upstream Parameters Done
Upstream Ranging Done
Establish IP Connectivity using DHCP Done
Establish Time Of Day In Progress
Transfer Operational Parameters through TFTP Done
Register Connection Done
Cable Modem Status Operational
Initialize Baseline Privacy Skipped



logs
1970-01-03 19:12:41 7-Information 0x848E0009 M569.1 Standby mode disabled
1970-01-03 19:11:30 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-03 18:36:10 7-Information 0x848E0008 M569.0 Standby mode enabled
1970-01-03 18:36:06 7-Information 0x848E0009 M569.1 Standby mode disabled
1970-01-03 18:36:04 7-Information 0x848E0008 M569.0 Standby mode enabled
1970-01-03 18:35:56 7-Information 0x848E0009 M569.1 Standby mode disabled
1970-01-03 18:31:30 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-02 19:26:27 7-Information 0x848E0008 M569.0 Standby mode enabled
1970-01-02 19:26:27 7-Information 0x848E0004 I500.0 Registration Completed
1970-01-02 19:26:26 3-Critical 0x045A8148 TLV-11 - Illegal Set operation failed
1970-01-02 19:26:26 7-Information 0x848E0002 D509.0 Retrieved TFTP Config ;kfoA,.iyewrkld SUCCESS
1970-01-02 19:26:26 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-02 19:26:25 7-Information 0x848E0003 D511.0 Retrieved DHCP .......... SUCCESS
1970-01-02 19:26:24 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-02 19:26:19 7-Information 0x848E0005 T500.0 Acquired Upstream .......... SUCCESS
1970-01-02 19:26:18 7-Information 0x848E0006 T501.0 Acquired Downstream (735000000 Hz)........ SUCCESS
1970-01-02 19:26:14 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
1970-01-02 19:26:13 7-Information 0x848E0006 T501.0 Acquired Downstream (735000000 Hz)........ SUCCESS
1970-01-02 19:26:09 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:26:08 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:26:07 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:26:04 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:26:03 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:26:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:57 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:55 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:54 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:51 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:44 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:43 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:42 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:42 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:41 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:41 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:40 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:40 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:38 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:23 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:22 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:22 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:21 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:20 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:17 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:16 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:15 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:15 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:06 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:06 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:05 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:04 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:04 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:03 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:25:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:25:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:58 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:58 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:50 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:45 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:44 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:42 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:42 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:38 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:37 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:35 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:29 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:21 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:20 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:18 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:18 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:16 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:15 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:14 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:24:10 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:24:09 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:23:58 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:23:57 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:23:55 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-02 19:23:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-02 19:23:53 3-Critical 0x0501BDC8 SYNC Timing Synchronization



failure - Failed to acquire FEC framing

Software Version: SB5100-2.3.1.6-SCM01-FATSH
Hardware Version: 3
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4
ayuda por favor


La franja horaria es GMT +2. Ahora son las 05:54.

Powered por vBulletin™ Version 3.8.10
Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.
Traducido por vBsoporte - vBulletin en español
ZackYFileS - Foros de Debate