Enable Jumbo Frames Causes External Hostname Problem

dsm1212 wrote:

With DynDNS the IP in use is the one assigned to your router by your ISP. Your Router is then set to port forward to your NAS. So if you do a ping jumbo frame test you want to do it to the "external" IP of your router or to the dyndns name you have assigned. Most likely your router is not set to respond to pings though so the test won't work. I am interested in your final answer though. I have one PC in my house that will not access the NAS using the dyndns name. The others work fine. I don't understand what is special about that system. It doesn't matter because it's not a laptop so it always uses the internal name, but I do wonder why it won't work. What error do you get? In my case the system does get an authentication challenge so it's reaching the NAS but after entering the password the browser stays blank. I've futzed with browser caches and what not but I just can't figure it out. I don't see where you've said exactly what error you get. Could you describe it? steve

Based on my testing no client on the LAN can access the NAS using the external hostname, if jumbo frames are enabled on the client and NAS, so this isn't isolated to a single client. The problem disappears if I run the webserver on a jumbo frame enabled spare computer instead of the NAS so there is something weird going on with the NAS.