Functionality available across various network connections
Functionality available across various network connections
Hey there, I get what you're going through. Network setup can be tricky, especially when trying to reach a server across different subnets. You're not alone—many face this kind of challenge. There are a few approaches you could try: static routing might help if you're comfortable with it, or you could adjust your server's configuration to allow access from both networks. Changing classes or reconfiguring the A class isn't necessary unless you're looking at deeper changes. Just make sure to test everything carefully and double-check the subnet masks. It’s not impossible, but it does require some planning. Don’t worry, you’re not doing anything wrong—just taking it step by step.
We started with two distinct networks for better coverage and flexibility.
If routers support multiple VLANs or routing tables, then yes—assigning them works. The reason you have two separate Class C blocks is likely due to configuration differences or specific requirements for each network segment.
It wasn't my decision to divide it; I received it that way. The split happened because there are two distinct user groups and only one ISP connection, so someone divided it into separate networks. Now they're asking for a shared server, but they're not really in favor of merging it. I'll need to convince them otherwise.
In the end, subnetting would have provided more advantages. Rather than using 192.168.0.0/24 and 10.0.0.0/24, a more organized approach would have been to adopt 192.168.0.0/25 or 192.168.0.128/25 based on host requirements. If you require a full Class C per floor, then 192.168.0.0/24 and 192.168.1.0/24 would suffice. Your current addressing remains valid, though it can become cluttered. Provided VLANs exist, a static route on the main router should suffice for directing traffic.