LMHOSTS is a stand-in for DNS in the sense that it
does domain-to-ip
translation. Odds are that your router is your DNS
server and as such should be
able to resolve all of you lan machine names into IP's
w/o using the lmhosts kludge.
All this extra mental gymnastics go out the window if
you'd just see the light
and use DHCP. I mean who cares what IP address a
system is on if you can get
there by name anyway????
No LEDs lit WOULD mean that some part of the router is
dead since having a
physical link lights a light reguardless of what a
higher layer does.
DHSinclair wrote:
> Ben,
> I do not know. Why I asked. I suppose I asked
because in testing my old
> router yesterday, it would not respond to pings or a
direct http call
> even though I had given it an IP addy that was
unique and on my chosen
> subnet. Oddly, the router looked (externally) as
though the switch
> portion was dead. No LEDs, no activity, no nothing
In or Out...... still
> troubleshooting.....
>
> The only "touching" I do to my "hosts" file is every
month when I
> download a new "host" file from sysInternals; and,
then install it on
> each client. I read somewhere that the lmhosts file
is used so my
> clients 'know' who everyone is. Did I miss
something?
> Yes, I do not have an active domain or domain
controller.
> All my clients use the default 'workgroup' in my
network setups.
> No, I do not use DHCP.
> Thanks. Best,
> Duncan
>
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
