I agrree about the static ip's.... I prefer them, especially in a small network... but then I also prefer jumperable hardware (PNP can be quite annoying...) He might be able to get by just by setting the hostname (hostname jim.darrough) I wrote him last night... maybe its working now... Personally, I would rather setup FQDN's. You can get dynamically assigned domain names from many places... Ive used dyndns, ml.org (now gone...) and they work pretty well... I had a network up for a year on a dialup connection using them... my IP changed many times a day, and I rarely had an instance when I couldnt find my computer (sometimes it would take upto a minute...) with a 24/7 connection (like DSL, @home, radio?) your ip doenst change often. and can be updated automatically, or on demand. I guess e-smith is ok if you dont want to know about networking, or how to configure services and such... its just not for me really... (no offense, if you like it, use it!).
Jamie On Sunday 02 December 2001 10:28, you wrote: > One way around fqdn, samba woes & local routing difficulties > is a simple set of /etc files files with only localhost, local intranet > addresses and windows pc addresses: > > hosts - entries for intranet ip.address then spoofed fqdn then alias eg: > 127.0.0.1 localhost > 192.168.0.x butthead.nodomain butthead > > lmhosts - entries for nmblookup ip.address then alias eg: > 192.168.0.x butthead > > networks - spoofed network name then 18,24 or 32bit net > loopback 127.0 > butthead 192.168.0 > > Note loopback device is usually required for local machine > browsing, http, etc. Check ifconfig and/or lsmod and usual network > setup files. Also, caps in network names aren't so good, as most *nix > stuff is case sensitive. Use caps in Samba configs *only* if some windows > box barfs on mixed case or lowercase names. Spoofed net entry only > if local intranet routing is hosed. Having hosts & lmhosts on windows > boxes in c:\windows\ helps them find stuff on the intranet fast as well and > cuts down on windows searching & caching. > > resolve.conf should not search local addresses or "spoofed" domains. > host.conf order should be host first. Samba should default to lmhost,host > with no dns EVER (found this the hard way when some windows box couldn't > find a share and broadcast nmb queries out ALL interfaces. There are > also a few lines in smb.conf which restrict what interfaces may be used). > > There appears to be some buggy code and/or scripts in the latest > Mandrake x-based gui configurators. I fixed my printing using the > ncurses-based tools from a real root shell login. > > IMHO dhcp isn't worthwhile for a small net. I've never had trouble with > static routing with up to 20 or so clients. > > Good luck! > > - jk > > On Saturday 01 December 2001 20:44, Apparently Jim Darrough said: > > Hi Jamie. > > > > The only problem is that I use DHCP on an e-smith server to provide my > > ip addresses, so they can change if the system has to be rebooted. I can > > mount and manually print to the remote printer using smbclient, so I > > know it works and is visible. The problem is that when the system boots, > > lpd does not load due to an error message telling me that jim.darrough > > is a bad hostname. How do I get around that? > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com
