Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Goonface]

Hi all,

I've run out of ideas and options for support and I've lost a lot of hair over these products.

I have 2 x twin packs of D-LINK Covr 2202, making that 4 (obviously!). I get routine messages on some devices saying "Connected, no internet" to specific nodes. The nodes stay white so the icons are not signalling a problem - so what on earth can it be?! Here's my set up:

1. All nodes are on latest firmware 1.05. I've factory reset a million times too!
2. I have set up one COVR-2202 Point A, directly connected to the router WAN. On it's own, I get internet no problem.
3. I boot up the corresponding COVR-2202 Point B (the relevant slave) and position it (without an ethernet backhaul) in the house. With these two in place, I get internet no problem.
4. I then "Add new device" in the Android App, boot up the other COVR-2202 Point A from the second pack, plug in the network cable and connect to the master Point A (which is connected to the internet) and perform the sync as per the steps in the D-Link App. The white LED appears on the new Point A, the app says success. I power down and position in the middle of the house. I get internet only part of the time, but for large parts I get "Connected. No Internet" when a device is connected to this new Point A node. I have to switch it off and back on and I get internet for around 5-10 mins before it loses it once again - it's then a repeat turn on and off again scenario.
5. I then "Add new device" to repeat the same steps for the corresponding Slave Covr-2202 node from the second pack and the suffers the exact same fate as the Point-A from this pack does.
6. If I go to the original Covr-2202 slave node, which corresponds to the working Master Point A that is connected to the router, it works fine. It's just these new additional nodes cannot keep a solid internet connection, despite the White LEDs being solid and always on.

To me, it looks like there's a fundamental communication issue between the added nodes on to the Mesh and I cannot solve it. I've tried to flip around which Point A is connected directly to the router and followed similar steps to the above. I've factory reset I don't know how many times. I've contacted D-Link with zero reply. I am close to rage rooming on these devices.

Ohh and the usual cliche - I work in IT so logically step through trying to solve the issues as you might expect - but this may be a PICNIC error I simply cannot see!

Anyone got any tips/thoughts/steps to get these working and has anyone suffered the same problem but fixed it?

Kr,
Goon

[FurryNutz]

Link>Welcome!

• What region are you located?

Internet Service Provider and Modem Configurations

• What ISP Service do you have? Cable or DSL?
• What ISP Modem Mfr. and model # do you have?

Please update the B point first then A point lastly to v1.06:
http://forums.dlink.com/index.php?topic=75828.0

Factory reset then setup from scratch...

When normally placed, what is the distance between the A and B point?
30 feet is recommended distance to begin with. No closer then that for normal operation distances.

[plabrevo]

I cant pretend anything since I own only two COVR so far, but considering purchasing another set.

- Did you try with connecting the second A with WIFI, instead of having it connected to the LAN?
- What if you plug the second B before the second A? Would you get 3 nodes successfully working?

[FurryNutz]

Any updates on this?

Hi all,

I've run out of ideas and options for support and I've lost a lot of hair over these products.

I have 2 x twin packs of D-LINK Covr 2202, making that 4 (obviously!). I get routine messages on some devices saying "Connected, no internet" to specific nodes. The nodes stay white so the icons are not signalling a problem - so what on earth can it be?! Here's my set up:

1. All nodes are on latest firmware 1.05. I've factory reset a million times too!
2. I have set up one COVR-2202 Point A, directly connected to the router WAN. On it's own, I get internet no problem.
3. I boot up the corresponding COVR-2202 Point B (the relevant slave) and position it (without an ethernet backhaul) in the house. With these two in place, I get internet no problem.
4. I then "Add new device" in the Android App, boot up the other COVR-2202 Point A from the second pack, plug in the network cable and connect to the master Point A (which is connected to the internet) and perform the sync as per the steps in the D-Link App. The white LED appears on the new Point A, the app says success. I power down and position in the middle of the house. I get internet only part of the time, but for large parts I get "Connected. No Internet" when a device is connected to this new Point A node. I have to switch it off and back on and I get internet for around 5-10 mins before it loses it once again - it's then a repeat turn on and off again scenario.
5. I then "Add new device" to repeat the same steps for the corresponding Slave Covr-2202 node from the second pack and the suffers the exact same fate as the Point-A from this pack does.
6. If I go to the original Covr-2202 slave node, which corresponds to the working Master Point A that is connected to the router, it works fine. It's just these new additional nodes cannot keep a solid internet connection, despite the White LEDs being solid and always on.

