Okay - so I'm the Mom/IT Director/MVP of the family , and so I decided that now that I'm trying to use two different Internet connections (switching from DSL to Cable eventually, but right now we have both), I would just make a policy route to route EVERYTHING from my own PC to the new Cable connection. When I do this though, I lose connection to other PCs on the wireless network - those that are hard-wired to the main switch are fine - it's just PCs on the wireless! My husband happens to be the router for a HP network printer. So his wireless card is 192.168.100.101, and he routes through to 192.0.0.2 which is the printer. I have a static route set up for the 192.0.0.0 network through him, and it works fine UNLESS I change my policy route to route out all traffic through the new cable. I'm assuming that this is because he has a different default route, but it's just perplexing. Also, if I set a policy route for ONLY HTTP/HTTPS it stops working, and I end up going out the DSL anyway.
So I guess there are two issues here:
1. Why does the http policy route just seem to "die" (as does the https, nntp, etc. - they work "sometimes" and then stop), but making a route for ANY from my PC works?
2. If I have a policy route for my PC, why do I lose the route to INTERNAL addresses - technically my PC at 192.168.100.198 shouldn't even need to DO anything to go to 192.168.100.101, but it seems like the policy route really takes over ALL routing, even internal. If I could get #1 to work, then this wouldn't be such a big issue I guess.
Any insights?
Thanks.
Danita
This thread was automatically locked due to age.
