Bell

We are a new Bell user and we have the new HH4000 Gigahub. We have only been with the service for a week but are facing a constant issue where after resetting the HH4000 all devices can connect to the wifi and access internet BUT after some time all connected computers (and computers only) will stop being able to access the internet... They can still see the Wifi network perfectly but cannot access the internet.

Bell support were unhelpful and suggested it was an issue with our computers (because all other connected devices like cell phones and tablets can still see and access the internet).

I can guarantee it is not our devices and even more telling, it is only happening with the three computers we connect to the network (2x Mac's 1x Windows so also not an OS specific issue).

After doing my own research the mac's were able to be brought back online (once) after resetting the network settings on the devices (this addressed a 'self assigned IP address' error both mac's were reporting as the issue in Network diagnostics)...  Here are the resources for others facing this issue: https://www.igeeksblog.com/internet-not-working-due-to-self-assigned-ip-address-on-mac/#Reset-your-n....

BUT THE STORY CONTINUES:

The above fix only worked the once and after a period of time all computers once again reported being unable to reach the internet DESPITE having a solid connection to the HH4000 wifi network.

We are currently falling back to our Rogers internet (which thankfully we haven't cancelled yet) so we can WFH each day given our work computers won't connect via Bell... I really need a long term solution for Bell to be a long term viable option for us!  Any assistance is appreciated 🙏.

Also worth noting:

- Tonight I will swap the HH4000 for the HH3000 to test if this will fix the issue 🤷‍♂️

- Despite the Bell Wifi app not indicating that any devices are 'Blocked' from the internet, it feels like the HH4000 is arbitrarily blocking all our computers from accessing the internet 🤔

- Thanks in advance, I appreciate any advice/suggestions 🙏

❗AI SUMMARY:

The error message "Error 1202 - No HSI configured" or "Configure HSI service" indicates that the modem is not properly activated or provisioned on the Bell network.

Key causes identified by the Bell Community:

• Provisioning and activation Issues: A common theme is that the modem, although receiving a signal, is not correctly authenticated or registered on the Bell network. This can happen with new installations or after a modem swap. One user noted that this is a "provisioning issue," where the modem isn't authorized for service.
• Fibre connection problems: The error can be linked to a problem with the physical fibre optic connection itself, such as signal strength issues. While a complete fibre cut might initially show a different error (like 1201), error 1202 can appear after a reboot during an outage.
• Equipment or infrastructure problems: While a possibility, but uncommon; swapping the modem for a new one has not always resolved the issue, suggesting the problem often lies with the service configuration rather than the device itself.

Solutions and troubleshooting steps from the Bell Community:

Community members have detailed several steps they have taken to resolve error 1202, ranging from basic user actions to requiring technical help:

• Basic Troubleshooting: Before calling for support, users suggest checking for any loose fibre cable connections and performing a full reboot of the modem by unplugging it for 30 seconds.
• Factory Reset: A factory reset of the modem, by holding down the reset button for 10 seconds, can sometimes resolve configuration problems by forcing it to re-download its settings.
• Device-Specific Network Reset: Some users experiencing intermittent internet access on specific devices (like computers) after the error appeared found temporary relief by resetting the network settings on those affected devices. However, this was often not a permanent solution.
• Use Virtual Repair: The Bell Community Manager recommended using Virtual Repair. This tool can check for local outages, inspect external equipment, reboot your system, and optimize settings. If the issue persists, the tool can help schedule a technician visit.
• Check for outages: It's worth checking if there is a known service outage in your area. How to check for Internet outages in your area or Outage Check.
• Contact Bell Support: Should the above fail to identify or resolve the issue, a technician may be required. Technicians can diagnose and repair issues with the external wiring, connectors, or other infrastructure problems that are beyond the user's control. Should you need to book a technician, reach out using Live Chat or you can dial *611 from any Bell mobile device.

I jus signed up with Bell about a week ago and downloaded the Bell Wifi app. However it will not allow me to login. I’m using same credentials as I use with MyBell APP which I can log into but no luck. Even tried to reset password (forgot password option) and I still can’t login and therefore not install a pod. What am I missing?

Today my bell internet Fibre 50 FTTH stopped working. My device still showed connection to the Wifi but there was no internet. The modem showed “Error 1201 - Low fibre signal Check fibre connection”. Restarting modem couldn’t fix the problem.

❗AI Summary:

Users experiencing the "Error 1201 - Low fibre signal" have identified several potential causes and solutions, primarily pointing to issues with the physical fibre optic connection. The error indicates that the modem is receiving a weak or no light signal through the fibre optic cable, preventing internet access.

Key causes identified by the Bell Community:

Discussions in the Bell Community Forum and other online platforms highlight a range of possible reasons for the error:

• Damaged or disconnected fibre optic cable: This is the most commonly cited cause. The cable could be cut, bent, or damaged externally, such as by landscaping activities. It could also be disconnected at the street-level utility box.
• Faulty or improper connections: The error can occur if the fibre optic cable is not securely connected to the modem or the wall socket. Additionally, the end of the fibre optic cable that plugs into the modem can become dirty and obstruct the signal. In some cases, the connector itself may be faulty.
• External infrastructure or equipment problems: Issues with your Bell modem or other network equipment can lead to this error. Issues may originate from outside the home, such as a problem at a node or demarcation point.
• Incorrect provisioning: A less common but possible cause is a "speed profile" or programming error on the user's account, which would require correction by Bell.

Solutions and troubleshooting steps from the Bell Community:

Forum members and Bell moderators have suggested several troubleshooting steps, ranging from simple checks to requiring technical help:

• Basic troubleshooting: The initial steps include rebooting the modem and ensuring the fibre optic cable is securely connected. However, users often report that a simple reboot does not resolve this specific error.
• Cleaning the fibre connector: Some users have had success by carefully unplugging the fibre optic cable from the modem (holding it by the green housing) and cleaning the tip with a lint-free cloth and rubbing alcohol.
• Use Virtual Repair: The Bell Community Manager recommended using Virtual Repair. This tool can check for local outages, inspect external equipment, reboot your system, and optimize settings. If the issue persists, the tool can help schedule a technician visit.
• Check for outages: It's worth checking if there is a known service outage in your area. How to check for Internet outages in your area or Outage Check.
• Contact Bell Support: Should the above fail to identify or resolve the issue, a technician may be required. Technicians can diagnose and repair issues with the external wiring, connectors, or other infrastructure problems that are beyond the user's control. Should you need to book a technician, reach out using Live Chat or you can dial *611 from any Bell mobile device.

What is error 2000 on Bell modem 3000?

❗AI SUMMARY:

Based on discussions within the Bell Community forum, modem error 2000 indicates a connectivity problem. Community members and official Bell documentation cited in the forum point to several potential causes for error 2000. The error message itself signifies that the modem is "Currently unable to connect to the Bell servers".

Key Causes Identified by the Bell Community:

• Network outages: The most common reason cited for error 2000 is a general network outage in the user's area. This can sometimes be due to network upgrades, 3rd party fibre cuts and other temporary service interruptions.
• Authentication issues: An "authenticity problem" where the modem is not correctly linked to the user's service agreement with Bell was identified as a cause. This could happen after a modem switch or an internet plan upgrade. One user noted the problem was temporarily resolved by changing the internet password, suggesting an authentication issue. On newer Home Hub models like the Home Hub 4000, Giga Hub or Giga Hub 2.0, the error is specifically related to internet account authentication.
• Hardware or connection problems: Physical issues can also lead to this error, including a defective modem, a poor fiber connection, or a damaged external cable.
• Generic connection failure: The error is sometimes described as a "generic" code indicating that the modem cannot connect to Bell's servers for an unspecified reason.

Solutions and troubleshooting steps from the Bell Community:

Forum participants and moderators have suggested a range of solutions, from simple resets to contacting technical support.

• Wait and retry: Since the error often relates to an outage, the most frequently suggested first step is to simply wait for a while and try connecting again later.
• Power cycle the modem: A common troubleshooting step is to perform a full power cycle by unplugging the modem (and disconnecting any backup battery), waiting for a few minutes, and then reconnecting everything.
• Reset the modem: A full reset of the modem by pressing the reset button was reported by one user to have fixed the problem. Another user mentioned a factory reset as an advanced step if other solutions fail.
• Check physical connections: Ensure all cables connected to the modem are secure and undamaged.
• Use Virtual Repair: The Bell Community Manager recommended using Virtual Repair. This tool can check for local outages, inspect external equipment, reboot your system, and optimize settings. If the issue persists, the tool can help schedule a technician visit.
• Check for outages: It's worth checking if there is a known service outage in your area. How to check for Internet outages in your area or Outage Check.
• Contact Bell Support: Should the above fail to identify or resolve the issue, a technician may be required. Technicians can diagnose and repair issues with the external wiring, connectors, or other infrastructure problems that are beyond the user's control. Should you need to book a technician, reach out using Live Chat or you can dial *611 from any Bell mobile device.

It would be great if Bell could confirm if they are going to update the FW on the HH4000 to enable a true bridge mode setup...also to stop the Wifi from automatically re-enabling itself anytime the HH4000 reboots itself. These are two MAJOR issues right now with the HH4000 and posted about on many forums (not just here).

It would be great if someone from Bell could chime in and let the community know if it is actually going to address these issues or not? If not, please explain why and please do not point to advanced DMZ as a solution because that doesn't actually work very well and severely impacts the performance on the Google Mesh (or any other pre-existing mesh setup). This is also discussed on many forums both on this one and externally by your customers.

We do realize the HH4000 is relatively new so there can be some improvements. We, as a community, just want to know if Bell plans to make those improvements or not.

Thanks,

-Derek

❗AI Summary: 

When attempting to use a third-party router, customers frequently encounter networking challenges due to the absence of a true 'bridge mode'. This limitation has led to a variety of solutions involving PPPoE and the Advanced DMZ feature to avoid issues like double NAT; where two devices on the network are performing Network Address Translation (NAT). Double NAT can lead to problems with online gaming, port forwarding, and other applications that require a direct connection to the internet.

Some complications you may experience:

• Wi-Fi auto re-enabling: Even when disabled, the Bell Home Hub's Wi-Fi can turn back on after a reboot.
• Advanced DMZ limitations: Advanced DMZ can be unreliable, especially with third party mesh systems. PPPoE is preferred by users in this scenario.
• IP lease and connectivity drops: Devices lose connection when the public IP changes, requiring manual reconfiguration.
• Performance degradation: Speeds, especially download speeds can drop over time. A reboot or modem reset will be needed to restore.
• No static IPs: IP changes cause disruptions. Using DDNS can be considered.

In response, Bell Community users have detailed two primary methods to approximate a bridge mode: PPPoE passthrough and the use of the Advanced DMZ feature.

User-Shared Solutions:

PPPoE Passthrough: Often described as more stable and straightforward; it involves configuring the third-party router to establish the PPPoE connection directly with Bell. This effectively bypasses the Bell Home Hub 4000, Giga Hub and Giga Hub 2.0's routing functions, providing the third-party router with its own public IP address. To do this, users typically need to obtain their "b1" username and password from Bell. While stable, a significant drawback of this method is a potential reduction in internet speeds, particularly on plans faster than 500 Mbps, as many consumer routers struggle with the overhead of PPPoE.

Advanced DMZ: This method involves placing the third-party router in the modem's "Advanced Demilitarized Zone." This exposes the third-party router directly to the internet, which can result in higher performance. However, this solution is often reported to be less stable. For instance, rebooting your router might necessitate a subsequent reboot of your Giga Hub/Giga Hub 2.0 to restore the internet connection. Some have also reported experiencing lag spikes with this configuration. When using Advanced DMZ, it is advised to leave the login information on the third-party router blank, as entering PPPoE credentials can cause the connection to fail.

Configuration Tips from the Bell Community:

• When setting up either method, it's recommended to disable the Wi-Fi on the Bell Giga Hub/Giga Hub 2.0 to prevent interference.
• For PPPoE passthrough, connecting the WAN port of the third-party router to any LAN port on the Bell hub and configuring the router with your b1 credentials is the general procedure.
• For Advanced DMZ, users need to enable the feature in the Giga Hub/Giga Hub 2.0's settings and assign their third-party router to it. It's also highly recommended to not plug other devices directly into the Bell hub for security reasons when using Advanced DMZ.

Ultimately, the choice between PPPoE passthrough and Advanced DMZ depends on the user's priorities. If stability and ease of setup are paramount, PPPoE passthrough is often the recommended choice. For those who prioritize performance and are willing to troubleshoot potential instabilities, Advanced DMZ may be the preferred option.

How do I split the wifi 5g and 2.4g on home hub 4000 so I can connect my Globe plugs which are 2.4 g only. Need my iphone only to be on 2.4 g network to do this and it automatically on the 5 g network.

-------------------------------------------------------------------------------------------------------------------------------------------------------

❗AI Summary:

"Band steering" technology broadcasts a single Wi-Fi network name (SSID) for both the 2.4 GHz and 5 GHz frequency bands, intending to automatically guide devices to the optimal band for better performance. However, this creates significant problems for devices that can only operate on the 2.4 GHz frequency.

The primary issue reported by users is the difficulty in connecting smart home devices—such as plugs, switches, and cameras—that are exclusively compatible with the 2.4 GHz band. During setup, these smart devices require a connection from a smartphone or computer that is on the same 2.4 GHz network. With band steering enabled, phones and computers often automatically connect to the 5 GHz band, preventing them from communicating with and configuring the new smart devices which are on the 2.4 Ghz band. Users have also reported unstable connections and frequent disconnections for some devices when band steering is active.

Solutions and advice shared by users in the forum thread include:

To address these challenges, forum members have shared several workarounds, primarily centered on disabling the band steering feature to separate the two Wi-Fi bands.

Permanent Separation of Wi-Fi Bands: The most common solution is to create two distinct SSIDs for the 2.4 GHz and 5 GHz bands. This is typically achieved by:

1. Logging into the Bell modem's administration page using a web browser (commonly at http://192.168.2.1).
2. Navigating to the "Manage My Wi-Fi" section.
3. Disabling the feature labeled "Whole Home Wi-Fi."
4. Access "Advanced settings" and uncheck the option to "Keep a common network name."
5. Assigning different names to the 2.4 GHz and 5 GHz networks (e.g., "MyNetwork-2.4" and "MyNetwork-5G").

This allows users to manually connect their setup devices (like phones) and smart products directly to the 2.4 GHz network.

Temporary Disabling for Device Setup: A less disruptive method involves temporarily disabling the optimization feature to connect a specific device.

1. Log in to the modem and turn off "Whole Home Wi-Fi."
2. Temporarily rename the 5 GHz network to force the device to connect to the 2.4 GHz band for setup.
3. Once the 2.4 GHz device is successfully configured, log back into the modem and re-enable "Whole Home Wi-Fi" to restore the single SSID.

Note: Permanently disabling the "Whole Home Wi-Fi" will prevent functionality and access to the Bell Wi-Fi app and Bell Wi-Fi pods, which rely on the integrated network management system. Some users ultimately revert to the default settings and opt for a more manual pairing process for their smart devices to retain these features. For persistent issues, some have resorted to using a separate, third-party router or access point dedicated to their 2.4 GHz devices.