Whoa, I hadn't considered that. The reason I didn't experience that issue in the previous config is that even though the ISP router was 192.168.2.1, it didn't matter to my PC because it was connected to a router with 192.168.1.1. So it just worked.

Quote:

Originally Posted by MeBe

"dude, I got nothing. But if you want to send me something destined for 192.168.1.100 I can totally do that for you with my eth switch and forwarding your L2 frame"

ROFL. Big Louis CK fan here ;-)

Quote:

Originally Posted by MeBe

Since your NAS and PC share the same subnet, they always know how to reach each other. The problem is for the times your PC thinks that same subnet is also the way it should send everything to the internet.

Here's a stupid n00b question; 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.

Out of curiosity, what does "9 if 18" mean? Is it just the span of IP addresses, such as 192.168.1.2 - 192.168.1.20?

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.

Thanks a ton for the help, I am confident this is exactly the issue. Will update soon!