Compatibility problems with NOD32 Anti-Virus

July 10, 2007 — Philip Churchill

NOD32    NOD32 on a go slow!     SNAIL

It seems that some of us are having problems with NOD32 on home server. One of our contributors TheJudge found that the Nod32 AMON service is NOW blocking access to he’s shared folders, but only since the installation of the uTorrent service.

“After about a dozen different configurations, trials and reboots, I found out that the conflict does in fact involve AMON. I turned off uTorrent and stopped the service. But Amon would still block the shared folders. AMON must be completely disabled or the shares will be blocked.  I’m not
sure why, but Amon is the reason. Odd part is that Amon played well with my WHS all week until I installed the uTorrent Service and add-in.  Coincidence? Don’t think so. Would an uninstall and reinstall of NOD32 work? Not sure, but that may be the next thing I try. If not, I may have to try another AV solution. The IMON portion scans incoming HTTP ports just fine on WHS and does not cause any conflicts even with uTorrent running happily in the background.

Wonder if anyone else has had this problem? “

They did, beta tester playadru182 from the WHS forums also had problems which disappeared only after he uninstalled NOD32 as did others as well. I have spoken to ESET technical support who said that they have not tested NOD32 on Windows Home Server yet, so have no idea why this is happening. They will be testing it before WHS goes RTM but say that since home server is based on Windows Server 2003 it should work fine which naturally it isn’t, which is a shame because NOD32 is a very good anti virus product. So until this problem gets resolved what can we use in the meantime? Looking back at my previous article More Anti-Virus Software for WHS and we can see that there are still a few others that we can use on the home server that are reasonably priced like AVG Anti-Virus Network edition and F-PROT Antivirus for Windows.

And the meantime any ideas why this is happening anyone?

69.png

Posted in Other Software, Windows Home Server. 9 Comments »

Setup Static IP for Windows Home Server

July 10, 2007 — Philip Churchill

If you have installed additional applications on Windows Home Server you would have setup port forwarding which enables your router to forward ports to the server’s IP address that you specified. Whilst this would work when you initially set it up, after restarting your WHS it would most probably get a different IP address. When this happens the ports would no longer be forwarded to your server’s IP address and port forwarding would no longer work. To get around this issue there are two options we can undertake. We can either setup a static IP via the router which is known as Static DHCP or we can setup a static IP on the Windows Home Server.

Static DHCP: If your router can do it, we can tell it to reserve an IP address for your server from within DHCP.  This means entering the MAC address from the network card in the WHS, into the router and assigning it a static IP address then whenever the WHS is restarted it will always have that same address.

The MAC address can be obtained by typing IPCONFIG /ALL at a command prompt from within the Windows Home Server.

If like many routers yours does not support this feature then we need to setup a static IP on the Windows Home server instead.

Static IP on WHS: First we need to choose an IP address.

IP Address Ranges:-
192.168.0.0   192.168.255.255   
172.16.0.0   172.31.255.255   
10.0.0.0   10.255.255.255

If in the router the DHCP Server IP addresses’ are assigned 192.168.1.100 to 192.168.1.150 then we can use any IP address from 192.168.1.151 to 192.168.1.255 for the static IP address as these will still be in the subnet but not in the DHCP scope.

Within the server click Start, Run and type CMD

In the box that opens type ipconfig /all and press Enter on your keyboard. Take note of the Subnet Mask, Default Gateway and the DNS Servers.

The DNS Servers entry may not be correct as some router’s act as a proxy between the actual name DNS servers and your computer. You will know if this is the case, because the Default Gateway will list the same IP address as the DNS Servers entry. We need to have the correct DNS Servers IP addresses otherwise we will not be able to browse the web. To get this information we need to log into the router’s web interface, and look at your router’s status page. On that page you should see an entry for DNS or Name Servers. Write down these IP addresses.

Type exit in this window, then press the Enter key to close it.

One again click on Start then Control Panel, Network Connections and then Local Area Connection.

On the dialogue that opens on the General tab click Properties.

On the General tab of this new box click on Internet Protocol (TCP/IP) (make sure that you do not un-tick it) and then click Properties.

On the General tab click Use the following IP address and enter the IP address you choose earlier followed by your Subnet mask and the Default gateway.

Click the lower Use the following DNS server addresses and enter those that you wrote down earlier.

We can now OK out of all the dialogue boxes.

We now need to re-boot the Windows Home Server and that’s it job completed!

69.png

Posted in Tutorial, Windows Home Server. 24 Comments »

Speed up File Transfer to your Shared Folders

July 10, 2007 — Philip Churchill

You may notice that it can take quite a time to move/copy large amounts of data to the WHS shared folders. To speed up this file transfer process I use FastCopy from SHIROUZU Hiroaki.

FastCopy

To get the FastCopy utility to work you have to first map your shared folders to drive letters*.

Copying 9.12GB of files using copy and paste in Windows explorer took just under 37 minutes and with FastCopy the same data took just under 15 minutes. A huge difference! It has saved me many hours moving my 250GB of data to my Windows Home Server shared folders using this utility.

*Map a drive to a shared folder in Windows XP 
*How to map a network drive in Windows Vista

69.png

Posted in Other Software, Windows Home Server. 11 Comments »