Our home network includes 2 servers in the basement. Both run Ubuntu 10.04 (Lucid) server. The older is primarily used as a web server. The newer is used mainly for NAS. When I’m completely happy with the new server I’ll add a web server, transfer our websites, then retire the old server. Both run Samba 3.4.7
The Samba server on the new server worked fine but I was using quick and dirty shares like this:
force user = root
writeable = yes
path = /storage
write list = steven
Using ‘force user = root’ is pretty sloppy but it works if I am the only user and I can’t be bothered sorting out linux permissions on the server. After a few days I needed to fix up the samba permissions so our other windows PCs could access the samba shares for file sharing and backing up. So I needed to:
- make sure the unix users have the correct directory and file permissions
- the corresponding samba users exist and have the same passwords
- the Windows hosts and users are set up correctly
- that is, Linux user <=> Samba user <=> Windows user
All went ok except for one thing: one of the other PCs always (or mostly) connected to the samba server as me. This was a problem because I wanted write access for myself for all the samba shares but I wanted the other PC to have read only access to some of the shares (videos, music etc) but write access to others (eg backup). The samba log reported that the correct host was connecting but the incorrect user. If I deleted my Samba user then the PC would connect to the correct Samba user. Then when I recreated my samba user the PC would again connect as me, which is the incorrect user for that PC.
I tried many fixes, such as
- created new windows users on various windows PCs – all were able to access the samba shares
- reinstalled Samba and changed the password backend from smbpasswd to tdbsam
- at the same time I was sometimes having trouble browsing the shares from all Windows boxes so I disabled the WINS server and instead configured all network IPs manually using hosts/lmhosts files.
At last today I figured it out. Of course the problem was with Windows rather than with Samba or Linux. At some stage I must have logged in to my samba user from the other PC and windows remembered that username and password. Despite numerous restarts and logouts and occassionally connecting to the correct samba user (when mine was not available) windows remembered my username and used it when possible. The solution was “to delete stored user names and passwords“.
For a number of years I have networked our home PCs. I did it for the usual reasons: to share devices like printers and storage, and resources like internet access and media files. I think my enthusiasm peaked in about 2002 while I was doing a Cisco networking subject at UTS. But over the last few years I have tried to take a more pragmatic approach. I stick with regular consumer hardware and software and I try not to indulge my IT excesses. If I can justify it I still like to configure things manually but I no longer collect junk for repair and improvement.
Our current network comprises:
- 3 PCs running Win XP +SP3,
- 1 web/storage server running Ubuntu 9.04
- 1 laptop running Win XP +SP3
- 1 PS3
- 2 mobile phones with wifi
The PS3, laptop and 1 PC connect wirelessly. 2 PCs and the server use fast ethernet cables. I also incorporate an 8-port switch for ease of cabling and to accomodate workbench projects.
Until last week I was using a Dynalink RTA1025w wireless modem/router connected to Exetel ADSL2. It had performed well for a few years but in recent months our net access was getting flaky. Everything still worked and it synched at 12 Mbps but anything that required a consistent connection seemed slower. I had a look inside the Dynalink and sure enough some caps were swollen. I replaced them but it only lasted for a day after surgery. Maybe my soldering was sloppy or maybe it was just a very cheap PCB.
To maintain our net access while I decided what to do I installed a Siemens Speedstream 4200 ADSL modem. I have two of these in the workshop. They are very simple WAN/LAN modems with only 1 LAN port and used to be given away by Optus and Telstra as part of broadband package deals. Many people immediately replaced them with a multiport modem/router so there are lots of these sitting around in unused condition. It performed really well. It’s abililty to route is almost non-existent but it is a great little modem. For a weekend we just had the Speedstream plus the switch operating with our wired PCs and there was a clear improvement over the recent performance of the Dynalink.
I decided to keep the Speedstream and add a separate wireless router. A few months ago my Mum got a laptop and I suggested they add a wireless router to their cable modem. I picked the ASUS RT-N11 and it proved to be good value, easy to set up and reliable. So I bought another for us.
Here is what I did:
- installed the latest generic firmware on the Speedstream. Optus and Telstra both produced firmware for use with this modem but I didn’t want any provider-specific features or settings confusing my setup. Firmware and lots of info about this modem is available from http://www.modemsupport.com.au/ [This site seems to be down at the moment, 18 May 2013, so try this for more info: http://shadow.sentry.org/~trev/4200.html]
- here are some instructions for bridging the Optus version
- put the Speedstream into bridge mode, so that all incoming packets are just sent to the Asus router. (Note that while in bridge mode the web configuration utility is not available so if you want to leave bridge mode you need to reset the modem to factory defaults and start configuration from scratch). I found a few different procedures for entering bridge mode. I read this whirlpool post but ended up following this HOWTO written by Jacob Comber. Except that my modem with generic firmware has IP 192.168.1.1 and not Telstra’s version with 10.0.0.1 That made things a little easier later because all the devices on my LAN have manually set IPs in the 192.168 subnet.
- After setting the modem to bridge mode I just connected the RT-N11 to the modem and to my PC and went through the router’s web setup utility.
For the record this is how to return the 4200 to factory defaults:
- Using the tip of a ballpoint pen or unfolded paperclip, press and hold the Reset button located on the bottom of the modem. The pwr LED will blink red once, indicating that the reset has begun.
- Continue depressing the Reset button for four seconds or until the pwr LED begins to blink alternating red-to-green.
- Release the Reset button.
In October 2012 to improve wifi coverage and to give me more control I bought an ASUS RT-N16 to replace the RT-N11, which I’ll keep as a spare.