StuC thanks for yout contunied help! If i dont put any manual static routes in PC in Site A tracert 192.168.2.50 (ip of a computer) tried to go out through the router and hits the internet so fails! On the same PC if i put a static route like this:

route add 192.168.2.0 mask 255.255.255.0 192.168.10.254

Still does the same thats why i think it must be something on the netgears I need to change so when it gets a request for 192.168.2.50 or whatever it passes it through its VPN not external interface hense dont think making any change on the server will help as its not coming into the equation

OK well that's pretty clear and you could be right on the Netgears.

Was going to set up a test link here but didn't see what type you are using PPTP or IPSEC etc. Not sure if I can get IPSEC going without wiping my old home Vigor 2800.

I use some Linksys RV042 at a few sites and I know they handle it OK over IPSEC.

They are using IPSec VPN's

Edited because I got my remote desktops mixed up ---

OK try on the remote office routers IPSEC add the extra subnet details on the "More" button under the TCP/IP Network Settings.

Just set one up here IPSEC Vigor-Vigor and adding that lets the packets route over the VPN. I can't test it further because we don't have other VPN's stared out from that Vigor.

The Mainsite has the 2820 yeah? do it on that one?

no I messed up, on the remote sites (both) if you can, if the Netgear offers it.

What I did was create the link then send some packets to an address I know is linked to the remote vigor.
"tracert" sees the packets go to internet UNTIL I tell the router (local) that the VPN handles that IP range as well.

I did download the Netgear manual but at work.