Kitz Forum
Broadband Related => Router Monitoring Software => Topic started by: rolocollie on June 09, 2017, 03:03:27 AM
-
Sorry to be a pain but had to reinstall system and cannot correctly get modem stats H612 work it is on my desktop at the moment all the settings a yellow please select a local folder path only
message have also tried putting it in programe file but that did not work please help
-
Copy the main folder into the route of your C drive, or anot her suitable location.
You then need to select the correct folder, do the top one first by selecting the browse button next to, once you've selected the correct folder ir will ask if you want to update the others.
If using Windows 10 you may have to run it as administrator whilst you set things up, right click on the exe file and direct run as admin.
http://www.kitz.co.uk/routers/hg612stats_setup.htm
-
hi I have a windows 10 install via parallels and can not get My H612 Modem Log Stats to work the ping aspect is functioning ok also have managed to enable stats upload any suggestions most welcome
-
You may need to run the following three programs manually, in this order. Sometimes Windows or your antivirus will block them, and when running from the task this doesn't show up.
Hg612_run.exe
Hg612_stats.exe
Hg612_current_stats.exe
Names might vary slightly as I'm on my tablet and can't double check.
Watch out for security warnings, and make sure the programs can run ok
Other thing to check is that you've set the ip address and the type of modem, also the user name and password if it needs setting.
-
Hi thanks for your reply not being very computer savvy I think that ive done all what you suggested still no joy the anti virus did flag up one warning which I corrected in application control
-
What happens when you run HG612_STATS.EXE?
If that runs and your settings are all correct then the stats shoud update on the GUI, if not then double check all the settings, especially for the modem. Is the modem on the same subnet, ie the first three numbers should be the same as your computers ip.
I suggest you run through kitz guide that I linked to rechecking everything.
-
Hi I have checked the modem it is the same as the IPV4 address 192.168.1.1 perhaps if I was a teenager it would come easily but as a silver surfer (80) it is sometimes daunting but like to try if you have ant suggestions that might help
-
Was you using Parrallels before?
What modem are you using, and can you login into it from Windows?
It may be worth posting the log files from Event & Error logs file, I might be able to tell what's wrong from them.
-
No I was not on parallels before
Jun 12 04:47:33 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 04:49:40 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 04:50:43 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 04:51:15 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 04:51:31 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 04:51:39 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 04:51:47 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 04:52:01 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 04:55:53 daemon info syslog: sending OFFER to IP:192.168.1.118, MAC:6c:b5:6b:70:aa:36
Jun 12 04:55:53 daemon info syslog: sending ACK to IP:192.168.1.118, MAC:6c:b5:6b:70:aa:36
Jun 12 04:58:47 daemon info syslog: sending OFFER to IP:192.168.1.105, MAC:08:eb:74:9e:bc:fd
Jun 12 04:58:47 daemon info syslog: sending ACK to IP:192.168.1.105, MAC:08:eb:74:9e:bc:fd
Jun 12 05:00:27 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 05:04:40 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 05:05:03 daemon info syslog: sending OFFER to IP:192.168.1.108, MAC:8c:f5:a3:cb:3e:9a
Jun 12 05:05:03 daemon info syslog: sending ACK to IP:192.168.1.108, MAC:8c:f5:a3:cb:3e:9a
Jun 12 05:06:47 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 05:07:50 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 05:08:22 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 05:08:38 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 05:08:46 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 05:08:54 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 05:27:30 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 12 05:27:30 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 12 05:28:16 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 12 05:28:16 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 12 05:28:18 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 12 05:28:18 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 12 05:28:19 daemon info syslog: sending ACK to IP:192.168.1.102, MAC:00:23:df:95:bd:48
Jun 12 05:50:00 daemon info syslog: sending ACK to IP:192.168.1.100, MAC:f0:4f:7c:12:2a:4e
Jun 12 06:14:38 daemon info syslog: sending ACK to IP:192.168.1.107, MAC:44:6d:6c:73:f6:77
Jun 12 06:21:47 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 06:38:54 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 06:51:15 daemon info syslog: sending OFFER to IP:192.168.1.111, MAC:00:00:48:67:64:e5
Jun 12 06:51:15 daemon info syslog: sending ACK to IP:192.168.1.111, MAC:00:00:48:67:64:e5
Jun 12 07:00:07 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 12 07:00:07 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 12 07:00:35 daemon info syslog: sending OFFER to IP:192.168.1.115, MAC:00:24:36:b0:87:7a
Jun 12 07:00:36 daemon info syslog: sending ACK to IP:192.168.1.115, MAC:00:24:36:b0:87:7a
Jun 12 07:05:00 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 12 07:05:00 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 12 07:05:02 daemon info syslog: sending ACK to IP:192.168.1.102, MAC:00:23:df:95:bd:48
Jun 12 07:06:47 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 07:12:17 daemon info syslog: sending ACK to IP:192.168.1.121, MAC:b8:e9:37:41:56:c7
Jun 12 07:17:17 daemon info syslog: sending OFFER to IP:192.168.1.111, MAC:00:00:48:67:64:e5
Jun 12 07:17:18 daemon info syslog: sending ACK to IP:192.168.1.111, MAC:00:00:48:67:64:e5
Jun 12 07:23:54 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 07:29:16 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 07:40:32 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 07:46:09 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 07:46:25 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 07:48:58 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 07:50:22 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 07:51:04 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 07:51:25 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 07:51:36 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 07:51:41 daemon info syslog: sending OFFER to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 07:51:41 daemon info syslog: sending OFFER to IP:192.168.1.118, MAC:6c:b5:6b:70:aa:36
Jun 12 07:51:41 daemon info syslog: sending ACK to IP:192.168.1.118, MAC:6c:b5:6b:70:aa:36
Jun 12 07:51:41 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 07:51:42 daemon info syslog: sending OFFER to IP:192.168.1.105, MAC:08:eb:74:9e:bc:fd
Jun 12 07:51:42 daemon info syslog: sending ACK to IP:192.168.1.105, MAC:08:eb:74:9e:bc:fd
Jun 12 07:57:39 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 08:03:16 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 08:04:42 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 12 08:04:42 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 12 08:06:05 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 08:07:29 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 08:08:11 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 08:08:32 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 08:08:43 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 08:08:48 daemon info syslog: sending OFFER to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 08:08:48 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 09:06:33 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 12 09:06:33 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 12 09:07:17 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 12 09:07:17 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 12 09:07:18 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 12 09:07:18 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 12 09:07:18 daemon info syslog: sending ACK to IP:192.168.1.102, MAC:00:23:df:95:bd:48
Jun 12 09:14:43 daemon info syslog: sending ACK to IP:192.168.1.112, MAC:44:6d:6c:73:f9:db
Jun 12 10:29:00 daemon info syslog: sending OFFER to IP:192.168.1.108, MAC:8c:f5:a3:cb:3e:9a
Jun 12 10:29:00 daemon info syslog: sending ACK to IP:192.168.1.108, MAC:8c:f5:a3:cb:3e:9a
Jun 12 11:01:58 daemon info syslog: sending OFFER to IP:192.168.1.111, MAC:00:00:48:67:64:e5
Jun 12 11:01:58 daemon info syslog: sending ACK to IP:192.168.1.111, MAC:00:00:48:67:64:e5
Jun 12 11:30:21 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 12 11:30:21 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 12 11:51:49 daemon info syslog: sending OFFER to IP:192.168.1.108, MAC:8c:f5:a3:cb:3e:9a
Jun 12 11:51:49 daemon info syslog: sending ACK to IP:192.168.1.108, MAC:8c:f5:a3:cb:3e:9a
Jun 12 11:54:24 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 12 11:54:24 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 12 11:55:04 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 12 11:55:04 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 12 11:55:06 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 12 11:55:06 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 12 11:55:06 daemon info syslog: sending ACK to IP:192.168.1.102, MAC:00:23:df:95:bd:48
Jun 12 12:04:42 daemon info syslog: sending OFFER to IP:192.168.1.108, MAC:8c:f5:a3:cb:3e:9a
Jun 12 12:04:42 daemon info syslog: sending ACK to IP:192.168.1.108, MAC:8c:f5:a3:cb:3e:9a
Jun 12 12:38:26 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 12 12:38:26 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 12 13:24:28 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 12 13:24:28 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 12 13:25:13 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 12 13:25:13 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 12 13:25:16 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 12 13:25:16 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 12 13:25:18 daemon info syslog: sending ACK to IP:192.168.1.102, MAC:00:23:df:95:bd:48
Jun 12 14:35:54 daemon info syslog: sending ACK to IP:192.168.1.113, MAC:00:24:36:a1:2f:ed
Jun 12 14:36:09 daemon info syslog: sending ACK to IP:192.168.1.113, MAC:00:24:36:a1:2f:ed
Jun 12 14:36:10 daemon info syslog: sending ACK to IP:192.168.1.113, MAC:00:24:36:a1:2f:ed
Jun 12 14:36:11 daemon info syslog: sending ACK to IP:192.168.1.114, MAC:8c:c1:21:9d:62:fa
Jun 12 14:36:14 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 12 14:36:14 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 12 14:41:38 daemon info syslog: sending OFFER to IP:192.168.1.112, MAC:44:6d:6c:73:f9:db
Jun 12 14:41:41 daemon info syslog: sending OFFER to IP:192.168.1.112, MAC:44:6d:6c:73:f9:db
Jun 12 14:41:50 daemon info syslog: sending OFFER to IP:192.168.1.112, MAC:44:6d:6c:73:f9:db
Jun 12 14:41:50 daemon info syslog: sending ACK to IP:192.168.1.112, MAC:44:6d:6c:73:f9:db
Jun 12 15:28:44 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 12 15:28:44 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 12 15:29:28 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 12 15:29:28 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 12 15:29:30 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 12 15:29:30 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 12 15:29:31 daemon info syslog: sending ACK to IP:192.168.1.102, MAC:00:23:df:95:bd:48
Jun 12 15:58:46 daemon info syslog: sending ACK to IP:192.168.1.107, MAC:44:6d:6c:73:f6:77
Jun 12 16:16:41 daemon info syslog: sending OFFER to IP:192.168.1.111, MAC:00:00:48:67:64:e5
Jun 12 16:16:41 daemon info syslog: sending ACK to IP:192.168.1.111, MAC:00:00:48:67:64:e5
Jun 12 17:19:26 daemon info syslog: sending ACK to IP:192.168.1.113, MAC:00:24:36:a1:2f:ed
Jun 12 17:19:40 daemon info syslog: sending ACK to IP:192.168.1.113, MAC:00:24:36:a1:2f:ed
Jun 12 17:19:42 daemon info syslog: sending ACK to IP:192.168.1.113, MAC:00:24:36:a1:2f:ed
Jun 12 17:19:43 daemon info syslog: sending ACK to IP:192.168.1.114, MAC:8c:c1:21:9d:62:fa
Jun 12 17:21:14 daemon info syslog: sending ACK to IP:192.168.1.100, MAC:f0:4f:7c:12:2a:4e
Jun 12 17:36:10 daemon info syslog: sending ACK to IP:192.168.1.112, MAC:44:6d:6c:73:f9:db
Jun 12 18:13:40 daemon info syslog: sending ACK to IP:192.168.1.105, MAC:08:eb:74:9e:bc:fd
Jun 12 18:35:25 daemon info syslog: sending ACK to IP:192.168.1.118, MAC:6c:b5:6b:70:aa:36
Jun 12 19:12:17 daemon info syslog: sending ACK to IP:192.168.1.121, MAC:b8:e9:37:41:56:c7
Jun 12 19:43:07 daemon info syslog: sending ACK to IP:192.168.1.100, MAC:f0:4f:7c:12:2a:4e
Jun 12 19:51:42 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 12 20:08:48 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 12 20:24:18 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 12 20:24:18 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 12 22:36:03 daemon info syslog: sending ACK to IP:192.168.1.112, MAC:44:6d:6c:73:f9:db
Jun 12 23:35:57 daemon info syslog: sending ACK to IP:192.168.1.108, MAC:8c:f5:a3:cb:3e:9a
Jun 12 23:36:13 daemon info syslog: sending ACK to IP:192.168.1.112, MAC:44:6d:6c:73:f9:db
Jun 13 00:21:41 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
Jun 13 00:38:47 daemon info syslog: sending ACK to IP:192.168.1.109, MAC:94:9f:3e:89:59:06
Jun 13 01:11:36 daemon info syslog: sending OFFER to IP:192.168.1.105, MAC:08:eb:74:9e:bc:fd
Jun 13 01:11:36 daemon info syslog: sending ACK to IP:192.168.1.105, MAC:08:eb:74:9e:bc:fd
Jun 13 01:36:14 daemon info syslog: sending ACK to IP:192.168.1.112, MAC:44:6d:6c:73:f9:db
Jun 13 01:46:33 daemon info syslog: sending OFFER to IP:192.168.1.118, MAC:6c:b5:6b:70:aa:36
Jun 13 01:46:33 daemon info syslog: sending ACK to IP:192.168.1.118, MAC:6c:b5:6b:70:aa:36
Jun 13 02:32:36 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 13 02:32:36 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 13 02:33:23 daemon crit kernel: eth2 (switch port: 4) Link DOWN.
Jun 13 02:33:23 daemon info kernel: br0: bridge group port 3(eth2) entering disabled state
Jun 13 02:33:25 daemon crit kernel: eth2 (switch port: 4) Link UP 100 mbps full duplex
Jun 13 02:33:25 daemon info kernel: br0: bridge group port 3(eth2) entering forwarding state
Jun 13 02:33:26 daemon info syslog: sending ACK to IP:192.168.1.102, MAC:00:23:df:95:bd:48
Jun 13 02:36:40 daemon info syslog: sending ACK to IP:192.168.1.112, MAC:44:6d:6c:73:f9:db
Jun 13 02:36:42 daemon info syslog: sending ACK to IP:192.168.1.110, MAC:94:9f:3e:89:59:a6
-
Forgot to mention modem is billion 8800 nl
-
That log looks like something from the router.
If you look on the HG612 stats folders you'll find a folder with error logs in it.
From Windows can you log into the Billion?
-
Yes I can log into the 8800nl not sure if this is the log that you requested as there are several
-
Yes thats one of the logs.
Now I need to you to change a setting in the GUI program. Go to the settings tab, then select the additional settings tab from the lower tabs.
Near the bottom of that tab is group marked Error Logging, enable the extensive logging option and then save the settings. NOTE: Once we have it working properly you need to disable the option, otherwise the logs will grow in size rather rapidly.
Now manually run HG612_Stats and then attach the ONGOING_ERROR.LOG file.
I'm not overly familiar with those logs, that was BaldEagles department, but hopefully from that I can work out what's going on, or not as is the case.
-
As requested could only do a part of log as it exceeds the maximum length
14/06/2017 3:13:00.82 - ONGOING-ISRUNNING-031300-695.TXT - Start of [HG612_stats.exe] - **** Version 5.1.0.0 16/05/2015 ****
14/06/2017 3:13:01.47 - ONGOING-ISRUNNING-031300-695.TXT - Immediately after ini_parse() - About to determine the OS version. ERROR.LOG status = 0,
14/06/2017 3:13:01.55 - ONGOING-ISRUNNING-031300-695.TXT - *** Windows version = [6.2.9200] ***
14/06/2017 3:13:01.63 - ONGOING-ISRUNNING-031300-695.TXT - In [HG612_stats.exe] - After obtaining the OS version. ERROR.LOG status = 0,
14/06/2017 3:13:01.80 - ONGOING-ISRUNNING-031300-695.TXT - ERROR.LOG successfully opened. Status = 1,
14/06/2017 3:13:02.83 - ONGOING-ISRUNNING-031300-695.TXT - ONGOING-ISRUNNING-031300-695.TXT created. Status = 1,
14/06/2017 3:13:03.78 - ONGOING-ISRUNNING-031300-695.TXT - There are 1 instances of HG612_stats.exe running. Status = 1,
14/06/2017 3:13:03.86 - ONGOING-ISRUNNING-031300-695.TXT - Continuing as there are only 1 instances of HG612_stats.exe running **. Status = 1,
14/06/2017 3:13:24.99 - ONGOING-ISRUNNING-031300-695.TXT - sockfd = 528, "res->ai_addrlen" = 16 connect() ERROR CODE = 10060 - Exiting HG612_stats.exe. Status = 1,
14/06/2017 3:13:25.07 - ONGOING-ISRUNNING-031300-695.TXT - connect() ERROR!!! - Exiting HG612_stats.exe. Status = 1,
14/06/2017 3:13:25.14 - ONGOING-ISRUNNING-031300-695.TXT - Now in exit. Status = 1,
14/06/2017 3:13:25.22 - ONGOING-ISRUNNING-031300-695.TXT - *** WSACleanup has completed.
14/06/2017 3:13:25.32 - ONGOING-ISRUNNING-031300-695.TXT - *** About to free(txbuf).
14/06/2017 3:13:25.38 - ONGOING-ISRUNNING-031300-695.TXT - *** txbuf has been freed.
14/06/2017 3:13:25.44 - ONGOING-ISRUNNING-031300-695.TXT - *** About to free(rxbuf).
14/06/2017 3:13:25.50 - ONGOING-ISRUNNING-031300-695.TXT - *** rxbuf has been freed.
14/06/2017 3:13:25.57 - ONGOING-ISRUNNING-031300-695.TXT - *** Now checking for resyncs - There are 1 instances of HG612_stats.exe running.
14/06/2017 3:13:25.69 - ONGOING-ISRUNNING-031300-695.TXT - ONGOING-ISRUNNING-031300-695.TXT DELETED - Status = 1,
14/06/2017 3:13:25.78 - ONGOING-ISRUNNING-031300-695.TXT - *** Scheduled snapshot logging is switched ON.
14/06/2017 3:13:25.86 - ONGOING-ISRUNNING-031300-695.TXT - *** Scheduled snapshot logging is NOT due yet.
14/06/2017 3:13:25.92 - ONGOING-ISRUNNING-031300-695.TXT - *** Scheduled Daily graphing is NOT switched on.
14/06/2017 3:13:26.02 - ONGOING-ISRUNNING-031300-695.TXT - End of [HG612_stats.exe], Closing ERROR.LOG. Status = 1,
14/06/2017 3:13:26.11 - ONGOING-ISRUNNING-031300-695.TXT - ERROR.LOG successfully closed. Status = 0,
14/06/2017 3:13:26.19 - ONGOING-ISRUNNING-031300-695.TXT - Normal End of [HG612_stats.exe]
14/06/2017 3:13:26.39 - ONGOING-ISRUNNING-031300-695.TXT - Web_stats are enabled, Username = Rolocollie
14/06/2017 3:13:26.47 - ONGOING-ISRUNNING-031300-695.TXT - temp log "C:\HG612_Modem_Stats\Ongoing_Stats\temp_Rolocollie_live_modem_stats.log" opened O.K.
14/06/2017 3:13:26.53 - ONGOING-ISRUNNING-031300-695.TXT - Ongoing log looks INVALID, so it can NOT be uploaded.
14/06/2017 3:13:26.67 - ONGOING-ISRUNNING-031300-695.TXT - End of [HG612_stats.exe] AFTER WebStats stuff
-
I can see there is an error, but I've no idea what it means.
14/06/2017 3:13:24.99 - ONGOING-ISRUNNING-031300-695.TXT - sockfd = 528, "res->ai_addrlen" = 16 connect() ERROR CODE = 10060 - Exiting HG612_stats.exe. Status = 1,
Perhaps use 7zip or WinZip to compress all the log files and the attach the resultant zip file to a post and then I can look through all them.
On the modem settings tab in the GUI you have set the modem to the Billion and entered the correct login details haven't you?
-
have set the modem to the Billion and entered the correct login details yes
-
Perhaps use 7zip or WinZip to compress all the log files and the attach the resultant zip file to a post and then I can look through all them.
-
I am afraid that I cant get my head around winzip is it possable to email you or i could up load it to drop box
-
Yes Dropbox is a great idea, if you want you could PM the link rather than post the link on the forum.
-
https://www.dropbox.com/sh/zm19usu9jhwm9hl/AACIDhS5L_Vz5nlWi8_30lqia?dl=0 afraid there is not much in it
-
I'm currently on my tablet at work, so I'll have a look when I get chance. Need to sort out my PC first, tonight working fine last night, this morning it was sitting displaying a message that winload was missing or corrupted.
So if I haven't got back to you by Monday, give this thread a nudge.
-
No problem also had trouble last night windows 10 side froze just a blank black screen the onlly way to cure it was a tome m/c reinstal toook the best part of five hours (thank god fo time machine save a lot of hard work)
-
... displaying a message that winload was missing or corrupted.
Is it an SSD? If so may just need power cycling....
-
Yes, it's an M2 ssd, did try one power cycle this morning. I'll try again tonight, thanks.
-
I usually find that it takes two or three attempts but does work sometimes on the first. If you don't know, there is an alternative method but requires a machine with a reset button so you can restart it without the OS running or powering it off...
-
Back up and running, repeated restarts didn't work. Following this guide did though, and then Windows promptly finished installing updates. I think this is the first major issue I've had with updates on 10.
https://www.youtube.com/watch?v=J0jeNxkJqXI
I've got time to have a quick look at the op's logs.
-
https://www.dropbox.com/sh/zm19usu9jhwm9hl/AACIDhS5L_Vz5nlWi8_30lqia?dl=0 afraid there is not much in it
Your right there's nothing there really, which is odd considering the big chunk of log you posted previously.
Lets try one last thing.
Delete all the error logs from the Event & Error logs folder
Go into the setting in the GUI and on the additional settings enable extra debugging info logging.
Save the settings
Then manually run HG612_Stats.exe
Wait for the above to finish
Then manually run HG612_current_stats.exe
Then copy all the error logs to Dropbox again, and I'll take a look when I get chance, which might not be until Sunday.