|OK, I set this up as described above, but I found two problems:|
1. Since the new subnet is on a 1.x instead of 0.x, I could not just do an ip renew. For whatever reason, it would not find the router. The workaround was to assign a static IP in the 1.x range, and let it find the router, and then set it back to DHCP. Then it would get a new IP address and connect to the internet and network.
2. Another issue was that after a computer was successfully on the network, there were network issues. In particular, an access database which is heavily used started having many problems. The user would restart access and it would work for a few minutes and would get another network error.
I finally took the new router off the network and it all started working fine again, but of course without the URL filtering.
So what the deal? Do I need a higher quality router? The netgear only cost $40 and it really isn't meant for the use that it was put through. The router had about 20 users, and the router was the throughput device to the server where the Access database is. I think that a better setup would be the URL filter is NOT between the server and the nodes, and only on the gateway side which I think would be much less traffic.
I also have a Netgear FVS318 which I am going to try the same experiment with. Maybe it is a higher quality switch.