This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Real time scanning creates save bar when using FQDN for Synology NAS but does not for IP connection

I have a weird occurrence, I have a Synology NAS on the network, when I save a office file to it and the network share is connected with the FQDN a save bar appears and it takes 1 to 10 seconds relative to the size of the file. However if I connect the share via IP address this does not happen, I have been trouble shooting various things to figure out why this does this, in my testing I have narrowed it down to file scanning in Sophos endpoint, basically if it is enabled and I am connected via the FQDN I get the save bar and the delay, if it is IP the save happens instantly, I should note that these are 200 KB to 400 KB files & I can transfer files between the NAS and my test computer at 100 mpbs.

Any ideas why file scanning would make a difference with FQDN vs IP?

This thread was automatically locked due to age.

Parents

0 bad robot over 5 years ago

I have made a case with support I will post the response here when we get a solution.
Cancel
Vote Up 0 Vote Down

Cancel
0 Gowtham Mani over 5 years ago in reply to bad robot

Hi bad robot

Can you please PM the case number that you currently have open with our support? I will look into it and check if I can provide any additional details here.

Regards,

Gowtham Mani
Community Support Engineer | Sophos Technical Support
Knowledge Base | @SophosSupport | Sign up for SMS Alerts
If a post solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel
0 bad robot over 5 years ago in reply to Gowtham Mani

#8578881

We have been able to determine this has something to do with remote scanning, however what I cannot figure out is why that would matter for a FQDN vs IP. Basically if you turn off remote scanning the issue goes away, however with remote scanning on and using direct IP the issue is also not there. It is a little confusing at this point but any help would be great.

Thanks,
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 bad robot over 5 years ago in reply to Gowtham Mani

#8578881

We have been able to determine this has something to do with remote scanning, however what I cannot figure out is why that would matter for a FQDN vs IP. Basically if you turn off remote scanning the issue goes away, however with remote scanning on and using direct IP the issue is also not there. It is a little confusing at this point but any help would be great.

Thanks,
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data