Widgets du forum
Discussions récentes
Port Forwarding
Yesterday I tried to ascertain why the pert forwarding I had set up over a year ago had become unstable. I logged into my Helix Modem/Router and went to the Port Forwarding section of the Advanced settings. I added an additional port forward entry but, for some reason, none of my entries worked. Somehow I found out that from now on I would have to use the website at helixfi.videotron.com in order to put in my entries. To give you a little background, I am a retired computer professional with over 40 years of experience in the field. In all that time I have never come across a setup that was so poorly written. I really don't know why it was necessary to deploy it in the first place since port forwarding has always been something folks did locally on their routers. I have at least three observations to make regarding the performance of this website. First, the website nor the Helix h/w use name resolution properly. Therefore all the Connected Devices show mainly MAC addresses without their names being resolved so you need to create a table yourself to cross check which MAC address corresponds to which connected device. Second, the ability to set up port forwarding locally is now removed so we need to deal exclusively with the website. The actual interface on the website is klunky. The drop-down list of the "Selected the device for this port forward" doesn't even match the one on he Helix equipment. Devices are listed as "Generic Windows PC/Laptop" or "Asus Windows PC/Laptop". If I only had 1 or 2 devices on my home network I could mange to identify them this way. Unfortunately, I have over 20 computers without counting all the virtual systems I have also deployed. Therefore, it is virtually impossible to figure this out. Yes, name resolution is the key!!! Third, a long time ago I must have brought up a laptop using DHCP, and an IP address ending in ".230" was assigned. I use reserved or fixed IPs at home except for cell phones and the like. The laptop in question was later assigned an IP ending in ".98". For some reason, the website recorded the ".230" address and it won't relinquish it. On the Helix device I modified the entry for the laptop to make sure it ends in ".98" but, lo-and-behold, the website ignores this in favour of the ".230" IP. Fourth, when I called in to support to see if they could help me it became obvious he could not. I was suggested that maybe I should use the Helix device as a modem only and have an additional router introduced where I could set up port forwarding myself locally. Furthermore, the website interface is asinine in the way it requires the port information to be entered. Why not copy the same set up that existed in the Helix device before it was demoted?
Is Videotron planning to offer higher upload speeds?
I understand that for most people, 50mb/s upload is just fine. However, it's absolutely not enough for me. I upload content near daily that exceeds 10 gigabytes in size, and I require constant, stable outgoing connections of 20+ mbps. With all over videotron's current plans, this is impossible, and has cost me many hours of frustration. I'm even willing to pay business internet prices if I need to, but I need at least 100 megabit upload, if not more.
can't access bing.com
I have a strange issue: 90% of the time I can't access bing.com when on videotron's helix wifi. It happens on all devices connected to my wifi. If I switch my cellphone to use telus's network, all works fine. I can't access bing.com, and then after a while I can access it again. Sometimes I can't access bing.com via edge but can via chrome, sometimes the other way around. soon after I can't access bing.com on either browser. Later that day it'll start working again on both. But most of the time it's inaccessible. All other sites I use work just fine, it's just bing.com that poses this strange problem
Helix and Google WiFi Mesh network - it works
Just want to share my experience with Helix and Google Wifi mesh network as when I was subscribing no one seemed to know if it would work or not. The short answer is it works perfectly - but requires some manual adjustments. 1. Set-up your helix wifi modem router using the app 2. Connect your Main Google wifi point to the Helix router ethernet with the red line marking 3. Restart the helix modem and then restart the Google wifi main point 4. Both HELIX and your Google wifi networks will now work at the same time which means you do not need to migrate all of your devices to a new network 5. Bridge Mode to ONLY have your google wifi network (and close the Helix wifi signal and simply use as a cable modem). I tried this and for some reason internet speeds on the google network were substantially slower than if I left it in normal mode. So after experimenting I now leave the HELIX with BRIDGE MODE DISABLED – so you will have a choice of either Helix or Google Network for Wifi. 6. YOU CAN connect your TV Helix devices to the Google Network. I have one TV connected to the Google wifi network and one to Helix wifi - and both work perfectly. Hope this helps others.How do you keep your precious voicemail messages?
If you’re like me, you’ve had voicemail messages from your loved ones saved in your mobile or home phone voicemail for some time. Unfortunately, voicemail is not like a safe, and sometimes these messages are deleted. If you want to protect your precious messages, there are solutions. I used a microphone connected to my computer and the Audacity app. I played the saved messages from my phone near the microphone to record them, then converted them into MP3 files that are now safe in my computer and its automatic backups. You can also do the same thing using two cell phones and an audio recording app, such as Smart Recorder or Recforge 2 on Android and Recorder Plus or Audioshare on iOS. Don’t dawdle too much and make these backups early this year to make sure you keep important messages from your loved ones! As for yourself, have you found another solution to keep your important voicemail messages?
Information for the WPA2 KRACK Flaw and Videotron's Zyxel router
According to Zyxel: http://www.zyxel.com/support/announcement_wpa2_key_management.shtml The only routers affected are those with the802.11r Fast-BSS Transition (FT) handshake feature. Those are modelsNWA5301-NJ,NWA5123-AC,WAC6103D-I andWAC6500 series. If you have one of those models, you will have to wait for February 2018 for a fix. You can also turn off that feature (see link above) to prevent been affected by the flaw. Videotron's latest router is actually Zyxel's EMG2926 and is not in the list. http://www.videotron.com/residential/internet/equipment/residential-internet/new-generation-wi-fi-router Zyxel's position on this is that those models not included are not affected: "For products not listed, they are not affected to the attacks either because they are not designed to act as WiFi clients, do not support 802.11r Fast-BSS Transition handshake, or do not support peer-key handshake by default." That should clear it up.Videotron started DOCSIS 3.1 deployment 4 years ago. When can we expect faster upload?
DOCSIS 3.1 deployment started in 2016, and by now, every new installation should have a DOCSIS 3.1 capable modem, whether it's a Helix plan or not. DOCSIS 3.1 also supports upload speeds up to 1 Gbps. Given all this, when can we expect to actually see these sorts of speeds with Videotron? Right now, no matter how much you pay or how badly it's needed, you are not able to get more than 50 mbps upload. This is probably fine for a good portion of people, but given the pandemic, it's absolutely not fine for many software developers and content creators who are now forced to work from home. Uploads that would take only a few minutes in the office now take upwards of half an hour, completely gutting my productivity through something completely out of my control. This is especially embarassing when other ISPs are offering symmetric gigabit speeds, while videotron can't even offer gigabit in a single direction. You have the infrastructure in place, the technology already exists, when can we start expecting more modern speeds?
Windows live mail error 0X800C013E after WIN10 feature 2004
I copied the link to the solution at Microsoft after translating it into english (now in bold print). Here it is and it worked for me, after spending an hour searching unnecessarily with Videotron tech support whose fault it wasn't. I also got a few dozen previously deleted messages reappearing in my inbox and sent box. In all the previous upgrades to WIN10, there has never been a snag with Windows Live Mail. Windows Live Mail (2012) error 0X800C013E after installing WIN10 feature 2004 Close Windows Live Mail. In the registry under Computer \ HKEY_CURRENT_USER \ SOFTWARE \ Microsoft \ Windows Live Mail create these 3 DWORD entries (I didn't have them) or change them to 1 if available RecreateFolderIndex = 1 RecreateStreamIndex = 1 RecreateUIDLIndex = 1 Restart Windows Live Mail. Then the message display goes back to normal for me and the 3 values in the registry are reset to 0. Can be left like this. For me, the account display in WLM with several accounts after the Windows Update 2004 was corrupt. This is also fixed.
