NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Bad Embedded Web Server
Have multiple NETGEAR WiFi routers in office. Prefer to use the office DNS to access them for obvious reasons (e.g., 'PetersWifi' instead of trying to remember IPv4/6 internal addresses like '192.168...
Netgear have fixed this in the webserver firmware! I tested the beta, it works; look forward to release.
ugh. I uploaded imaes of the NSLOOKUPS, the successful web page from R6300v2.xxxx.local, the failure or web page R7800.xxxx.local, and the successful webpage using the IP for R7800.xxxx.local (192.168.254.24). Do you know how to get the pics in my post to show to people who are not logged in as me?
Any images posted have to approved by a mod first. Anyway, I would give the r7800 a static ip then see if it resolves by hostname.
EDIT: can see your images now.
Tried that. This has nothing to do with name resolution, apparently. It actually seems to return a DIFFERENT bad page based on the characters in the name. This is getting scary (buffer overrun in host header -> memory overwrite?)
EDIT: It also returns a DIFFERENT bad page if you use FQDN (which returns '0707n%' and not '0')!
Further note: You will get the '404 -- This server does not support...' error if you do not supply the page (default document, e.g., 'http://R7800.xxx.local'). You get the random characters if you supply the page (e.g., 'http://R7800.xxx.local/index.htm')
Netgear have fixed this in the webserver firmware! I tested the beta, it works; look forward to release.