Bell Home Hub 3000 - Error 2100

[Altameemy]

Internet outage- error 2100. What does this mean?

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

❗AI SUMMARY:

Discussions within the Bell Canada Community and other online platforms point to several potential causes and solutions for error 2100. This error code primarily signals a DNS (Domain Name System) issue, but user experiences suggest a few other possibilities as well.

Key causes identified by the Bell Community:

• DNS errors: The most frequently cited cause for error 2100 is a problem with the DNS servers. This means the modem is having trouble translating website addresses (like "google.com") into the IP addresses necessary to establish a connection.
• Internet outage: The error can also be a symptom of a broader internet outage.
• Authentication and provisioning issues: Some users have reported that the error was due to an authentication or credential error, which could relate to the modem not being properly programmed or provisioned on the network.

Solutions and troubleshooting steps from the Bell Community:

When faced with error 2100, forum members have found success with a range of troubleshooting steps, from simple reboots to more technical adjustments.

• Manually change DNS servers: A common and often successful solution is to manually change the DNS servers on the modem. Users have reported that switching to a public DNS provider, such as Google's (8.8.8.8 and 8.8.4.4), can resolve the issue. This is done by logging into the modem's administrative interface. To access the modem's settings to change DNS or run diagnostics, you can typically navigate to http://192.168.2.1/ or bell.ca/mymodem in your web browser.
  
• Clearing DNS cache: Clearing the DNS cache on your computer is one suggested troubleshooting step.
• Reboot the modem: A simple power cycle of the modem can sometimes clear the error.
• 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.

[WelshTerrier · Accepted solution]

This code is related to an DNS / Outage issue. Log in to your modem & check to see if your Internet is up and running. (To Log in to your modem: Open your web browser and visit bell.ca/mymodem or 192.168.2.1 Enter your administrator password.)  If it shows it is okay,  I would suggest that you run a Speed test from the main screen window: Tools & settings  > Speed test.

If everything is copacetic, then you can move on. If not, you may want to run the Virtual Repair Tool. This tool can identify & repair any number of problems.

Internet: troubleshooting tools, virtual repair tool and support (bell.ca)

If this fails as well, then I would reach out & contact Bell Fibe Internt Tech Support for further testing & analysis.

Let us know how you make out & if you are requiring any further assistance.

Take care.

[Xanadu · Accepted solution]

@WelshTerrier provided an excellent response. I have had this error code twice in the last year on two different occasions. In both instances, the issue wasn’t a network outage but a HH3000 that needed to be replaced. The device was simply faulty and this was the code displayed. Underscores the advice to contact Bell Tech Support when your own troubleshooting, and that provided on Bell sites, doesn’t solve the problem. 

[Batmarin]

Asking everybody with the same error-code to share some more details.

During the last 2-3 weeks this error started showing on my modem frequently, after 5 years of uninterrupted use. I-button is red, error code ERROR 2100 appears in red, and there is no internet connection.After restarting the modem (simple restart with the button or from the dashboard) internet is back until the next interruption (3-5 times a day, sometimes in the night as well). Sometimes there is a message "New device connected" in red and the I-button is red. After pushing the latter message disappears and I-button becomes white.

Spoke with Bell support several times and received a new modem. It worked perfectly in the beginning then it started showing the same error. Tried to check hardware attached after the modem for errors. There is only an ethernet switch and 7 wired devices, one of them is a WPA, but I rarely use Wi-Fi connections, only for guests (phones). Replaced Ethernet-cable from modem to switch.

In the modem system logs (dashboard) I'm seeing very often the following errors/warnings:

1. DNS name resolution failure

2. ppp0:Request for a new authenticated connection

and the following 2 infos:

1. TR-069 connectivity to remote server has been initiated

2. TR-069 connectivity to remote server has been closed

Which of the above is Error 2100 and which one is causing the internet-interruptions?

Is it an authentication connection failure or a DNS-failure? Or something else?

Thanks in advance!

[WelshTerrier]

Good Day.

This code is related to an DNS / Outage issue. Log in to your modem & check to see if your Internet is up and running. (To Log in to your modem: Open your web browser and visit bell.ca/mymodem or 192.168.2.1 Enter your administrator password.)  If it shows it is okay, I would suggest that you run a Speed test from the main screen window: Tools & settings > Speed test.

1. I will assume that you have restarted your computers, connected devices & Bell modem. If not, then you should do so.
2. Have you tried to clear your DNS cache? In Windows 10 / 11, open Command Prompt as administrator, type ipconfig /flushdns, and press Enter.
3. Have you tried to isolate the issue by disconnecting each device & reconnecting them one by one?
4. Have you tried to run the Virtual Repair Tool? This tool can identify & repair any number of problems.

