I was having a terrible time with a new Canon ELPH 350. The Camera has a WiFi connect feature that allows connection from camera through a Wireless Network with a specified SSID to a specified PC on the network. I found that in order to connect I had to completely un-install the software from the PC, re-install, make one single successful connection, optionally transfer new picture files. The next attempt to re-connect would fail, so, repeat the process of software un-install/re-install. Odd thing, I noted that I was actually able to ping from the PC to the camera. This was while using the ISP supplied Arris brand, model SBG6580 WiFi cable router. Just for the heck of it, I tried my idle D-Link DIR-628 as the WiFi device, not even connected to WAN. It worked like a charm without any software change at all. I do not currently have the Admin password for the ISP router.
(1) Does anyone have an explanation for why a WiFi router might cause connection problems? Nice that D-Link is problem free, but I am very curious.
The next thing I did was plug DIR-628 WAN port into a LAN port in the SBG6580. This, of course, is double NATing. All function worked as expected. I could switch SSID's at will. There was a D-Link Wireless shutdown problem that I will not go into, that obliged me to repeatedly switch SSID's. Along the way I was trying to connect to the D-link-628's Remote Admin function. I had previously used this particular router in this way successfully connected to broadband modems. I identified that the connect problem with Remote Admin on the DIR-628 would go away if I configured Remote Admin (accessed from the LAN side) to not use HTTPS. Un-encrypted connection to port 8080 works fine from the WAN side of the DIR-628. I suspect that the HTTPS shuts down if the WAN side is on a Private Network. (In this case 192.168.0.x) .
(2) Can anyone verify my thinking on the problem with Remote Admin using HTTPS on a Private Network?