Member Avatar for weasel7711

I work for my family's small business. I recently graduated with a BS in Comp Sci but I didn't have much networking education. I am setting up a small file server to serve core files to about 10-12 computers. It will be running Ubuntu Server while the PCs connected will be running various versions of Windows. The files they need are not large, less than a few MB, but its much safer to have all copies of the files in one location (aside from backup) rather than multiple copies on multiple computers. I was wondering about how to structure to network. I have two choices that I can see at this point.
Modem --> Server --> Router --> (PC1, PC2, PC3, etc)

This is the architecture that I am leaning toward but I didn't know if I should consider the following:
Modem --> Router --> (Server, PC1, PC2, PC3, etc)

I figured with the first layout I can filter internet, server printers, and control the entire network through one computer/server. What should I go with or what other questions should I be asking myself before I make the decision?

Thanks for the help.
-Weasel

  • 3 Contributors
  • 3 Replies
  • 486 Views
  • 2 Months Discussion Span
  • Latest Post Latest Post by weasel7711

Dani AI

Generated

Practical, ready-to-use checklist for a small Ubuntu file server. Builds on ’s topology suggestion and ’s OS note while focusing on the operational steps that matter after placement is decided. Priority items: predictable addressing, reliable wired links, secure SMB configuration, and recoverable backups.

Network and hardware
Give the server a stable address via a DHCP reservation on the router (simpler than hard-coding on the host). Use wired gigabit connections and a gigabit switch to avoid throughput bottlenecks; put the server on the same LAN segment as clients for easy discovery. Keep a UPS for the server and router so brief outages don’t corrupt files. Avoid making the file box the gateway—letting the router handle WAN/NAT simplifies security and reduces single points of failure.

File sharing and Windows integration
Use Samba with UNIX accounts that mirror Windows users, and control access with groups rather than broad guest shares. Enforce modern SMB (disable SMBv1) and prefer SMB2/3 for performance and security (e.g., set server min protocol = SMB2 and require encryption where supported). Provide name resolution with the router’s DNS or a lightweight DNS/DHCP on the LAN so clients can mount by hostname rather than raw IP.

Security, backup, and maintenance
Do not expose SMB ports to the Internet; use a VPN for any remote file access. Block SMB ports at the edge router and monitor authentication logs for odd activity. Implement regular backups (daily incrementals + weekly full), keep an offsite copy, and remember RAID is redundancy, not a backup. Keep the OS and Samba updated, document restore steps, and test restores periodically so recovery is straightforward.

Recommended Answers

All 3 Replies

Member Avatar for rch1231

Hello,

I suggest that you use the second setup.
Modem --> Router --> (Server, PC1, PC2, PC3, etc)
for several reasons.
1. You don't have to open ports on the routers firewall to allow the Windows systems to get to the server.
2. You can use the firewall in the router to limit access to the all of the systems and the server's samba drive share from the WAN.
3. It will also make it easier for the windows systems to find the server if they are in the same subnet. (i.e. 192.168.1.1-)

Hope this helps.

Member Avatar for oknaru

yes , u can follow the above steps and can use win 7 as server os and control all the pcs , also u can map the drive with all the users folders where they can store the files at one location in stade of storing on local machine...hope this will helps.

Member Avatar for weasel7711

I decided to go with rch1231's advice. Thanks for the help guys. Sorry for the late reply.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.