Most “server is down” complaints in small offices are actually “the server moved” — a changed IP, a renamed PC, a shortcut pointing at an address that no longer exists. Discipline prevents all of them for free.
This is the least technical page in the series and the one that saves the most support calls. A file server is infrastructure, like the electricity meter: it gets one name, one address, and one set of drive letters, written down and never improvised. Apply it on day one, whichever of the three methods you built.
Name the server for its job, not its hardware or its owner: FILESERVER (or OFFICE-SERVER) will still make sense in five years when the box has been replaced twice; "RAMESH-PC2" will not. Keep it short, one word, no spaces or special characters — names get typed into phones, scripts and support calls. Every share path in the office then reads the same way: \\FILESERVER\Accounts. When the day comes to migrate to new hardware, the new box takes the old name and every mapping in the office keeps working — the single strongest argument for naming discipline.
The server's address must never drift. Two correct ways: set a static IP on the server itself, outside the router's DHCP pool range; or keep the server on DHCP and add a DHCP reservation in the router, binding the server's MAC address (from ipconfig /all on Windows, or the TrueNAS dashboard) to one fixed IP. Reservations are easier to manage centrally and document; static IPs survive router replacement. Either is fine — what is not fine is the default, where the address is whatever DHCP felt like on boot day, quietly changing after every long power cut.
Shortcuts and mappings built on \\192.168.1.50\Accounts embed the address into every PC, every script and every saved document link. The day the address changes — new router, new subnet, replaced server — all of it breaks at once, and the fix is a tour of every desk. Mappings built on the name resolve through the network fresh each time, so the same change is a non-event. If name resolution ever misbehaves on your LAN, fix the DNS/DHCP setup rather than retreating to IP shortcuts — the shortcut always sends the bill later.
Agree the letters once: perhaps S: for the Common shared drive, A: for Accounts, and so on, avoiding letters local devices already use. Map them identically everywhere — by Group Policy Preferences in a domain, or by a small logon script (the commands in the panel above) on each workgroup PC. The payoff is human, not technical: "save it in A: drive, Billing folder" becomes a complete instruction that works in training, on the phone and in documentation. Random per-PC letters make every support conversation start with five minutes of archaeology.
Finish with a single page kept with the office records: server name, fixed IP and how it is fixed (static or reservation, and the MAC), the share list with their drive letters, where backups live, the snapshot schedule, and where the admin credentials are sealed. Update it the day anything changes. This card is what lets any competent technician — or you, two years from now, at 9 PM — understand the setup in four minutes instead of reverse-engineering it.
The video names and configures its servers on screen as the builds happen — watch how the same discipline applies across all three methods.
▶️ Watch Full VideoBoth are legitimate. Reservations centralise the record in the router, which is nice until the router is replaced and the reservations vanish with it. Static IPs on the server survive router swaps but must be recorded on your server card so a future DHCP pool change does not collide with them. Consistency and documentation matter more than the choice.
Pick a different letter for the office standard rather than fighting per-PC exceptions — letters from the middle of the alphabet (S, T, U) are usually free everywhere. One standard with a slightly unusual letter beats a “perfect” letter that exists on only half the machines.
In one planned pass: fix the server name and reservation first, then re-map each PC by name with the same letters, and update saved shortcuts and application paths (accounts software often stores file locations). Do it desk by desk in one week, then change nothing about the old address until every machine has been visited.