Internet: troubleshooting tools, virtual repair tool and support (bell.ca)

If this fails as well, then I would reach out once again & contact Bell Fibe Internet Tech Support for further testing & analysis.

Let us know how you make out & if you are requiring any further assistance.

Take care.

[Vanadiel]

I am not aware what error code 2100 means. I will ask around...

Here's a list of all error codes.

[Batmarin]

Hi there and thank you for your prompt reply!

I already read your answers in connection with the same question earlier and did what you've been suggesting - it didn't help. I called Bell/Virgin helpline and I was told that error code 2100 is an authentication error - I don't think this is correct but one of the warnings I can find in the modem-log many times during the day (and night!) is:

SYS	ppp0:Request for a new authenticated connection

On the other hand the errors I'm seeing in the log are mostly:

DNS	DNS name resolution failure

I changed the DNS-setting in the modem to "Manually specify DNS information."

I've used 1.1.1.1 or 8.8.8.8. "DNS name resolution failure" remains, showing many times a day.

From time to time I see on the modem the message "New device connected". When the message is in white, there is indeed a new device connected recently. When the same message is in red, I didn't connect any new device before the message shows. After pushing the I-button the message (in red) disappears.

To answer your 4 questions:

1. Yes, many times. I even did factory resets on the brand new modem. I restarted all connected devices more than 2-3 times each resp. re-installed any software they are using (e.g. for WAP, security cameras). Installed the latest firmware (e.g. for the WAP)

2.Yes I did it - 4-5 times since the new modem is in use. After that the modem is working normally but I can't say if this temporarily "solves" the problem and for how long.

3. Yes, but I can't say which device (if any) might cause the internet loss and the above mentioned error. The system works perfectly in any possible combination I have tried but for 2-3 days max. I don't know how many combinations can be made with 7 devices attached/detached to/from the modem (via switch) but I need years to check all of those (e.g. 2 devices attached - 5 detached compared to 3 devices attached-4 detached). Not all of them are used all the time so I have sometimes 3 on and 4 off and later 5 on and 2 off but this doesn't change anything.

One of the devices is an ATA - changed its DHCP information to BRIDGE (instead of NAT). Modem worked perfectly 2 days and stopped (again no internet, error 2100) on the third day. Sometimes (I don't know if the error code shows) the internet connection is slow, lagging, sites don't open, internet stops. When I go and check the modem, everything is fine and after pushing the I-button I see the message" Your modem is working correctly." When I go back to my PC the internet is back. In the system log I usually see:

SYS	ppp0:TR69 ConnectionRequest: processing request from ACS

SYS

ppp0:TR69 creating new session with ACS

4. Yes. But when I come to point "resetting the modem" (by myself at the modem or from distance, by provider) after the reset I do have internet, modem is working so I have to answer the next question with "Yes" and for the VRT the problem is solved. Not until the next time....

The last interruption I had was around 2:30 a.m. It's almost 12 hours since but I have at least 30 times (every 10-15 minutes sometimes) the message

ERR

DNS

DNS name resolution failure (teredo.ipv6.microsoft.com)

 in the logs.

I hope I described as much as I could.

I asked could I sent my modem logs to somebody to check them but received a negative answer on the support line 2-3 days ago.

Regards!

[Vanadiel]

ERR

DNS

DNS name resolution failure (teredo.ipv6.microsoft.com)

teredo is a tunnel to allow IP6 devices to communicate with IP4 devices.

Are you using IP6 or IP4, or both?

[Batmarin]

Thanks for the reply!

I'm using both.

The standard modem-setting for IPv6 is "ON" - I didn't touch it since the modem has been installed and in use.

When I ping any of the 2 protocols in Utilities, there are no losses (0%).

Both protocols are activated in all devices attached to the modem/hub as well.

[Vanadiel]

Try turning IP6 off in the modem. Wondering if there's some kind of firmware bug.

[Batmarin]

I turned it off. 4'30" later I see the following errors in the modem log:

ERR

DNS

DNS name resolution failure (foodanddrink.tile.appex.bing.com)

ERR

DNS

DNS name resolution failure (teredo.ipv6.microsoft.com)

I have no idea what is "food and drink-tile-appex-bing" but I've seen this error before, a couple of times.

Modem is working without problems though - no internet interruptions so far. No messages on the modem itself.

[Vanadiel]

That failure would be normal as foodanddrink.tile.appex.bing.com can indeed not be resolved by a DNS server.