Re: Network: everything seems okay, but there's no connect
- From: jpd <read_the_sig@xxxxxxxxxxxxxxxxxxxxxx>
- Date: 23 Dec 2007 12:23:14 GMT
Begin <29fsm3pu2vbmpgd4t7q32k8ohn8qnppsho@xxxxxxx>
On Sun, 23 Dec 2007 11:12:11 GMT, Puzzled <scratching.head@xxxxxxxxxxx> wrote:
Now that i've got the addresses fixed up, i can ping - but
windows is still not doing a lookup in hosts. If i pass ping the
address it works fine, but if i pass it the nodename, it shrugs
and says 'unknown'. Any ideas about that?
Set up DNS. For local hostname lookup you can either fix the hosts
files (on every host, every time something changes[1]) or you can run a
locally authoritative DNS server that will translate host1.puzzled.local
to 192.168.2.11 and back, and so on and so forth.
I should mention that i'm building the fbsd box as a tame server
for web dev and testing, not as a fw for the lan. That's why the
win boxes have fws running.
Your windows machines having to contend themselves with LINK-LOCAL
addresses tells me your network was not setup at all. You probably
should fix that. Just plugging in machines and have them magically
work is possible, but you need something on your lan that provides
the services that make that work.
For small local networks like this it makes sense to build a small box
(old pc, soekris box, linksys thingy, etc.) that will play gateway, fw,
local- and caching DNS server, DHCP server, and maybe provide NTP too.
The upside is that you have only one place where you assign names to
machines (DNS) and provide them with the necessairy configuration
information (DHCP) and have only one box talking NTP to the rest of the
world while ensuring all machines on the LAN have the same time even if
the uplink dies.
Caching DNS means the local boxes ask it for anything they want looked
up, and it'll ask the other servers on the 'net for them, caching the
results. If you're feeling really fancy and have some disk and cpu to
spare on that magic lan box, you could add a caching proxy to reduce the
http bandwidth used on the uplink too. It's not required, though.
Read through the handbook and the various other books and articles on
the FreeBSD project site and see if that helps you getting started.
You are your own network admin now, so might as well get it right.
[1] Which is how the internet started out. Then people got sick of
it and they invented DNS.
--
j p d (at) d s b (dot) t u d e l f t (dot) n l .
This message was originally posted on Usenet in plain text.
Any other representation, additions, or changes do not have my
consent and may be a violation of international copyright law.
.
- Prev by Date: Re: Network: everything seems okay, but there's no connect
- Next by Date: Re: Network: everything seems okay, but there's no connect
- Previous by thread: Re: Network: everything seems okay, but there's no connect
- Next by thread: Re: Network: everything seems okay, but there's no connect
- Index(es):
Relevant Pages
|
