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
At 11:58 01/14/2008 -0500, you wrote:
Why would you need to touch your lmhosts file at all? You should only
touch hosts, and even then you don't need to change that if you're just
bringing something you want to telnet to on your network.
DHSinclair wrote:
If I believe I need to bring another device (an old router) on to my LAN
for continued troubleshooting, should I update my current client's lmhost
file to disclose this "new" device B4 I plug the brick in?
The reason to put the device on my LAN is to try and see if the http
interface works or not.
So far, only the old telnet (rs-232c) works to this device........ :(
Thanks,
Duncan
