Question Alexa will not connect to my WiFi ?

[Paul Oberman]

I have an Alexa Dot second generation, which has been working for a long time. Recently it stopped working and hasn't been able to connect to my wifi.

So, I purchased a new Alexa 4th gen......

It has exactly the same issue connecting to my wifi. How it fails is exactly the same.

That means it must be my wifi that's the issue, it is a Meshforce M7

I have restarted the modem and the the meshforce routers and it has no effect on the Alexa connecting

I have tried disabling the the 5ghz, for compatibility, and that didn't work either

I have done hard resets of the new Alexa and gotten it to go all the way through set up and claim success, only to still have it say at the end it's not connected.

I am at a loss

 

[Ralston18]

Make and model modem? Make and model router (or modem/router if combined)?

This product/system?

https://meshwifisetup.com/meshforce-wi-fi-system-setup/

The Meshforce router's logs, if available and enabled, may provide some clue.

Are you able to use a browser to directly log into the Meshforce router via the default IP address (192.168.0.1)?

Reference:

https://www.router-reset.com/default-ip-address-list/MeshForce

(You will need the login name and password if they have been changed from the default settings.)

= = = =

Overall, I would suspect some router/network configuration error of omission or commission.

Alexa Dot 2nd Gen may have failed in some manner but other things could have happened.

And with the Alexa Dot 4th Gen not connecting then it is likely that there is a common problem.

Are you able to view the Alexa's IP address via Alexa App > Settings ?

FYI:

https://tomstek.us/how-to-find-alexa-ip-address/

How long are you waiting for the Alexa to connect? Sometimes, it takes awhile for all of the devices involved to "handshake" and recognize each other.

 

[Paul Oberman]

The modem is a technicolor DPC3216

The wifi mesh is a Meshforce M7 with wireless backhaul

Not sure how to get the connection logs. Can this be done with a third party app, without the wifi router's invovement?

Now something interesting!!! I can not reach the wifi mesh through a browser on a wired or wireless computer "this site can't be reached" I have tried clearing the cache and modifying the site settings..... nothing. What is also interesting is that the network has a Connection-specific DNS Suffix. This is something I haven't seen before. That Connection-specific DNS Suffix is for meshforcewifi.com which is some placeholder page.

I can't get the the alexa addresses, as they never finish connecting. Always show disconnected

I have waited quite a long time and gone through the connection process many times, including with the amazon support.


Thanks for your amazing input.

 

[Paul Oberman]

Ok, I have done a hard reset on my mesh network. Nothing has changed.

The only time I can get the alexa to go all the way through the set up successfully is when I do a hard reset on the alexa and deregister it.

Even then it goes all the way through the set up and it says it was set up successfully, but still says it's not connected at the end

 

[Ralston18]

I am not aware of any third party apps that can access router logs and/or other configuration information. Even if so, very likely that the router would not respond without be provided the necessary login information: e.g., login name, password at a minimum.

= = = =

According to one link, the modem's (modem/router) IP address is 192.168.100.1 with default login name being "admin" and the default password being "password".

Reference:

https://linustechtips.com/topic/121...he settings of,default password is "password".

The link includes another link to the modem's User Guide (.pdf).

Then there is this link:

https://router-network.com/technicolor-router-login

= = = =

You mentioned a router: make and model?

For most home networks the connectivity is very much like the following line diagram where ---- > represents an Ethernet cable:

ISP === (DSL, coax, fiber) ===> Modem ---> [WAN Port] Router [LAN ports] ----> wired network devices and ~~~~ > wireless network devices.

(Feel free to edit and correct my line diagram as necessary.)

However the modem and router can be combined.

So if you have a combination modem/router and then another router then that can cause problems. There should be only one router configured to provide network addresses to network devices. For the most part the modem's router functions would be disabled and the separate router would handle IP addressing etc...

As for "site cannot be reached" that is problematic.

Many manufacturers are forcing (for lack a of better word) end users to go through the manufacturer's website to configure the user's own device (modem/router, router). E.g., " meshforcewifi.com."

When all that is necessary is direct access to the router via the router's IP, login name, and password using a browser. Caveat being that no one has changed the default configuration as should really be done.

Otherwise, the option is to press some small button to restore the router to factory's default IP, login name , and password. All three can vary even with the same manufacturer.

See what else you can find and update my line diagram.

 

[Paul Oberman]

My modem is separate from the wifi mesh system. So there is a ethernet to the meshforce.

The modem is a technicolor DPC3216

The wifi mesh is a Meshforce M7 with wireless backhaul

My ip on the wifi is 192.168.0.1

Still getting "this site can't be reached" when i try to connect from the browser. Even after a complete hard reset of the wifi.

This is truly a mystery.

 

[nigelivey]

What is your IP if you are connected directly to the Technicolor and what is your IP on the Mesh, does Alexa require internet access to complete its setup?

 

