New answers tagged home-networking
So here is my forensics on what you are presenting: The Basics 220.127.116.11 is a multicast address in the administratively-scoped (local) multicast range of addresses from 18.104.22.168 to 22.214.171.124. Since 126.96.36.199 resolves to Bouygues Telecom, my best guess is that is your outward/WAN interface address or perhaps a router on the Bouygues Telecom ...
This usually comes down to either channel support issues (which you may have ruled out) or using a hidden (non-broadcast) SSID, which some clients had been configured to scan for (added to their preferred networks list) and others had not. Make sure you haven't set your AP (Wi-Fi router) to hide its SSID. As for channel issues, channels 12, 13, and 14 ...
Assuming that the solution to your problem is "combine 2 internet connections", there are several way to do this: Deal with your ISP To increase performance of your subscription (basically they will cut less traffic from you, if the current line capacity isn't fully used). To use technologies like link-aggregation but pay attention! A router capable of ...
I had this exact problem, and it was strange, some machines connecting and some not. The cause: A wifi access point on the network had failed in a strange way, causing it to set it's BSID to the mac address of a computer that was on the network, and the Colorqube seems more picky about duplicate mac addresses than other devices. It didn't matter whether ...
It is not normal for this to happen. Your modem is likely fried. I would suggest you buy a new modem, or contact your isp for a replacement one.
Unchecking AppEx worked for me using Windows 10 Home Premium. File transfer in Filezilla accelerated to over 10X faster speed before it ran out of file to transfer. Was at around 10kbps.
The information might be in a local nameserver; you can try: nslookup HOSTNAME or nslookup HOSTNAME.yourdomain.com
I had the same exact issue, drove me nuts for months and finally fixed it by doing the following. It may be overkill but it worked and that's all that mattered to me lol. Delete all known wireless network profiles Open elevated Command Prompt (CRTL+X, Command Prompt(Admin)) Type without quotes "netsh wlan show profiles" and press Enter. This will give ...
The probable cause was a defective Ethernet port on the router. I didn't find the evidence to support this until 30 April 2015, and I didn't make the connection until 10 August 2015. What I Should Have Done A few additional troubleshooting steps: I should have tried plugging in the router end of the Ethernet cable into a different router port. Sure, I ...
It should be just a matter of ports forwarding to your internal router (changes to the config must be made on your external router): For PPTP VPN forward : Port 1723 TCP. Allow GRE traffic (if your router can block it). For OpenVPN forward : Port 1194 UDP. Maybe on OpenVPN you can change this at config. Don't hope to be capable on PPTP, I fear.
Your problem is the 20% packet loss. Contact your internet service provider and advise them of the problem you are having. A faster connection may help a little bit but try reading something with 20% of the words missing....
Top 50 recent answers are included