What improvements can be done in a small network in regards to shares?

Posted on

QUESTION :

Short of setting up an Active Directory; What improvements can be done in a small network in regards to windows shares/device discovery?


I have a small network.

  • ADSL Modem/Router/WiFi (gateway, DHCP, DNS) (+ 2 gigabit switches under it)
  • 2 almost always on desktops (Both Vista Business, one may upgrade to win7 soon)
  • 2 laptops (always on during the day) + 2 laptops that come into play every other day (OSes vary: XP, Vista, Ubuntu netbook. — all those windows laptops carry the ‘home’ version of windows–)
  • guest laptops frequently come into play also (usually XP or Vista)
  • a small NAS (Muse X Duo Raid)
  • a file server PC hidden away in the basement (new addition, Ubuntu)
  • a print/fax/scanner device
  • an HTPC under a TV in the play room.

There is no guarantee all of them sit on the same Workgroup (ie. the guests).

For the most part I don’t have any serious issues with regards to file sharing.

The most often glitch we get is a machine not ‘seeing’ another in ‘Network’ under it’s file manager. Users can manually enter //machine-name/ or //ip/ to get there, or, you know, call me and complain and I go and do that for them …

Current setup:

The ADSL router currently has DHCP, gateway and DNS duties.

Everything uses DHCP.

Not all machines use file sharing.

If we have any shares on the desktops/laptops they are read-only for ‘Everyone’ and we’re not sharing anything important there (just music, pics, silly stuff).

The Muse X Duo raid NAS device, and the Ubuntu box in the basement are both set up with account shares in mind and we do use that for important stuff and private backups etc. That NAS is slow (<5Mbyte/s read-write speed), but we’re starting to use the Ubuntu box for storage more and more lately.

I don’t plan on setting up an AD/PDC since only part of the hosts would use it anyways and it’d be an administrative headache we (I) don’t absolutely need.

Questions:

Any suggestions that would improve the setup?

Would I see any real improvement if I moved the DHCP and DNS duties to the Ubuntu box in the basement? (Something else too maybe? .. WINS? or does that not matter in such a small network?)

What would improve connectivity/device discovery/whatever you want to call it, for the permanent machines that are always here?

Same question for the guest laptops that occasionally come here?

Update: If the ubuntu box was to take over DHCP duties, and DNS duties, would dhcp and dns talk to one another to keep the local ip/names updated? Would that translate to some actual difference on the windows machines?
ie. How would a windows machine ask a local dns server something like ‘give me all known local host ip/name info’? or is that something else (ie. WINS? or is that too archaic?)

ANSWER :

Set up an internal DNS server that has your local machine entries in it and forwards any unknown requests off to the Internet (ie: the ISP’s name servers).

Check out MaraDNS it’s free and open source, and runs on Linux and Windows:

MaraDNS is supported on two platforms: CentOS Linux 5, and Windows XP (via MinGW32).
Other systems can be easily ported to, but are not supported. This means that, while it should be fairly easy to port MaraDNS to another platform, you will have to port it yourself or pay me to port it for you. The Windows XP port does not support all of the features the CentOS Linux version has.

There’s probably others out there for you to choose from as well.

Leave a Reply

Your email address will not be published.