Server-Workstation Network Upgrade
Budget: $15 – $25 USD
I need a fresh set of eyes on the way our servers talk to our workstations. At the moment the traffic flows, but not as smoothly as I’d like: file transfers stall, log-ins lag, and a few mystery drop-outs appear during peak hours. Everything sits on one flat IPv4 segment sprinkled with a handful of unmanaged switches, so there’s plenty of room for smarter design.
You’ll start by reviewing the current topology, cabling runs, switch configurations (where any exist), and the Windows-based server roles that soak up most of our bandwidth. From there, I’d like clear, actionable recommendations—whether that points to VLAN segmentation, QoS tweaks, upgraded switching hardware, or simply better-tuned NIC settings on the workstations. Packet captures with Wireshark or a similar tool will help us make decisions backed by hard numbers rather than hunches.
Deliverables
• A concise network diagram showing the “as-is” layout and your proposed “to-be” state
• Written configuration changes or commands suitable for our switches/routers (note the exact model or OS version when relevant)
• A short report that summarises bottlenecks you discovered, the tests you ran, and the measurable improvements we can expect once changes are applied
The environment is small enough to grasp quickly, yet critical to daily operations, so every suggestion must balance performance gains with minimal downtime. If this sounds like the kind of optimisation project you enjoy, let’s get it moving.
You’ll start by reviewing the current topology, cabling runs, switch configurations (where any exist), and the Windows-based server roles that soak up most of our bandwidth. From there, I’d like clear, actionable recommendations—whether that points to VLAN segmentation, QoS tweaks, upgraded switching hardware, or simply better-tuned NIC settings on the workstations. Packet captures with Wireshark or a similar tool will help us make decisions backed by hard numbers rather than hunches.
Deliverables
• A concise network diagram showing the “as-is” layout and your proposed “to-be” state
• Written configuration changes or commands suitable for our switches/routers (note the exact model or OS version when relevant)
• A short report that summarises bottlenecks you discovered, the tests you ran, and the measurable improvements we can expect once changes are applied
The environment is small enough to grasp quickly, yet critical to daily operations, so every suggestion must balance performance gains with minimal downtime. If this sounds like the kind of optimisation project you enjoy, let’s get it moving.
Related categories:
Cisco
Windows Server
Network Administration
Network Security
Network Engineering
Performance Tuning