| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 91351 | 2008-07-04 00:07:00 | NOD32 on SBS2000 | hcl (10925) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 685091 | 2008-07-08 01:26:00 | Obvious thing to check would be your port blocking, as POP uses a different one to SMTP (25 as opposed to 110) | nofam (9009) | ||
| 685092 | 2008-07-08 01:28:00 | How did you configure ISA on the SBS2000 server? | SolMiester (139) | ||
| 685093 | 2008-07-08 01:28:00 | If you are installing NOD32 on a server are you following the recommended config for a server? i.e. DO NOT install IMON - Disable scanning of certain Windows system files - Disable scanning of the Exchange folder etc Also how are the workstations getting their updates? Normally the server would get the updates from NOD32 server then host them locally for the workstations. So the workstations don't even need internet access to get the NOD32 updates from the SBS box. |
CYaBro (73) | ||
| 685094 | 2008-07-08 03:14:00 | Also how are the workstations getting their updates? Normally the server would get the updates from NOD32 server then host them locally for the workstations. That's an interesting point - the server should be issuing out the updates - might sound silly, but have you tried turning the proxy setting off, and trying like that - if the workstations are updating then it appears they are not going through the server. Also - no firewall stopping it ?? Also just reading more on Esets site - "If you use a proxy server, click on the Detect button to check for one" I was just speaking to one of the tech guys at chillisoft,( NZ distributor) about another matter - and mentioned this- according to him the only thing that would normally stop it is incorrect proxy settings ( if using a proxy) |
wainuitech (129) | ||
| 685095 | 2008-07-14 03:30:00 | That's an interesting point - the server should be issuing out the updates - might sound silly, but have you tried turning the proxy setting off, and trying like that - if the workstations are updating then it appears they are not going through the server. Also - no firewall stopping it ?? Also just reading more on Esets site - "If you use a proxy server, click on the Detect button to check for one" I was just speaking to one of the tech guys at chillisoft,( NZ distributor) about another matter - and mentioned this- according to him the only thing that would normally stop it is incorrect proxy settings ( if using a proxy) I talked to chillisoft about it too, and they couldn't think of anything that could be causing it. It doesn't work with or without proxy settings. It didn't work with the usual setup (proxy details entered, no username & password entered, connect to LAN as system account) so I tried entering domainname\administrator & password & tried all the different connect to LAN options - nothing worked. The workstations are updating directly from Eset. I'm sure it must be the proxy, but I've got no idea how to find out exactly what is going wrong with the proxy. The router is plugged into the server & all the workstations connect to the internet through the ISA server. ISA is configured to allow the workstations internet access without authentication, but anything running on the server still requires authentication. |
hcl (10925) | ||
| 685096 | 2008-07-14 05:05:00 | Hmmm Stab in the dark - but have you tried setting the port for Nod32 (on the server) to use port 80, I'm assuming that a standard web browser will work OK. ????? | wainuitech (129) | ||
| 1 2 | |||||