2010-10-19 02:51 AM
I got below above error when i issue vscan command. Some error captured from /etc/messages
cifs domaininfo shows it is connected to the domain, I found that i can ping to the SCANSERV from admin server but cannot nslookup.
from the log it show when it first happen
Tue Sep 28 04:25:17 CST [filer1: vscan.server.fqdn.unavail:error]: CIFS: Could not determine Fully Qualified Domain Name (FQDN) of virus vcanning (vscan) server (111.222.333.83). If the vscan server is running on the Microsoft Longhorn OS, the storage system requires vscan server FQDN for authenticating itself to the vscan server.
hosts: files dns
Is it the filer could find the FQDN virus scan server that cause it is disconnected from it. But how to prove and solve it.
2010-10-19 03:13 AM
Looks like somebody messed up the DNS entry.
Try changing the /etc/hosts entry to a FQDN:
Also, have the DNS records fixed. SCANSERV should have good forward and reverse resolution...
At your service,
2012-05-01 05:45 AM
So I just fixed this issue in my customers environment and wanted to make sure no one else ran into the same thing and ran out of options. I found the following KB from McAfee https://kc.mcafee.com/corporate/index?page=content&id=KB68524
Solution 2 worked for me which was to:
Enable Network access: Let Everyone permissions apply to anonymous users
1. Click Start, Administrative Tools, Local Security Policy.
2. Expand Local Policies and click Security Options.
3. Scroll down and double-click Network access: Let Everyone permissions apply to Anonymous users
4. Click Enable, OK
5. Restart the computer
6. Check the logs to verify the issue is resolved
I am not sure if this is against anyone's security policies but as far as I read this it aligns the permissions and makes the group "Everyone" to "Anonymous".
Let me know if this helps anyone.
2014-02-20 01:57 AM
I think your "vscan.server.fqdn.unavail:error" error message kind of says it all.
We use Trend on W2K8 R2 in our environment. If you do so, too, this may be a helpful link: