R
Rob Carroll IndusCom
Hey everybody,
OK... this is probably a simple issue, but I don't have time to
troubleshoot it. Here's the scoop...
I've got one Windows 2000 server, which is our "everything" server,
including DNS. As far as I can tell, DNS is configured properly.
All Windows clients' DNS settings are served via DHCP, and they all
register themselves in DNS. Pinging Win clients is no problem.
However, there are a few devices (Unix box, AS/400, print server) that
don't broadcast themselves to the DNS server. Since I'd like people
to be able to access these resources via hostname, I've manually
created hostname records in DNS. After doing an IPCONFIG /RELEASE,
/FLUSHDNS, /RENEW, a user can ping these devices. However, if the
user reboots their computer, they can no longer ping these. They can,
however, still ping other Windows clients.
If the user goes and does the IPCONFIG three-step, they can then ping
them again.
What gives?
Thanks,
Rob
OK... this is probably a simple issue, but I don't have time to
troubleshoot it. Here's the scoop...
I've got one Windows 2000 server, which is our "everything" server,
including DNS. As far as I can tell, DNS is configured properly.
All Windows clients' DNS settings are served via DHCP, and they all
register themselves in DNS. Pinging Win clients is no problem.
However, there are a few devices (Unix box, AS/400, print server) that
don't broadcast themselves to the DNS server. Since I'd like people
to be able to access these resources via hostname, I've manually
created hostname records in DNS. After doing an IPCONFIG /RELEASE,
/FLUSHDNS, /RENEW, a user can ping these devices. However, if the
user reboots their computer, they can no longer ping these. They can,
however, still ping other Windows clients.
If the user goes and does the IPCONFIG three-step, they can then ping
them again.
What gives?
Thanks,
Rob