2 problems
-
[quote=“Sk00t3r, post: 2070, member: 430”]Monday Blues BUMP still trying to figure out these two issues. Any advice would be much appreciated. Thank you![/quote]
Please try this for the hostname issue - try editing /etc/resolv.conf. At the end of the resolv.conf file (after the nameserver
entries), add the following (substituting your actual domain name—fully
qualified):search yourdomain.name
Save the file, then your FOG server should be able to resolve the hostnames.
I’m not sure on your ClamAV issue, I’ve never run into any issues with it. Hope you resolve your issues.
-
Hi, and thank you for the reply. I have this set in my resolv.conf. It works fine with XP machines (as long as port UDP 7 is open and ICMP is allowed). It’s only with W7 and the firewall turned on I get this issue. I can even enable the firewall to allow every port every program 100% access and it still does not work. There must be something W7 firewall blocks that I am missing.?.? Thank you.
-
Hello,
I have this exact same issue with my Windows 7 machines. I have not tried this with XP, but I can verify that with Windows 7 firewall turned on with all traffic allowed I have the same problem. With the windows 7 firewall turned off, the issue goes away.
Puzzling.
-
How about disabling windows defender, does that affect it?
I suspect the Av issue is a 64bit issue I get the same result with my 64bit server.
-
did you disable the windows firewall using group policy? Is the firewall service stopped?
Double check to make sure —> gpedit.msc —> Computer Configuration —> Windows Settings —> Security Settings —> Windows Firewall and Advanced Security —> Windows Firewall Properties (1/2 way down the page). Verify that Domain / Private / Public profiles are all set to disabled.
Then go to services.msc and stop / veriy that the windows firewall is also set to disabled / manual.
We ran into this issue on our end with windows 7, and even though we had the firewall off and disabled via group policy our Windows update server kept turning it on when a service update / service pack was sent out (SP1 for win 7). Big pain in the @#$@#$ .
Hope this helps.
-
Just a thought, I have a feeling that if you disable IPv6 on the Win7 clients all will work just fine.
-
I will try disabling IPv6, as for disabling the firewall this is not an option on production computers. I only disabled it for trouble shooting purposes. Thanks for all the input will try and report back my finding. Thanks again.
-
Okay, well I got around to trying a few more things. Still no luck. IPV6 is disabled on the adapter and still the same results occur. Anyone have this working with W7 and the firewall enabled? Thank you all.
-
Did you install Clam AV before fog? I do not think it is bundled with FOG.
Your photo shows this message
“Lib Clam AV Error: cli_loaddb(): No Supported database for Clamav” - does it show a location? like usr/local/share/clamav???If it does, is that the correct location you installed Clam?
Do you have a MySQL database for clam?
I do not have Clam on my system, but I assume that when it gets installed, it creates a DB for it. -
I am having the same issue with the firewall on Windows 7. Making exceptions do nothing. I will keep tinkering with it but so far it’s driving me nuts :mad:
-
So to confirm, if you have the firewall disabled they ping and show up correctly… ? yes?
-
That is correct, but it appears that there is currently no known way to make it work without completely disabling windows firewall… bummer…
-
As stated before, the current version of the client software was built around Windows XP, and hasn’t been rebuilt or optimized for NT6. Things such as UAC, printer management, etc do throw it off from time to time.
If a C+ / C Sharp dev wants to donate some time to make the software play a bit nicer that would be awesome.
In it’s current form the client software is functional, just not robust.
-
I’ve setup 3 Fog 0.32 servers, and it installs clamav during the Ubuntu instal for Fog (at least it says it does). I have 3 Fog servers that all give the same error when trying to run the virus scan, “no supported database found”. I think it’s a glitch and I haven’t invested the time to fix it.
-
ok. I got clamav to work on my Fog 0.32 server. It might have been easier to get healthcare reform legislation passed in the US, but it’s done.
I had to add the PPA package source to apt, remove the old clamav on the server, install the new one from PPA. Expand the init.gz that fog uses, update the hosts and freshclam.conf files, and make symbolic links to the virus databases in the root of my web server. If anyone wants specifics, I’ll explain, but it’s quitting time and my butt hurts from working on this for 4 hours.
-
Nice, as a Linux/Fog n00b I would love some step-by-step / specifics if you have the time. If not that’s okay too, I’m sure I’ll figure it out from the post above. Thanks again.
-
I’ll wiki it and post when it’s done.
-
I’m in the same boat as Sk00t3r. I’ve been trying to hammer my way through making a FOG server, but as this is the first time I’ve ever used Linux, it’s been creating some problems for me. I have the majority of the server up and running with a master image, but getting ClamAV to work is still escaping me. Any luck with that wiki? I would really appreciate taking a look at what you have to say about it.
-
I started to edit the clamav wiki article, but it wasn’t flowing right so I am trying to figure it out. Too busy with end of the school year stuff at the moment, but be patient and I’ll have some specifics up near the end of May/beginning of June
-
No worries! I appreciate the help, and I look forward to seeing that article from you.