Hello,

My diagnosis/conclusion concerning my UBEE cable modem is:

Corruption of download signal over COAX is somehow locking the modem out, or it's done by ISP provider, mostly it is caused by signal corruption.
(Could also be a miss configuration by ISP because of upgraded protocol, old modem gets confused by newer protocol, see log below)

This tutorial might help those to diagnose problems and to see menus of UBEE cable modem, the exercise in itself is almost useless it does provide some information about mac addresses and firmware, but logs will be deleted/reset, however this exercise
does prove the cable modem is working correctly before it is hooked up to the COAX:

1. Disconnect cable modem from power.

2. Disconnect cable modem from coax/white cable (to splitter).

3. Connect cable modem to power.

4. Press reset button with a tiny screw driver.

5. Have browser open and navigate to 192.168.1.1

Use following links if 192.168.1.1 is not showing default menu:

Basic information is accessible without username/password:

http://192.168.1.1/BasicCmState.asp
http://192.168.1.1/BasicFirmware.asp
http://192.168.1.1/BasicStatus.asp

Advanced information is accessible with authentication:
user: admin
password: password

http://192.168.1.1/AdvMta.asp
http://192.168.1.1/AdvLine.asp
http://192.168.1.1/AdvDhcp.asp
http://192.168.1.1/AdvQos.asp
http://192.168.1.1/AdvProvisioning.asp
http://192.168.1.1/AdvEventLog.asp

The outputs will be htm pages, with red bars and information.

The event log was the most interesting after step 6:

6. Connect cable modem back to coax, I did it by disconnecting power first.

This is what the log showed:

Advanced
Event Log
This page displays the Event Log on the current system.
CM Event Log
Date/Time Event Level Event ID Description
Time Not Established Warning (5) D3.0 DHCP WARNING - Non-critical field invalid in response ;CM-MAC...
Time Not Established Critical (3) R2.0 No Ranging Response received - T3 time-out;CM-MAC=0c:60:76:49...
Time Not Established Critical (3) T1.0 SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Time Not Established Critical (3) T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC f...

MTA Event Log
Date/Time Event Level Event ID Description
Endpoint

I now believe that this response says it all:

"Non-critical field invalid in response"

Something strange is being downloaded.

Either it's a misconfiguration/miss communication from the ISP side, confusing this modem which is from 2009 or it is data corruption because of noisy signal.

Hopefully soon new splitter will arive which is supposed to replace old splitter to clear up analog tv signal.

It will be very interesting to see if this fixes the problem.

If not I may phone ISP with my findings to inform them that they might be causing some weird kind of misconfiguration on my modem, probably because of more advanced protocol from their side which may not be incompable with this older modem.

Date: 15/10/2018

Bye,
Skybuck.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)