server accessible from different networks

[xbkuba]

Hey guys,

 

I'm thinking about this for some time but my networking skills aren't that good. Is there a way to make the server (10.0.0.5) accessible both from the 192.168.0.0 and 10.0.0.0 network?

The server is used as a media and storage server. Will I have to remake the A class into C class, which I take only as the last option here, or is there some other way?

I've heard about static routing could that help? Or is it impossible?

Both networks use 255.255.255.0 mask

 

I know that the setup looks really stupid pls dont judge

[Radium_Angel]

10 minutes ago, xbkuba said:

impossible?

Why do you have 2 different networks to begin with?

[Snipergod87]

If if routers are capable of multiple vlans or adding routing tables than yes if you assign the vlans or routing tables (99% of consumer gear cannot do this). but why do you have two seperate class C blocks?

[Lurick]

A static route on the main router on the 192.168.0.0 network pointing to 10.0.0.1 for the 10.0.0.0/24 (or whatever subnet mask you're using for that network) will work just fine but, as others have mentioned, why are you splitting it that way?

[xbkuba]

It wasnt me who decided to split it, I got it that way, but it was because there are 2 different user groups and only one ISP connection so someone split it into two separated networks, but now they want shared server but they dont really like the idea of merging it but I guess I will have to talk them into it.

[Tzomb1e]

Ultimately, subnetting would have been beneficial here.  Instead of 192.168.0.0/24 and 10.0.0.0/24, it would have been cleaner to use something like 192.168.0.0/25, 192.168.0.128/25 depending on the amount of hosts needed anyway.  If you need a full class C for each floor, then 192.168.0.0/24 and 192.168.1.0/24.  You can still use your current addressing of course...it is just messy :D.  Assuming the VLANs are already present, all you should need is a static route on the primary router telling it where to send the traffic.