[Ralston18]

"IP on the wifi is 192.168..0.1"

Router possibly being 192.168.100.1

Copy and paste my line diagram in Post #5 but show (as requested by @nigelivey ) the IP addresses being used by each of the connected devices. Wired or wireless.

Which device is the router (default gateway)?

On a working computer with working access to your network and the internet access run "ipconfig /all" (without quotes) via the Command Prompt.

Post the results. (You should be able to copy and paste the results with no need to retype it all.)

 

[Paul Oberman]

"IP on the wifi is 192.168..0.1"
typo

Router possibly being 192.168.100.1

Copy and paste my line diagram in Post #5 but show (as requested by @nigelivey ) the IP addresses being used by each of the connected devices. Wired or wireless.

Which device is the router (default gateway)?

On a working computer with working access to your network and the internet access run "ipconfig /all" (without quotes) via the Command Prompt.

Post the results. (You should be able to copy and paste the results with no need to retype it all.)

Now an interesting development.

Left the dot plugged in all night. Woke up this morning and it is connected. Interesting thing is that it still shows as disconnected in the app
The wifi was reset yesterday to generate an IP address of 192.168.0.1 BUT this morning it has changed itself to 192.168.7.1 Still can't access it through the web interface

represents an Ethernet cable:

Comcast ===> ( coax,)
===> modem is a technicolor DPC3216
---> [1 WAN Port] meshforce m7[2 LAN ports]
---->pc wired 192.168.7.136
~~~~ > wireless network devices

1. macbook 192.168.7.165
2. unknown 192.167.7.184
3. mitsu 192.168.7.199
4. unknown 192.168.7.154
5. unknown 192.168.7.159
6. amazon 192.168.7.157
7. unknown 192.168.7.130
8. imac 192.168.7.180
9. amazon 192.168.7.200 (2.4ghz)
10. irobot 192.168.7.113
11. macbook 192.168.7.194
12. vizio 192.168.7.174
13. thingsturn 192.168.7.189 (2.4ghz)
14. esp_1FA6EE 192.168.7.129 (2.4ghz)

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-29K9N9U
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : meshforcewifi.com

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : meshforcewifi.com
Description . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Physical Address. . . . . . . . . : 0A-E0-AF-C1-02-B0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::8f1f:aebf:7427:31b9%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.7.136(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, April 9, 2023 10:24:56 AM
Lease Expires . . . . . . . . . . : Sunday, April 9, 2023 11:24:54 AM
Default Gateway . . . . . . . . . : 192.168.7.1
DHCP Server . . . . . . . . . . . : 192.168.7.1
DHCPv6 IAID . . . . . . . . . . . : 101376175
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-41-12-FA-0A-E0-AF-C1-02-B0
DNS Servers . . . . . . . . . . . : 192.168.7.1
NetBIOS over Tcpip. . . . . . . . : Disabled

 

[Ralston18]

The lease time is only one hour.

Try changing theDHCP IP address lease time to 168 hours (7 days).

Disable IPv6.

Regarding:

"The wifi was reset yesterday to generate an IP address of 192.168.0.1 BUT this morning it has changed itself to 192.168.7.1

What, where, and how was the wifi reset done?

 

[Paul Oberman]

The lease time is only one hour.

Try changing theDHCP IP address lease time to 168 hours (7 days).

Disable IPv6.

Regarding:

"The wifi was reset yesterday to generate an IP address of 192.168.0.1 BUT this morning it has changed itself to 192.168.7.1

What, where, and how was the wifi reset done?

I did a hard reset with a paper clip and set the system back up from scratch, via the ios app.

Not sure how I am going to make those changes from the app, as I still can't log on with the ip address in a browser.

 

[Ralston18]

When you attempt to log into the router using the browser what IP addresses have you been trying?

When you make the next attempt, capture a screen shot and post the screenshot (or a photograph) if ncessary) via imgur (www.imgur.com).

According to the posted "ipconfig" the default gateway for your network is 192.168.7.1 and all of the devices that you listed appear to be in the 192.168.7.100 to 192.168.7.200 range.

The Alexa Dot must be configured to join the network via a DHCP IP address request to the router (192.168.7.1, Subnet 255.255.255.0) and once configured so should receive an IP address within the range listed above.

If you, via the browser, enter 192.168.7.1 and enter the applicable login name and password then are you able to directly access the meshforce device?

Look on the back of both the Technicolor modem and the Meshforce device.

Do you see "0A-E0-AF-C1-02-B0" (MAC address) listed?

Is there also a MAC address on the Alexa Dot?

Also, for reference purposes (images and text):

https://www.mbreviews.com/meshforce-m7-review/

The connectivity that you are using is:

Comcast ===> ( coax,) ===> modem is a technicolor DPC3216 ---> [1 WAN/LAN Port] meshforce m7[ LAN port] ----> pc wired 192.168.7.136

