All -
Please forgive me if this is an easy one. I'm an application developer, not a network guy, and I'mtrying to help out one of my clients.
They have a very small Win2K network - 4 workstations plus a digital printer attached and using active directory on one server. The IP addresses are statically assigned. On trying to add a new WinXP workstation to the domain, I'm getting DNS name resolution errors. On the server, for the computer object, I've noticed that the "DNS Name" field is not populated as it is for other workstations. Could this be the source of my issue, or is this field populated when a workstation successfully connects to the domain?
The domain is not a single-label domain; another user in another forum suggested a fix for that scenario. I'm drawing at straws here - the other workstations joined the domain with very little effort. This one is not at all behaving.
Please help - I'll be happy to provide any further details that may be necessary in diagnosing the issue.
Thanks,
Tim
Please forgive me if this is an easy one. I'm an application developer, not a network guy, and I'mtrying to help out one of my clients.
They have a very small Win2K network - 4 workstations plus a digital printer attached and using active directory on one server. The IP addresses are statically assigned. On trying to add a new WinXP workstation to the domain, I'm getting DNS name resolution errors. On the server, for the computer object, I've noticed that the "DNS Name" field is not populated as it is for other workstations. Could this be the source of my issue, or is this field populated when a workstation successfully connects to the domain?
The domain is not a single-label domain; another user in another forum suggested a fix for that scenario. I'm drawing at straws here - the other workstations joined the domain with very little effort. This one is not at all behaving.
Please help - I'll be happy to provide any further details that may be necessary in diagnosing the issue.
Thanks,
Tim