Purchased (3) Comet units. Upgraded firmware to v. 1.2.2. release1 - Binding error on all units, tested with multiple computers. White light on unit - non will successfully BIND. Windows machines.
I'm very sorry for the inconvenience caused. Could you please give us your device mac so that I can check the factory information of the device on the platform to see if it is normal
94:83:C4:AD:92:13
94:83:C4:AD:91:11
Hello, can these two devices be bound normally now
Negative. Binding Failed. I purchased (3) Comets. None have ever worked. 94:83:C4:AD:90:A2
and 94:83:C4:AD:92:13 and 94:83:C4:AD:91:11. Multiple RESETS. Firmware(s): V1.1.0 release2 and ver.1.2.3. No DNS resolution. Have wasted literally HOURS on this. Don't think this COMET "pre-release" should have shipped.
Please try to manually set the DNS server according to the method in the link.https://docs.gl-inet.com/kvm/en/tutorials/how_to_set_static_ip_for_comet/
This also has never worked. RESULTS:
Error: The name net.connman was not provided by any .service files
Error 'config': Invalid argument
Normally, port 53 corresponds to the command program.
If you are using dnsmasq, you can try to disable it and manually enable comman, the command is as follows(this command will cause rm1 to reconfigure the network):
/etc/init.d/S80dnsmasq stop; /etc/init.d/S45connman restart
After execution, port 53 will be monitored by the command program. You can now configure the DNS server through the previous link.
ERROR - NO SUCH PROCESS:
TERMINAL OUTPUT:
bash-4.4# /etc/init.d/S80dnsmasq stop; /etc/init.d/S45connman restart
Stopping dnsmasq: OK
Stopping connmand: start-stop-daemon: warning: killing process 629: No such process
FAIL
Starting connmand: OK
bash-4.4# connmanctl config connmanctl services |grep ethernet|awk -F' ' '{print $3}' --ipv4 manual 192.168.0.254 255.255.255.0 192.168.0.1
Error: The name net.connman was not provided by any .service files
Error 'config': Invalid argument
Please pay attention to the private message, we will have engineers to help you solve this problem remotely
Please check your private messages. Our engineers have tried to contact you via private messages a few days ago, but have not received a response.
Sorry for the inconvenience caused. Please follow the following plan to check the network situation of the device
- KVM device and your PC are on the same LAN
- Open the browser and access using the KVM intranet domain name or IP address. The default intranet domain name is
glkvm.local - Click the Toolbox and Access buttons on the page to enter the device terminal
- Enter the following command at the command line to check the DNS and network status of the device, and save a screenshot of the output status.
ping google.com
netstat -ntlp | grep 53 - Provide device logs to us for further analysis.
All instructions to resolve the issues with these COMETS (I bought 3) have been repetitive and useless. Can I get an RMA on these things?
It looks like there is a problem with the device's domain name resolution, and our engineers will follow up.
Have you tried connecting Comet to other networks to resolve the domain name normally?
Three (3) Comet units. I have access to three networks, home, work, and a friends house. Same result on all three. Reset each unit 3-5 times. Upgraded firmware on 2 units twice. Home and work have Synology Routers/Access points - Comcast cable. Friends Network uses Verizon and Verizon router/gateway. no difference on any of the networks. Reset each unit on all. DNS resolution error on all. No binding on any unit ever.
Could you please provide us remote access, such as teamview?
You can email me directly at zefu.du@gl-inet.com
Binding Fails. I purchased (3) Comets. None have ever worked. 94:83:C4:AD:90:A2
and 94:83:C4:AD:92:13 and 94:83:C4:AD:91:11. Multiple RESETS. Firmware(s): V1.1.0 release2 and ver.1.2.3. No DNS resolution. Have wasted literally HOURS and now... weeks. So, is any solution or RMA forthcoming? Thank you.
We have contacted you several times to troubleshoot the problem, but have not received a response.
We are sorry to bring you a bad experience. You can contact cs@gl-inet.com to return the device.
"We have contacted you several times to troubleshoot the problem, but have not received a response."
Untrue. 22 days of responses to multiple suggestions I "reset" the devices which I have done. You are correct, I did ignore the ridiculous suggestion I install TEAMVIEWER or some such and jump through a bunch of hoops to allow your customer service people to access my network and machines remotely. That's a joke right? I'm not sure what forum "private message" I am supposed to be "paying attention" to. How about just posting any real solutions on THE FORUM for everyone to see? That would be helpful. I do see I have finally been offered the option to return the three non-working COMETS, (because these COMET units grab an IP address via DHCP from my router however they do not obtain valid DNS values - and there seems to be no method whatsoever of assigning a static IP AND DNS ADDRESS to the units?) so if no actual solution is forthcoming - yes I will RMA the 3 units.
1 Like