The connection was tied to one laptop rather than serving an expanded office workstation environment.
One office.
More possibilities.
I replaced a single-laptop remote-access arrangement with a tested SonicWall site-to-site VPN at a satellite office, supporting five on-site computers and enabling employees to work, meet, and attend training closer to where they are based.
From one laptop using NetExtender to three workstations and two laptops at the satellite site.
Monthly meetings and certification-dependent training can be attended from their nearest office.
User-reported additional field-work time available on affected meeting or training days; not a time-sheet audit.
The constraint was
bigger than a VPN client.
The satellite office originally relied on one laptop running SonicWall NetExtender to reach resources associated with the main office. This limited the local setup and did not provide an office-wide site-to-site connection for a larger group of computers.
Employees also had to travel to the main office for company-wide meetings and training. For field personnel, that travel competed directly with time available for scheduled field work.
From one connection
to a connected office.
The diagram below is conceptual. It shows the change in access model, not real firewall topology, addressing, routes, authentication settings or tunnel configuration.
Five local computers use the site-to-site arrangement instead of relying on NetExtender running on a single laptop.
Infrastructure that
supports a team.
My contribution combined firewall deployment, remote-access administration, expansion of the satellite office's device footprint, and end-to-end testing.
Clean up legacy VPN accounts
Reviewed and cleaned up existing VPN accounts and reactivated Cloud Secure Edge for several users as part of the broader connectivity work.
Install the satellite-site SonicWall
Installed a SonicWall at the satellite office to support a persistent interoffice site-to-site VPN instead of depending on a single user's laptop and NetExtender session.
Support five local computers
Expanded the office setup to three workstations and two laptops, with office resources accessed through the site-to-site VPN arrangement.
Establish and test the connection
Established the site-to-site VPN and successfully tested connectivity between offices. This is a completed, validated deployment, not a proposed future tunnel.
Less traveling.
More time in the field.
With the satellite office equipped for regular work and Microsoft Teams conferencing, staff can participate in company-wide meetings and training from a nearby office rather than assembling at the main location.
Closer to the work
Field employees can use their nearest office for meetings and certification training, reducing the need for cross-office travel.
One company-wide meeting each month
Across a field team of 35, each affected employee can potentially reclaim about one hour on a meeting day that would otherwise be allocated to travel.
Four to eight monthly training sessions
Training frequency depends on certification level. Each relevant attendance day can also make about one additional hour available for field work.
Meeting-only illustration if all 35 field staff attend and each avoids one hour of travel. Actual reclaimed hours depend on who attends, which office they use, and their previous travel arrangements. Training benefits are additional but cannot be totaled without attendance by session. No payroll savings, increased billable hours or measured productivity gain is claimed.
Technical deployment.
Practical business value.
This project moved beyond troubleshooting an individual laptop. I helped turn a small satellite location into a more capable office environment, with reliable interoffice connectivity for multiple computers and an operational reason for the upgrade.