I just tried switching it to that and it fixed the problem. All my other scopes were domain.local. Guess I've just been lucky that nothing to this point has cared in the past 7 years.
-----Original Message----- From: HELP_PC [mailto:g...@enter.it] Sent: Thursday, August 19, 2010 12:28 PM To: NT System Admin Issues Subject: R: DHCP Scope Option Option 15 in DHCP should be domain.local GuidoElia HELPPC -----Messaggio originale----- Da: N Parr [mailto:npar...@mortonind.com] Inviato: giovedì 19 agosto 2010 19.15 A: NT System Admin Issues Oggetto: DHCP Scope Option 15 DNS Domain Name Should it be just domain or domain.local? Or does it not matter? My win clients don't have any issues but I have a terminal client that can ping it's management server by the FQDN but not by machine name alone. And of course it won't work unless it can find it's management server by the machine name. All my win clients can do either. Just trying to figure out anything that would solve this because the vendor has never had this problem before. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
