Search results

Final resolution.... I bit the bullet and purchased a separate router. Now all clients are either assigned a static IP address or connect to the new separate router. Everything is working well but I'm a little "ticked" at my ISP (Rogers) that has caused me to spend money on a router. Thank you...

Yes. It seems that is my only option.

I haven't posted the entire length of the chronology of my problem solving so as not to bore everyone. Both my PCs are direct wired with Cat5e cables. They were using the auto-configuration process of the DHCP and occasionally getting a 169.254.x.x IP address. After I assigned them static IP...

I found my Amazon Echo IP address by getting it's MAC address from the Amazon Echo settings, then looking at the connected devices on the Router to find the IP address associated with that MAC address.

I may be getting out of my depth here too. (I'm not fully knowledgeable about a wireless site survey). However, given the little that I do know, her are my thoughts... I have a number of LAN clients hardwired and they occasionally got a 169.254.x.x assignment. Because of this, I deduced that...

Yes. I can run the Hitron as a modem. If a DHCP reservation will encounter the same problem as allowing the DHCP to assign IP addresses, it looks like that's what I'll have to do. I do have the static IP assignments outside the range available to the DHCP.

Sorry for the confusion. I'm far from an expert in this area. I have just enough knowledge to get myself in trouble. Here's what I mean.... Any client for which I have assigned a static IP address works perfectly. i.e. It never gets a failure because of a 169.254.x.x address. By "autoconfig IP...

Thank you for the responses. Sorry for the long post but I don't want to waste anyone's time because I don't provide enough information. First, I have multiple wired and WiFi clients on my network. I have assigned static IP addresses to all wired and WiFi clients other than the Echo and Hub)...

I have a Hitron CODA 4582 modem and am having trouble with autconfiguration DHCP assignments. (About once or twice a week the Hitron will not assign a proper IP address to it's clients. Instead it assigns a 169.x.x.x address. A modem reset temporarily resolves the issue.) I have beat this issue...