Connect. Secure. Manage.
Cisco Remote Access Troubleshooting
Investigate Cisco VPN connection and access faults through client logs, identity services, tunnel policies and the routes to business applications.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
Cisco remote access troubleshooting follows each stage of the user’s failed connection. We check client settings, identity checks, tunnel setup and the path to the app. Evidence from the affected workflow guides changes on supported Cisco VPN systems. This avoids changing unrelated settings and keeps live work within the agreed approval process.
Defined trust
Make access boundaries explicit rather than relying on an assumed internal network.
Controlled access
Connect identity, policy and network enforcement to the services people actually use.
Evidence for change
Test the intended security outcome and retain useful operational records.
Identify where the connection stops
We ask what the user sees, which device and client version are involved, where they are connecting from and when the failure began. A certificate warning, rejected login, disconnected tunnel and unreachable app point to different areas. Comparing a working user or device with the failing case can narrow the investigation substantially.
Recent changes are recorded, including gateway upgrades, certificate renewals, identity policy and endpoint software. The investigation does not assume the VPN platform is at fault merely because the symptom appears while a user is remote. Local internet access, DNS and the app itself remain possible causes until evidence separates them.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Check the endpoint and gateway identity
We check the service name, DNS response and gateway certificate presented to the client. An unexpected address or trust warning is investigated rather than bypassed. Client profiles and certificate-selection settings are reviewed where they influence the connection, particularly on devices carrying old profiles or multiple authentication certificates.
Endpoint security software, local firewall rules and another installed VPN can also affect the path. We assess those interactions with the relevant support team. Temporarily disabling protection across a fleet is not a proportionate diagnostic method when a narrowly scoped test can establish the same point more safely.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Trace authentication and authorisation separately
The gateway may authenticate through an external identity provider, RADIUS service or another supported arrangement. We correlate timestamps and results across the systems involved, checking group mapping and the policy actually chosen. A user can pass MFA and still be correctly denied access by a separate authorisation rule.
Recovery and exception accounts are treated carefully. We do not broaden group membership or remove MFA simply because an ordinary login fails. Any temporary access requires approval, a limited purpose and a review point. The investigation should explain the failed condition so the final correction does not depend on leaving an insecure workaround in place.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Follow the application path after the tunnel forms
An established tunnel proves only part of the service. We check the assigned address, routes, DNS setup and permissions relevant to the user's app. Return routing and downstream firewall policy can cause failures even when the client reports a healthy connection.
Overlapping home networks, split-DNS behaviour and apps with several dependent destinations deserve particular attention. We test the real protocol and workflow rather than relying exclusively on a ping. The result should distinguish a missing route from an app refusal or a name-resolution answer that sends traffic to the wrong destination.
Investigate intermittent performance with measurements
Slow or unstable remote access can reflect latency, loss, MTU problems, congestion or resource pressure at the gateway. We compare affected times and paths, review relevant counters and use controlled tests appropriate to the app. One speed-test result is rarely enough to identify the responsible component.
We also consider session changes caused by roaming, sleep and resume or internet failover. A user may experience repeated interruption even though each individual reconnection succeeds. The investigation records those transitions and tests whether the behaviour matches the supported client profile and the customer's availability expectations.
Collect evidence proportionately
Client diagnostics and gateway logs can be valuable. But they may contain usernames, destinations and other sensitive details. We agree what is necessary, how it will be transferred and who can access it. Authentication codes, passwords and unrestricted setup archives should not be placed in ordinary public support messages.
Captures and active tests are authorised and bounded. We prefer a defined hypothesis and a verification step to making several unrelated changes at once. Where a vendor escalation is needed, the evidence package identifies the affected versions, reproducible workflow and observations without presenting an unconfirmed theory as a proven product defect.
Resolve the cause and remove temporary measures
The incident record explains what failed, the evidence supporting the conclusion and the change made. We check the affected workflow and relevant neighbouring cases, including users whose access should remain restricted. Temporary diagnostic permissions and exceptions are removed or formally accepted with ownership.
MCI can provide a focused investigation or support an internal team handling a recurring problem. Our Cisco remote access VPN design review is relevant where repeated incidents reveal a structural issue in routing, identity or resilience. Begin with the symptoms and affected workflow. We can then agree a safe scope for access and testing rather than asking for sensitive production details before the problem is understood.
Technical references
- Cisco Secure Client VPN configuration — Cisco / Cisco Meraki
- Cisco Secure Client certificate matching — Cisco / Cisco Meraki
Talk to a specialist
What does your network need next?
Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.