To me, it looks like there's a fundamental communication issue between the added nodes on to the Mesh and I cannot solve it. I've tried to flip around which Point A is connected directly to the router and followed similar steps to the above. I've factory reset I don't know how many times. I've contacted D-Link with zero reply. I am close to rage rooming on these devices.

Ohh and the usual cliche - I work in IT so logically step through trying to solve the issues as you might expect - but this may be a PICNIC error I simply cannot see!

Anyone got any tips/thoughts/steps to get these working and has anyone suffered the same problem but fixed it?

Kr,
Goon

[contrarytriangle]

For anyone else reading this, the COVR has a compatibility issue with green ethernet switches. I had to jank a whole bunch of Trendnet green switches out (best seller on Amazon)

Second tip, enable guest wifi and toss in a good password in there to avoid the problem of a surprise OPEN FREE WIFI for all your neighbors.

[FurryNutz]

Ya seems to be a known issue with MESH systems.
D-Link DGS-105/108 and HP ProCurve 1400/1800 series switches work for COVR systems.

[Amzo]

I just bought a second pair of D-Link covr-2022. Set them all up like yourself and found the new pair were on 1.04 and had the upgrade to 1.05 available. Only updated the new pair point B and not the New pair point A (now a point D) and all seems to be performing well with New Point A (D) connected to a PC in another room and with Wifi - no dropouts. So all units on 1.05 except new additional point A (cofigured as point D) which is still on v1.04.

[FurryNutz]

You should be able to connect to the D Points web page and update FW directly to it's web page.
Also there if v1.06 which is more recent and works well.
http://forums.dlink.com/index.php?topic=75828.0

I just bought a second pair of D-Link covr-2022. Set them all up like yourself and found the new pair were on 1.04 and had the upgrade to 1.05 available. Only updated the new pair point B and not the New pair point A (now a point D) and all seems to be performing well with New Point A (D) connected to a PC in another room and with Wifi - no dropouts. So all units on 1.05 except new additional point A (cofigured as point D) which is still on v1.04.

[Amzo]

Updated point D (second pair point A) to v1.06 and all working ok. Thanks! 30mins later after checking, I upgraded points B, C also to v1.06B03. All ok so far. Shall I leave off upgrade on original Point A?

[FurryNutz]

ALL Points should be updated to same version. Updating the A Point lastly.

[Amzo]

Thanks updated original Point A. However, its seems the Point A from the new set (now point D) is giving speed test results as 25% of what it was and upload is at 75% of what it was? I turned off point C that was working as it should be and swapped with the point D (new pair point A) and same results. Any suggestions? Could be a faulty device but was getting faster speed test results previously? Should I remove the device from the mesh and reset up? Was noticing DHCP issues previously though before update (iphone connected but no internet until I renewed lease on the phone) with the 4th device in mesh which seems to be resolved in this update...still monitoring that though

Update

So equipment was
1A
1B
2A
2B

All points are on latest 1.06 after point 1A was updated I then reset and added Point 2A first, all ok, then Point 2B all ok. Then Point 1B and the point 1B is running at 25% of normal download speed and upload of 75% when tested. Something is not right when you go to more than 3 mesh devices?

swapped things around and 1A,1B and 2A work fine together. Please note - the 4th I am adding that always goes into the deprecated output (I have tried moving devices around in links) is one that is connected in the mesh diagram as working through one of the other points (not connected directly to point A)... It should however still pipe whatever speed is at the point it is placed that that the node it is connected to gives in that area though right? Think this is similar to the point mentioned inthe Topic: COVR-2202 - BETA Firmware 1.06B03

Re: COVR-2202 - BETA Firmware 1.06B03
« Reply #5 on: September 04, 2020, 12:16:21 PM »

[FurryNutz]

What happens if you don't use the 4th Point?
Just run with 3 points...

[Amzo]

Seems to be ok so far (speedtests show as expected) - Points 1A, 1B and 2A... Will try to rig up 2B tomorrow in an area where Point 1a shows in mesh as direct connections to 1B and 2A and 2B. I think the issue may lie in node daisy chains if you know what I mean.....

[FurryNutz]

And what you might do as well to test the 4th Point out, swap it in place with one of the other Points, then test again.

[Amzo]

Tried this after everything was running fine for hours. 4th added and had problems again with one of the devices at random having 25-30% speedtest result. Dropped back to 3 with one point swapped with the 4th device. All ok. 2 node in Daisy chain is not the issue as when I had all 4 connected 2 in chain worked fine but the one connected to point A had the issue (Was one point unchanged from the working 3 config). Looks like it cant handle 4 devices in the mesh. All on 1.06B03.... Will have to stick with the 3 until some fix can be found. Can exclude Point A of new pair being the issue I guess.