Second LAN port unconnected

Plus wireless ~ > wireless network devices

If everything else is working well then the Alexa is likely misconfigured in some manner.

What has been done to configure the Alexa to your wireless network?

App and procedure?

For example:

Alexa Configuration Reference

 

[Paul Oberman]

When you attempt to log into the router using the browser what IP addresses have you been trying?

192.168.7.1

When you make the next attempt, capture a screen shot and post the screenshot (or a photograph) if ncessary) via imgur (www.imgur.com).

According to the posted "ipconfig" the default gateway for your network is 192.168.7.1 and all of the devices that you listed appear to be in the 192.168.7.100 to 192.168.7.200 range.

The Alexa Dot must be configured to join the network via a DHCP IP address request to the router (192.168.7.1, Subnet 255.255.255.0) and once configured so should receive an IP address within the range listed above.

If you, via the browser, enter 192.168.7.1 and enter the applicable login name and password then are you able to directly access the meshforce device?
_
This site can’t be reached
192.168.7.100 took too long to respond.


Try:

• Checking the connection
• Checking the proxy and the firewall
• Running Windows Network Diagnostics

ERR_CONNECTION_TIMED_OUT
__


Look on the back of both the Technicolor modem and the Meshforce device.

Do you see "0A-E0-AF-C1-02-B0" (MAC address) listed?

MAC address on technicolor does not match that
Don't see a MAC address on the meshforce, but I can't unplug all the cables right now
Is there also a MAC address on the Alexa Dot?
No

Also, for reference purposes (images and text):

https://www.mbreviews.com/meshforce-m7-review/

The connectivity that you are using is:

Comcast ===> ( coax,) ===> modem is a technicolor DPC3216 ---> [1 WAN/LAN Port] meshforce m7[ LAN port] ----> pc wired 192.168.7.136

Second LAN port unconnected
Yes
Plus wireless ~ > wireless network devices

If everything else is working well then the Alexa is likely misconfigured in some manner.
I wish I could manually configure the ip address, but there is no manual way to change the network settings in the dot.

What has been done to configure the Alexa to your wireless network?

App and procedure?
Standard "add a device" proceedure. It does try to use the saved wifi, even when you do a hard reset on the dot. The hard reset is the only way to get the dot to go all the way through the setup. At the end the gen 4 unit says it is not connected to a network, which is what the gen 2 unit in the livingroom was doing. I have left it on , the same as the gen 2 device, to see if it eventually figures it out

There doesn't seem to be an option to do a manual ip address

For example:

Alexa Configuration Reference

 

[Ralston18]

You have a working wireless network that should be based on the router at 192.168.7.1 as the DHCP router.

You have, as part of that network, a set of working mesh devices serving multiple wireless devices.

You have an Alexa Dot that is unable to connect to anything because it is not configured to do so. Likely the default/current configuration is not what it needs to be.

= = = =

This Meshforce system?

https://the-gadgeteer.com/2021/01/2...ifi-system-review-get-wifi-to-all-the-places/

FYI:

https://ask.imeshforce.com/en/articles/2476316-how-to-change-the-lan-ip-address-for-the-mesh-system

(Reference only - just for explanation purposes.)

Are you using the Meshforce app to manage the Meshforce system?

If all other devices are working well except that for the Alexa Dot(s) being unable to connect then the issue is with the Alexa.

= = = =

192.168.7.100? Typo? Router is 192.168.7.1 per ipconfig /all.

How did you obtain the list of IP addresses shown in Post #9? Did you run "arp -a" via the Command Prompt?

The second device listed is "unknown 192.167.7.184 " (My underline - I would expect 192.168.7.184 - typo? Did you retype the list?

What is #9 "amazon 192.168.7.200 (2.4ghz) "?

Can you ping that device? Try doing so with the Alexa powered on and then powered off. However, being DHCP the IP address could change.....

[ Note: You can copy and paste from the Command Prompt without needing to retype everything.]

Those "unknown" devices need to be identifed. "arp -a" via the Command Prompt will list the device IP addresses and the devices's MAC. IP addresses (DHCP) can and will change. The MAC's should not. There should be a MAC on the bottom of each Meshforce unit - note the photographs in the Gadgeteer link. You should not need to unplug anything to read the MACs.

Microsoft Reference:

https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/arp

= = = =

Do you have the Alexa App?

https://www.lifewire.com/setup-mode-echo-dot-5183932

https://www.asurion.com/connect/tech-tips/fix-alexa-not-connecting-to-internet/

Key is to discover the IP address that the Alexa Dot(s) are currently configured to use. Then use that information to configure/reconfigure the dot to your wireless network.

Here is a link that may help discover more about the dot:

https://blog.privadovpn.com/alexa-i...at can access,ISP (internet service provider).

Read the text etc. and avoid the clicks and links.

Goal being to get the Alexa to work without disturbing anything else.