Issues after router reset - can anyone offer me some guidance?

[Midnight_Voice]

I’ve been making the transition from BT to EE for broadband and EETV. It has not gone as smoothly as I might have hoped.

The relevant issue here is that after some problems with DV, I was advised to reset my router, a BT SH2, to complete the transition from BT to EE. (It had been decided earlier that I did not need a change of router).

So I did this. A little complication I have is that years ago, I stopped changing all my WiFi logins every time I got a new router, and so I knew to go into the router settings and put the ‘Netgear’ SSID and password I actually use back over the BT defaults that the reset had brought back.

After which, I tried various of my WiFi-connected devices, which all fell into one of three categories:-

1 They carried on without missing a beat;

2 They needed to be retold the ‘Netgear’ SSID, but didn’t ask for the password as well;

3 They needed to be retold the ‘Netgear’ SSID, after which they wanted the password as well.

There were a lot of 3s, and I got the impression that the smarter the device was, the more likely it was to be in this group.

And some of them wouldn’t come back at all that first evening, even though I was sure I had the password right. Though I did notice that the WiFi seemed to be hunting in and out, probably retraining after the reset. Or something.

The next day, I went round all the balky devices again, and had no trouble getting the details in, and having them connect.

But I wonder if anyone can throw any light on what was going on? Did all these devices detect the couple of minutes when the SSID they knew wasn’t present any more, and many of them couldn’t reconnect themselves when it came back?

Should I maybe have gone round the house before the rest, turning all these devices off at the mains, so they never saw their expected SSID vanish? And only turn them on again when it was back?

Or would the disruption to DHCP, when the router had to rebuild the IP table, cause the above anyway?

[Mustrum]

@Midnight_Voice   its hard to say , but were it me I would have switched the router off for a short while after changing the SSID, so when it restarted all of the devices get a chance to reconnect.

And those that did no, switch them off and back on, before trying to change settings.

HTH

[Midnight_Voice]

@Mustrum 

Thanks - I didn’t do any of those things, and I can see how they might have worked better.

[JimM11]

@Midnight_Voice Well it's a sign, just did the same on a EE Smarthub+ up 86 day's but wife was complaining looking like her wireless laptop's were slowing, did not believe so but rather than you know what, did a software restart of the router, well went to hell and a hand basket, not one 2.4ghz device would connect, normally have 5/6 at any one time, managed to get two back on so far, just need to do a whole power off/on to see if it clears it all up, all the 2.4ghz devices jumped onto my Asus RP-AX58 which surprised me no end, so they are all working just not logical.

Now have done this before, but was trying to keep the EE router up as monitoring it's performance over time as user's were complaining drop off's never had but was well slowing down web interface, but day to day did see NO issues in operation.

Plan is, power off the EE, power off the Asus, bring the EE up, watch all the devices re attach to the router, once done power the Asus up again, need 20 minutes to plan and get it all done, but will have to wait well later when all in bed to get it done.

Devices go were they want too, think that this well proves that fact but sure P's one off, know what i mean.! 

The possible problem that is underlying for me is, that an app FW upgrade kind of fixed the naming convention side, but i now have 2 identical named devices, with different mac's so not surprised the EE Router just threw it's hands up and guess what, it's the Asus in 2.4ghz that's got the wrong name, and NO way to change it.....

DHCP would think not, have all mine static IP's, but power off before that may be the key.

That Factory reset advice, have only ever done it once, as reached the impasse with SKY at the time, and i have never ever found it to clear a router suspected fault, your DV may have been a service swap BT - EE but cannot say yah/nah, i just keep away from it myself....

[JimM11]

@Midnight_Voice To keep it simple, just powered of the Asus RP-AX58, left it for 5 mins then powered it back on watched it go through it's boot up to the steady white light for up and at em status. Went had a look on the EE Web manager, and all of the 2.4Ghz devices had jumped ship back onto the EE router as i suspected that was what they would do, it's logical for them to be attached device wise there, the Asus grabbed them and boy it's for not letting them go. This is/was unusual but pretty damn sure it's the naming that's messing the whole thing up. Does not matter where they go, just the old OCD kicking in...

[Midnight_Voice]

@JimM11 

I’m guessing you don’t have EETV? Something that might not like your range extender…

So I’m just using the supplied router, and fortunately it covers the whole house.

Everything finally settled down, anyway, and the DV is currently behaving, so maybe there was something in what they asked me to do. Watch this space…..

[JimM11]

@Midnight_Voice Yes you got it, no DV dropped that as would not put up and take the chance, NO EE TV have separate control via the SAT dish to offload the network but controller is smart and can stream wherever needed.

DV just takes a few day's to settle, but as long as you are aware you can keep the eye on it, and the finger on the pulse.

Good your seeing the light at the end of the tunnel now.👍

[JimM11]

@Midnight_Voice Watching your posting with Interest, as the combined way that EE have you going.

BT Smarthub2 is a really well spec router even though i have never used, DV landline appears to de ROCK solid both EE Service wise and BT control with it.

As to features not sure what you did or how you looked/setup the router, are you Web manager based / MyBT app control, but expect to see what you come up or against in the journey.

You have seen, looked at all the post's potential issue's etc with using a EE Smarthub+ so you do have the better setup currently as far as i would say.

[Midnight_Voice]

@JimM11 

I’ve had the router four years, since we moved in here, when I moved my existing broadband contract from our previous house. It was a bit weird there, as I had FTTP installed when it came out in our area, but BT left the landline on the old POTS system.  But when we moved here, it was strictly FTTP only, so BT gave me a digital adapter for my DECT phones. But they misbehaved a bit, saying they were engaged when they weren’t, so BT lent me a DV phone. Which, for some peculiar reason, stopped the DECT phones misbehaving.

Until recently, when I took EETV, initially from BT, and then got ported to EE. That’s been a bit of a rocky road, in various ways, but none I would ascribe to them having me stay on the BT router. Until the DECT phones started misbehaving again, but this time cutting off callers when I pressed the talk button, a more serious issue.

Hence the advice to reset the router,  and it has worked so far.

I look after the router, when needed, by typing its IP address in my browser, and working with it at that level. I don’t need any simplified toys 😛

[JimM11]

@Midnight_Voice Still all the same way then, Digital to the Router dect, and your Dect still on the DVA, pity the router throwed a wobble at the change over and that the factory reset seemed the only way to recover it all, but doo doo's do happen from time to time. Look's like you got it all well under control now.👍🤞