Thanks for any help in advance.
Posting here because I can find very little info through our friend google.
I have recently gotten the D'link 3782, (previously had the hg635).
In short:
Reproducable problem is that I am having to turn off the firewall on the router and restart both printer and PC to be able to print.
In depth:
After changing over routers I was unable to print using a printer that was on the network via wifi. (I assumed this was some issue with the PC) so spent quite a few hours, uninstalling - reinstalling running the HP support software etc etc.. The reason I repeated these steps so long is because HP software could sometimes see the printer but not communicate with it. (windows just always said offline). Tried turning off PC firewall, changing device sharing settings etc..
I had also noticed that netflix/amazon fire on my TV were slower loading menus and stuttering on films. So assumed that it was trouble with the wifi connection itself, also the printer would occasionally give a 169.254.xxx.xxx address indicating DHCP problems - again possibly pointing to trouble communicating with the router, so went through the routine of changing routers position, trying everything again, change position try again etc etc.
Anyway the upshot is. I finally as the last step disabled the router's firewall. Luckily i was trying to print with both my phone and PC. As my PC hadn't found the printer. I nearly gave up. however my phone did!
Turn off the firewall on the router.
Turn off printer.
Shut down PC. (scanning for device etc just wont find the printer with windows grr)
start printer wait till its connected.
restart PC.
Print (yay).
As mentioned the same issue with printing via phone, however restart of phone not needed, just printer. (+1 for android there)
So temp fix aside, this is abnormal behaviour, does anyone know of a better fix? is there a patch/firmware update - or will there be? (cant find date of most recent software update on the router however the copyright is 2015 and that usually gets updated with most firmware updates). Is this a known issue or am I alone in this?