Re: FQDN cannot be managed because it is not running Windows NT
- From: "Ace Fekay [MVP Direcrtory Services]" <firstnamelastname@xxxxxxxxxxx>
- Date: Fri, 12 Sep 2008 22:57:22 -0400
In news:55CE7392-5CDA-4178-B409-CB88E876385D@xxxxxxxxxxxxx,
JCCIT <JCCIT@xxxxxxxxxxxxxxxxxxxxxxxxx> requesting assistance, typed the following:
Thanks for responding
In regards to the JCDC02 1005 dsrestor error I reset the password as
outlined in KB 322672?
Yes, that will work.
Port 445 is not blocked on any server or PC but I had to increase the
connection time out and listen timeout
times to their maximum in Solarwinds port scanning to get the
majority to respond correctly.
Interesting. Never seen this problem that I would have needed to make such a change.
For the workstations that are having the problem there is a DNS
record for each in the Forward Lookup table and Reverse Lookup table.
Both are also able to resolve using nslookup and pinging the computer
name. There no enabled firewall on the workstations.
Although when I do a nslookup on the domain I am receiving the
fallowing and am not sure why 10.14.73.38 is showing up it is a DHCP
server on our VOIP VLAN.
C:\>nslookup \\jacksoncountywv.local
Server: jcdc02.jacksoncountywv.local
Address: 10.35.18.211
Name: jacksoncountywv.local
Addresses: 10.35.18.210, 10.35.18.211, 10.14.73.38
It seems that 10.14.73.38 is a DC as well, and if it is, this is normal behavior because each DC will register an LdapIpAddress that looks like:
(same as parent) A 10.14.73.38
It appear to clean this up, AD Sites must be configured. This subnet should be in it's own Site so the machines will not query any DCs outside the site, unless of course all DCs do not respond in it;'s own site and at which case, will look for a DC outside the site. I assume at least one of the DCs on this subnet is a GC.
You are correct in your assumption that the subnet is not bridged to
another VLAN.
This PC taxpc04 is working correctly this today, the only thing that
has been done to try to correct the errors were to reboot both DCs
and both workstations. Assessor06 is still having the same symptoms.
C:\>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : taxpc04
Primary Dns Suffix . . . . . . . : jacksoncountywv.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : jacksoncountywv.local
jacksoncountywv.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : jacksoncountywv.local
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit
Ethernet
Physical Address. . . . . . . . . : 00-16-35-61-07-EF
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.35.18.68
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.35.18.1
DHCP Server . . . . . . . . . . . : 10.35.18.216
DNS Servers . . . . . . . . . . . : 10.35.18.210
10.35.18.211
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : Wednesday, September 10,
2008 8:41:2
8 PM
Lease Expires . . . . . . . . . . : Thursday, September 18,
2008 8:41:28
PM
This looks fine. It may come down to a Site issue. Are AD Sites configured?
Ace
.
- Follow-Ups:
- References:
- FQDN cannot be managed because it is not running Windows NT
- From: JCCIT
- Re: FQDN cannot be managed because it is not running Windows NT
- From: JCCIT
- Re: FQDN cannot be managed because it is not running Windows NT
- From: Ace Fekay [MVP Direcrtory Services]
- Re: FQDN cannot be managed because it is not running Windows NT
- From: JCCIT
- FQDN cannot be managed because it is not running Windows NT
- Prev by Date: Re: Unable to Logon after demoting Domain Server to Workgroup
- Next by Date: Re: Name reference invalid
- Previous by thread: Re: FQDN cannot be managed because it is not running Windows NT
- Next by thread: Re: FQDN cannot be managed because it is not running Windows NT
- Index(es):
Relevant Pages
|
Loading