Enterprise Networking Guide
How to Fix Slow OA, ERP, and Internal Web Access from Overseas Branches to China Headquarters
When overseas subsidiaries, offices, or factories connect back to headquarters in China for OA approvals, internal web pages, ERP, or finance systems, they often face slow logins, interrupted attachments, and long save waits. Using existing broadband at each location, we deploy access appliances and establish cross-border transmission channels between overseas sites and China headquarters data centres or public clouds to improve remote office response without replacing existing software or account systems.
Many enterprises with overseas subsidiaries, sales offices, or factories rely on daily access back to internal systems hosted in headquarters data centres or cloud platforms in China: administrative and sales staff open internal headquarters web pages, log in to OA systems to submit approvals and send or receive contract attachments, merchandising and warehouse staff check inventory and enter or save orders in ordering or ERP systems, and finance staff retrieve and submit headquarters financial reports. Enterprises often find that while local colleagues at headquarters in China work smoothly, overseas employees face endlessly spinning pages, long waits after clicking "Save" or "Submit for Approval," and interrupted attachment transfers.
To support overseas offices accessing internal systems at headquarters in China, we use the existing public internet broadband at each site to deploy on-premises or cloud access devices between overseas branches and China headquarters data centres (or domestic public clouds), connecting both ends to a cross-region transmission network; for small overseas offices that only use a single internal web application, we can also extend an access entry point near the overseas location. Requests from overseas employees to headquarters internal systems travel over a dedicated cross-border channel while general web browsing stays on local broadband, allowing the enterprise to keep its existing office software, employee account systems, and local broadband without waiting to install new cross-border physical dedicated lines (if teams in China need reverse access to internal systems such as SAP at European or North American headquarters, the same approach applies).
How headquarters in China, public clouds, and overseas branches connect at both ends
We combine connection methods at both ends based on where your China headquarters systems are hosted, the headcount at each overseas site, and on-site conditions, without forcing a one-size-fits-all deployment across every branch:
- China headquarters data centre or domestic public cloud side: If internal web pages, OA, ERP, or finance systems are hosted in a headquarters data centre in China, a physical device can be deployed in the data centre alongside your existing firewall or switches; if headquarters has a virtualised environment, or if systems run on domestic public clouds such as Alibaba Cloud, a virtual access device can be deployed directly in the existing virtualisation platform or cloud environment to connect the internal network. Access devices can run alongside your existing VPN or circuits for a smooth transition.
- Overseas factory or major branch side (site-to-site intranet interconnection): When an overseas factory, R&D site, or larger subsidiary needs simultaneous access to headquarters OA, ERP, production management, and internal file sharing, the overseas site deploys a physical access device directly over its existing local office broadband (or a virtual device if on-site virtualisation is available) to form a unified enterprise intranet with headquarters in China and public clouds. For overseas branches without dedicated on-site IT staff, we ship a pre-configured device to the site using zero-touch provisioning (ZTP), so local staff simply plug in power and the existing broadband cable to pull configurations automatically. For example, in a similar cross-border multi-site networking project, we helped a Suzhou precision equipment manufacturer connect its Suzhou headquarters, multiple domestic offices, and overseas branches (10 offices in total) along with Alibaba Cloud and Azure (5 public cloud environments in total) into a single enterprise network, achieving stable interconnection between cross-border branches and multi-cloud internal networks while preserving existing broadband access at each location.
- Small overseas office side (nearest entry point for a single system): If an overseas sales office has only a few employees who mainly open a single internal web page or approval system at China headquarters via a browser or client, and modifying the local office LAN is inconvenient, we can use application publishing to extend that system's access entry point near the overseas branch region so authorised employees connect to the nearest PoP and reach headquarters over our backbone network. Choosing between a single-system entry point and site-to-site intranet interconnection depends on how the software actually runs: if the application calls multiple backend internal services during use, site-to-site intranet interconnection is more suitable.
Which requests use the cross-border channel and what your existing environment can keep
Once connected, traffic is routed by destination address: traffic from overseas employees to China headquarters internal subnets, internal domain names, and cloud business systems enters the cross-border channel, while daily browsing of local web pages or external public services continues over the overseas office's existing local broadband. If your internal portal, OA approval system, or ERP also calls internal DNS resolution, unified account authentication (such as Active Directory or single sign-on), separate attachment storage, or software licence servers when logging in, opening forms, or downloading attachments, we confirm all involved internal addresses with your system administrator and include them in the channel so users do not get stuck on login verification or attachment downloads after the main page loads.
With this approach, your enterprise keeps its existing business software, employee account permissions, and local carrier broadband at every site, and network-level connectivity never bypasses the access controls of the business systems themselves. During deployment and go-live, we work with your China headquarters or cloud administrators to confirm required address ranges, routing, and security policies based on your actual network environment, scheduling the cutover window outside peak office hours (we recommend keeping it separate from software version upgrades). Provisioning is faster than traditional cross-border physical dedicated lines, and after cutover, overseas employees notice improved responsiveness during normal working hours when logging in, sending or receiving attachments, and querying or entering orders; during month-end financial closing, peak order entry seasons, or periodic bulk data syncs, you can also scale up bandwidth on demand without waiting for long circuit construction lead times.
Why local access at headquarters is smooth while upgrading overseas branch broadband alone still lags
For systems deployed in a China headquarters data centre or domestic cloud, every click request and data response from an overseas employee must cross international links. Long-distance transmission inherently carries physical round-trip latency; when traffic travels directly over the public internet, congestion or packet loss on cross-border segments triggers retransmission waits. Whether opening an internal web page with multiple forms and attachments or executing operations like "Save Order" or "Post Document" in ERP and finance systems that require repeated back-and-forth confirmations between the client and the headquarters server, latency and packet loss retransmissions compound—when the bottleneck lies on that cross-border public internet path, simply upgrading the overseas office's local broadband plan to a higher speed cannot shorten the wait across the international route. At the same time, unstable local Wi-Fi at the overseas office, local broadband saturated by large files, an overloaded existing firewall VPN tunnel, or heavy headquarters database load and maxed-out concurrent accounts or software licences can also cause slow responses or dropped connections, so a single lag event or smooth local access at headquarters should not be attributed solely to the cross-border link. Before reaching out for a consultation, you do not need to capture packets, run speed tests, or troubleshoot device load item by item; simply share the difference in operational experience between overseas and headquarters colleagues, and we will help you verify the situation alongside your current network conditions.
Basic information to prepare for your initial consultation
- Which city data centre or cloud platform hosts your headquarters systems in China, which countries and cities your overseas branches, offices, or factories are in, and which systems they use daily (such as internal web pages, OA approvals, ERP, or finance software).
- Specific daily operations that overseas employees report as slowest or prone to interruptions (such as spinning login screens, sending or receiving approval attachments, querying and saving orders, or exporting financial reports), and whether colleagues at headquarters in China experience normal performance during the same hours.
- How overseas sites currently connect to the internet (such as local standard broadband or an existing VPN) and any explicit headquarters rules on access scope or security; for an initial consultation, you do not need to prepare network topology diagrams, packet capture reports, system account credentials, or internal business data.