is the lone reason I can't connect the NAS directly to my PC due to the lack of a crossover cable? I haven't used one of those since the days my LAN parties consisted of two PCs, only one connected to the net.
I would recommend sticking with your router and not a crossover even though you only have two devices that need to talk to each other because it has a DHCP server for assigning the IP to your NAS and PC interface. With a crossover cable you'll probably have more trouble trying to make sure both sides have the IP they need to talk to each other.
what does "9 if 18" mean?
I missed the words mask & metric in there:
route -p add 0.0.0.0 mask 0.0.0.0 192.168.2.1 metric 9 if 18
route -p add 0.0.0.0 mask 0.0.0.0 192.168.2.1 metric 9 if 0x18
route -p add 0.0.0.0 mask 0.0.0.0 192.168.2.1 metric 9 if 192.168.2.20
Only one of these would get added, I just wasn't sure at the time I posted that of the syntax on how MS wants to see which interface (if). However, I just looked at help and it appears specifying the interface isn't needed and it should automatically know. So this command should do the trick without worrying about how to identify which interface.
route -p add 0.0.0.0 mask 0.0.0.0 192.168.2.1 metric 9
(of course that is if 192.168.2.1 is still the gateway to the internet. Sounds like you might have changed things up.)
From MS help for route -?:
> route ADD 126.96.36.199 MASK 255.0.0.0 188.8.131.52 METRIC 3 IF 2
destination^ ^mask ^gateway metric^ ^
If IF is not given, it tries to find the best interface for a given
Instead of running those, I think what I'm going to attempt is changing the IP of the ISP router (I do have access to it; it's a family's member's network I'm borrowing that lives close), and then just change my internal router to 192.168.2.1... like it probably should have been since the beginning.
Are you saying that you are going to or already have changed the ISP router to 192.168.1.1 and your internal router (with the NAS attached to it) to 192.168.2.1 ?
That isn't going to buy you anything unless I'm missing something here. However, you reported that things are better, so IF it seems to have fixed it, then the order in which you brought up interfaces just happened to at that time set the metrics to what you needed by chance is my guess. I'd have to see your current ROUTE PRINT to know for sure.
The ISP router is 192.168.2.1, and the router here is 192.168.1.1. In the last place (and soon, here), this router plugged into the ISP router, with the same IP addresses used.
The difference at the last place is that your PC was only directly connected to one single network, and reached all other networks via that single net. That network was your LAN with your router(gateway) also on that LAN. That router then connected to the ISP router via the WAN interface on your internal router. When your PC sends packets it knows that anything destined for 192.168.1.0/24 goes out the interface with the IP in that subnet. Anything else goes out of the default route (0.0.0.0) interface, which was the same interface.
PC <<-- 192.168.1.0/24 subnet -->> LAN router&NAS <<-- 192.168.2.0/24 subnet -->> ISP router <<-- internet -->> global destination
You now have a situation where your PC is "dual-homed" and has two different networks it can send packets out to. 192.168.1.0/24 and 192.168.2.0/24
Since it has interfaces with IPs in both subnets, it automatically correctly knows which interface to place packets on when sending to either 192.168.2.X or 192.168.1.X
However, when it wants to send a packet to say a google server at 184.108.40.206 it doesn't have a specific route in the list, so it uses the default route. There are two default routes, so whichever default route happens to have the lower metric wins.
PC <<-- 192.168.1.0/24 subnet -->> LAN router&NAS
PC <<-- 192.168.2.0/24 subnet -->> ISP router <<-- internet -->> global destination
The good situation
: If this happens to be the route that uses 192.168.2.1 (ISP router via wifi) as the gateway then 192.168.2.1 takes it from there and uses the default route it has stored in its own memory pointing to the public IP on the subnet the ISP router was assigned by the ISP. Your NAS is also reachable because your PC is on the same subnet as the NAS and therefore uses a DIFFERENT route entry that is more specific than the default route.
The bad situation
: If this happens to be the route that uses 192.168.1.1 (LAN router via wired) as the gateway then 192.168.1.1 takes it from there but it doesn't have a path to the internet so it dies. Your NAS is still reachable though because your PC is on the same subnet as the NAS and once again has a specific route.
If things are working great for you ever since swapping IP addresses there isn't really a logical reason for why that would have made things better without seeing your route print table.
I think I'll be doing my first post soon and hopefully you'll be able to give some advise on that build. Trying to build out an ESXi box with servers for studying for the CCIE voice exam. I used to keep up with PCs from the 80s all the way up to about 10 years ago but now I find how much I don't feel confident on when making decisions since I've focused on Cisco networking and haven't kept up on the latest CPU/Motherboard/RAM options.
Wow, that got long quick! Sorry for the long post.