Network troubleshooting
Intermittent Wi‑Fi, roaming failures, unexplained congestion, broken topology, unstable uplinks and the problems that survive the first three “fixes”.
- Root-cause mapping
- On-site measurement
- Recovery plan
Network architecture · Field infrastructure · Bohinj
Networks that
have to work.
Independent planning, troubleshooting and delivery for hospitality, rural operations, events and places where generic IT answers stop being useful.
- 01Design before hardware
- 02Failure paths made visible
- 03Verified in the real environment
What needs to work better?
Start with the problem.
Not the product catalogue.
We start with what the location needs: a new installation, an expansion or a system that no longer behaves predictably. We choose the technology once the constraints, dependencies and impact on daily work are clear.
Network planning
New sites, renovations, expansions and inherited environments. Wired, wireless, fibre, segmentation, resilience and capacity planned as one system.
- Architecture
- Coverage and capacity
- Failure paths
Installation & rebuilds
Practical implementation with clean architecture, sensible hardware and verification in the real environment — not only on a dashboard.
- Direct implementation
- Specialist coordination
- Handover
Internet anywhere
Fibre, 5G, LTE, satellite, point‑to‑point and multi‑WAN designs for mountain, rural and locations with demanding operating conditions.
- Path diversity
- Automatic failover
- Remote reach
Hospitality networks
Guest Wi‑Fi is only one workload. POS, staff devices, surveillance, access, reception, back office and Internet resilience all compete for the same infrastructure.
- Guest and operations separation
- Seasonal peak readiness
- Business continuity
Event & temporary networks
Temporary connectivity for events, seasonal sites and mobile operations where payments, production and staff systems still need to behave like permanent infrastructure.
- Rapid deployment
- Critical-workload priority
- Teardown-ready design
The whole operational path
One system.
Not six islands.
A network is useful when it supports the work that depends on it. Architecture connects internet links, the core network, wireless coverage and operational devices into one understandable system.
Upstream
Fibre · LTE/5G · Satellite · Radio
Core
Routing · Segmentation · Resilience
Field
Wi‑Fi · PtP · Outdoor coverage
Operations
POS · Staff · Guests · Cameras
The architecture is the product. Hardware is selected only after the system has a reason to exist.
The useful kind of difficult
Difficult is interesting.
A good network is not a pile of access points. It is a system of dependencies, constraints, failure paths and human operations.
The job is to remove fragility without replacing it with a different kind of complexity.
Field evidence · verification in practice
Evidence before
adjectives.
A system is verified against the environment and operation it serves. Public claims come later—only when their source, scope and wording are ready.
01record the actual operating conditions
02make failure paths visible
03test under representative load
04state only the supported outcome
This page explains the method. Client identities, measurements and security-sensitive details remain private until publication is approved.
Explore the field verification methodHow the work happens
Understand → Design → Build → Verify
One accountable line from the first symptom to a system that works in practice.
- 01Constraints before solutions
Understand
What are you actually trying to accomplish? Where do traffic and information flow, and what depends on them? What happens when something breaks?
- 02Clarity before quantity
Design
Choose the smallest architecture that solves the real problem, fits the organisation and keeps failure paths visible.
- 03The right hands for the job
Build
Implement directly or coordinate trusted specialists where fibre, electrical, construction or other disciplines are needed.
- 04Reality is the dashboard
Verify
Test the system where it matters: on site, under load, across actual workflows — not only in configuration screens.
One architect. The right people when needed.
Small by design.
AlpskiMedved.solutions is built around specialist systems architecture rather than a generic helpdesk model. Network infrastructure stays front and centre; related business systems are included when they are part of the same operational problem.
When a project needs installation capacity or a discipline outside the core, trusted colleagues and contractors join the work.
- Service area
- Bohinj · Bled · Kranjska Gora
- Model
- Independent specialist
- Bias
- Evidence over adjectives
Start here
Describe the problem.
We’ll start there.
A useful first message does not need a shopping list. It needs the location, what you want to solve or build, the impact on daily work and what “working” should look like.
START A CONVERSATION
Contact Marko Kolman by email or phone, or prepare a short project brief to start the conversation.