MRT-Man
100+ Head-Fier
- Joined
- May 24, 2005
- Posts
- 458
- Likes
- 1,528
Seems like AKM (dac supplier) is finally resuming volume production in Q3 of this year…Any rumor about a SP3000 ? May be to be anounced at Munich's High End in May ?
Seems like AKM (dac supplier) is finally resuming volume production in Q3 of this year…Any rumor about a SP3000 ? May be to be anounced at Munich's High End in May ?
Same, I also had the orbi.I have ongoing issues connecting my SP2000 with my Orbi Netgear. it takes a few mins of toggling the wifi on/off on the SP2000 before it will connect. I am using Static IP instead of DHCP and that doesn't seem to help either. the SP2000 is the only device I have at home that just won't play nice with my home wifi network. it does connect almost instantly when I take it out of the house to my dealer's place and other places where there's wifi. so that was how I knew I was only having issues with my own home wifi network.
I have ongoing issues connecting my SP2000 with my Orbi Netgear. it takes a few mins of toggling the wifi on/off on the SP2000 before it will connect. I am using Static IP instead of DHCP and that doesn't seem to help either. the SP2000 is the only device I have at home that just won't play nice with my home wifi network. it does connect almost instantly when I take it out of the house to my dealer's place and other places where there's wifi. so that was how I knew I was only having issues with my own home wifi network.
Mesh networks like the Orbi can cause a number of issues with older devices. newer stuff has less of an issue. I have a Netgear wifi router -not the orbi. I took my old Netgear wifi router and turned it into an "access point" type device to increase the size of my wifi-network. this is a supported net gear configuration. causes havoc with my control 4 tablet. although the tablet is new the controller is older (2016). the readers digest issue is the assigning of ports on a mesh slave is not necessarily the port that it gets on the master wifi device. This is very hard to see even when looking at connections via the Netgear configuration program. I don't do much streaming, but do use wifi for updates. will run some tests and see if I can find a couple of workarounds with static ip's and blocking ip's on my access point.Same, I also had the orbi.
Was able to run a few tests last night and was not able to create an issue where I could not connect and maintain the connection. Keep in mind I am not on an Orbi. Considering the Orbi is a relatively new device from Netgear it may be worth checking to see that you have the latest firmware on the Orbi.Mesh networks like the Orbi can cause a number of issues with older devices. newer stuff has less of an issue. I have a Netgear wifi router -not the orbi. I took my old Netgear wifi router and turned it into an "access point" type device to increase the size of my wifi-network. this is a supported net gear configuration. causes havoc with my control 4 tablet. although the tablet is new the controller is older (2016). the readers digest issue is the assigning of ports on a mesh slave is not necessarily the port that it gets on the master wifi device. This is very hard to see even when looking at connections via the Netgear configuration program. I don't do much streaming, but do use wifi for updates. will run some tests and see if I can find a couple of workarounds with static ip's and blocking ip's on my access point.
Have you tried Automatic DHCP not a static? if you have to use a static can you set the static to a higher number? IP's tend to get assigned to devices in sequence-ish. so low numbers like 192.168.1.10 will be used before 192.168.1.50. you might have a device that is trying to step on your static IP like a phone or tablet. I get this with my NAS that is set to 17. I have to make sure that it is running before I do a router update or something else will grab that IP. because I have home control I have 60 or so devices fighting for ports.I can confirm my Orbi is using the latest firmware. Since the time I’ve owned the SP2000, I’ve updated the firmware for the Orbi at least twice so I’m pretty sure that at least in my personal case, the firmware is not a problem.
You can avoid that by making a DHCP reservation on your routers DHCP server. That way, your NAS will always get the same IP address from the router and it won't get assigned to another device instead.Have you tried Automatic DHCP not a static? if you have to use a static can you set the static to a higher number? IP's tend to get assigned to devices in sequence-ish. so low numbers like 192.168.1.10 will be used before 192.168.1.50. you might have a device that is trying to step on your static IP like a phone or tablet. I get this with my NAS that is set to 17. I have to make sure that it is running before I do a router update or something else will grab that IP. because I have home control I have 60 or so devices fighting for ports.
I can confirm my Orbi is using the latest firmware. Since the time I’ve owned the SP2000, I’ve updated the firmware for the Orbi at least twice so I’m pretty sure that at least in my personal case, the firmware is not a problem.