IP Address, Windows Server 2019, SonicWall TZ350


New Member
Hello everyone,
I recently start working in small business medical organization. I am not sure if this is the right place to ask, but i am facing a problem that I could not figure out if IP address in location A is then on Location B is so on... My question is how it is configured like that? What is used to configured this way, I mean using Server or Using Firewall or does it has to do with Router/ISP provider? Firewall is SonicWall TZ350. I am myself all alone, I am only entry level, I do have basic understanding and some intermediate. IF i add user in Location A using active directory, Same user can login in Location B. After short while i got hired, Network engineer fough my boss and quit the company for whatever reason.

Thank you,

It sounds like you're dealing with a network setup that spans multiple locations. In this type of setup, the IP addressing scheme you described is usually achieved using routing and firewall configurations.

To establish connectivity between different locations, routers or managed switches are commonly deployed. These devices are responsible for routing traffic between different subnets or IP address ranges. Additionally, firewalls like the SonicWall TZ350 you mentioned can be used to enforce security policies and control traffic flow between locations.

Here's a simplified explanation of how the setup you mentioned might be configured:

1. Each location has its own subnet: Location A has a subnet with IP addresses in the 10.1.10.x range, Location B has a subnet using 10.2.10.x, and so on. This allows devices in each location to have unique IP addresses while still being part of the same organization's network.

2. Routers or layer 3 switches: These devices connect the different locations together and allow traffic to be routed from one subnet to another. They facilitate communication between devices in Location A and Location B, even though they have different IP address ranges.

3. Firewall configurations: The SonicWall TZ350 may be responsible for regulating the flow of traffic between locations. It could be configured to permit specific traffic between subnets and enforce security policies. This ensures that only authorized users and devices can access resources in different locations.

4. Active Directory and user management: Active Directory is a Windows server feature that enables centralized user management and authentication across the network. When you add a user to the Active Directory domain, it is possible for them to log in from any location within the domain, including Location A and Location B.

If you need to add users and manage them in Active Directory, you should have administrative access to the domain controller. However, without the expertise of a network engineer, managing a complex network setup can be challenging. If you have specific issues or concerns, it might be a good idea to reach out to a consultant or technology specialist who can provide assistance.

I hope this information helps you understand the basics of how a multi-location network might be configured. If you have any further questions, feel free to ask!
Lots of ways this could be setup and that will depend on the equipment in the mix.

Most likely their will be vlans setup on your switch(es) with a trunk port setup for however traffic is fed into the servers, specifically the DHCP. From DHCP there will be a scope per subnet however that is partitioned out