SB5100 no conecta

[joelenriquepace]

Aqui os adjunto el log dle SB5100, que no se me conecta y no se por que echadme un cable.

2008-05-29 00:09:26 3-Critical 0x045A8148 TLV-11 - Illegal Set operation failed
2008-05-29 00:09:23 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-29 00:09:16 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-29 00:09:11 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:09:08 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:09:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:09:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:09:02 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:09:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:09:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:08:59 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:08:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:08:57 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:08:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:08:55 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:08:54 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:08:53 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:08:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:08:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:08:52 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:08:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:08:50 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:08:49 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:08:49 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:08:47 3-Critical 0x045A8148 TLV-11 - Illegal Set operation failed
2008-05-29 00:07:40 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-29 00:07:32 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-29 00:07:27 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-29 00:07:27 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-29 00:07:04 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:07:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:07:01 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:07:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:07:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:07:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:06:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:06:58 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:06:58 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:06:57 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:06:57 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:06:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:06:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:06:55 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:06:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:06:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:06:42 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:06:42 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:06:40 3-Critical 0x045A8148 TLV-11 - Illegal Set operation failed
2008-05-29 00:05:33 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-29 00:05:26 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-29 00:05:23 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-29 00:05:23 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-29 00:04:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:04:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:04:51 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:04:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:04:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:04:46 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:04:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:04:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:04:43 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:04:43 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:04:43 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:04:40 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:04:39 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:04:38 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:04:38 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:04:37 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:04:36 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:04:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:04:35 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:04:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:04:32 3-Critical 0x045A8148 TLV-11 - Illegal Set operation failed
2008-05-29 00:03:23 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-29 00:03:16 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-29 00:03:11 3-Critical 0x04E339AC Init RANGING Critical Ranging Request Retries exhausted
2008-05-29 00:03:11 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-29 00:02:41 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:02:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:02:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:02:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:02:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:02:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:02:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:02:29 3-Critical 0x045A8148 TLV-11 - Illegal Set operation failed
2008-05-29 00:01:17 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-29 00:01:08 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-05-29 00:00:59 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:00:58 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:00:57 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:00:57 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:00:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:00:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:00:55 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:00:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:00:55 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:00:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:00:54 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-29 00:00:54 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-05-29 00:00:54 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

[supersoco]

a mi me pasa esactamente lo mismo en zona eurodocsis con sigmax2 v14 y no se ya que hacerle estoy harto de meter mac y nada

[Carnoso]

UP!!

[reporter]

probar con otro firmw que hay varios y a su vez tambien de mac que las hay muy buenas

[serpor]

Estais probando con macs de docsis1.0 ?

[joelenriquepace]

Ya lo solucione es que ahbia activado el modo factorya del modem tonces no me iba, sabeis para que es ese modo. Y otra cosa yo antes con el SB4200 lo conectaba al PC por Cable Ethernet y me daba la Ip en el PC, pero tambien tenia une quipo virtual en el PC con VIRTUAL PC 2007, y tambien me la dba e decir el pc y el equipo virtual tenian la misma ip. Lo que ocurre ahora es que el SB5100 no me asigna la direccion ip al eqiupo virtual. Y quiero saber por que el SB4200 si lo hace y este otro no.

[supersoco]

pues yo sigo igual no me conecta ni para atras ni para delante le e puesto en factory mode le he activado y desactivado bpis e puesto cientos de mac y me sale el mensaje que hay arriba en los log por la señal no puede ser por que conecto mi sb 4200e y va de dulce asi que cual sera el problema ayuda please

[serpor]

pues yo sigo igual no me conecta ni para atras ni para delante le e puesto en factory mode le he activado y desactivado bpis e puesto cientos de m@c y me sale el mensaje que hay arriba en los log por la señal no puede ser por que conecto mi sb 4200e y va de dulce asi que cual sera el problema ayuda please
El 4200e es eurodocsis el que no te funciona tambien es eurodocsis?
O estas en zona docsis?
salu2