----- Original Message -----
Sent: Tuesday, January 06, 2004 11:58
AM
Subject: RE: [KCFusion] SA help
(OT)
I'm not going to claim any form of expertise in these matters, so
I'm just going to list maybe some questions that might spark an idea in
your head as to what might have happened. I know that when a computer
logs on to the network, it has to negotiate the ip from the dhcp server,
but then it has to register itself with the primary dns server on the
network for your dns mapping of machine name to ip to work. Has your
primary dns server failed? You should have a secondary dns server also,
and has it failed? Have new firewalls been installed on any of the
machines affected or any of the primary dns/dhcp servers that might be
blocking the necessary communication between the machines? Is there a
domain involved or is it just a workgroup? Have any of the network
settings been changed recently for either the domain, or any of the
machines? How long has it been since you've noticed these problems? It
normally seems to take maybe 10 - 15 minutes for the dns to register on
the domain just from my experience, and sometimes quite a bit longer. What
has changed recently around the same time as the problems started
happening?
Bruce Dunwiddie
Ticket Technology
P:
866.543.3331
F: 913.451.7832
[EMAIL PROTECTED]
What does it mean when you can find a
computer on the network by IP but not by computer name? I have three
computers all in the same workgroup. A webserver a backup server
and a workstation. I can't see the backup server from the webserver but
I can see the backup server from my workstation. I can see the
backup server from the webserver if I map a drive using the IP
address but not the computer name.
Adaryl "Did you reboot?"
Wakefield
Aviator by passion
Programmer by sheer force of
will