Domain computer on the network but can't see its own domain

Question

I have one computer that is acting very strangly when working with the domain. I have removed and rejoined this computer to the domain and it found and connected to the domain just fine. but it is unable to see the domain after joining. I am able to do an nslookup on the domain and the correct server responds but the computer itself does not seem to authenticate or see the rest of the domain. I can connect to other file shares for instance but it prompts for a login since it can't authenticate itself.

This computer uses our standard XP image and its just a basic loadout. User accounts are user accounts, only administrator accounts on the machine are the local and domain administrators. Windows Firewall is disabled

I did perform the following commands on it and made sure it was in the right mode.

nbtstat -R
nbtstat -RR
netsh interface ip reset reset.log
netsh winsock reset
ipconfig /flushdns
ipconfig /registerdns

From the command line on the client I an able to lookup the domain, (And the DNS server is one of the DCs so its obviously talking to it.) but that seems to be all I can do with it. One thing too is the domain sees it just fine, I'm connected into it with both VNC and RDP

C:\Documents and Settings\Administrator>nslookup DOMAIN.lan
Server:  SERVER1.DOMAIN.lan
Address:  10.0.0.4

Name:    DOMAIN.lan
Addresses:  10.0.0.4, 10.0.0.147, 10.0.0.15, 10.0.0.11


C:\Documents and Settings\Administrator>nslookup DOMAIN
Server:  SERVER1.DOMAIN.lan
Address:  10.0.0.4

SERVER1.DOMAIN.lan can't find domain: Non-existent domain

C:\Documents and Settings\Administrator>nslookup SERVER1
Server:  SERVER1.DOMAIN.lan
Address:  10.0.0.4

Name:    SERVER1.DOMAIN.lan
Address:  10.0.0.4


C:\Documents and Settings\Administrator>nslookup SERVER1.DOMAIN.lan
Server:  SERVER1.DOMAIN.lan
Address:  10.0.0.4

Name:    SERVER1.DOMAIN.lan
Address:  10.0.0.4


C:\Documents and Settings\Administrator>ping DOMAIN.lan
Ping request could not find host DOMAIN.lan. Please check the name and try
again.

C:\Documents and Settings\Administrator>ping SERVER1

Pinging SERVER1 [10.0.0.4] with 32 bytes of data:

Reply from 10.0.0.4: bytes=32 time<1ms TTL=128
Reply from 10.0.0.4: bytes=32 time<1ms TTL=128
Reply from 10.0.0.4: bytes=32 time<1ms TTL=128
Reply from 10.0.0.4: bytes=32 time<1ms TTL=128

Ping statistics for 10.0.0.4:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Documents and Settings\Administrator>ping DOMAIN.lan
Ping request could not find host DOMAIN.lan. Please check the name and try
again.

C:\Documents and Settings\Administrator>ping SERVER1.DOMAIN.lan
Ping request could not find host SERVER1.DOMAIN.lan. Please check the name and try
again.

The ipconfig looks like it should, its getting all the information although I'm a little curious as to why the domain shows up twice in the DNS Suffix Search list.

C:\Documents and Settings\Administrator>ipconfig /all

Windows IP Configuration

    Host Name . . . . . . . . . . . . : COMPUTER8862
    Primary Dns Suffix  . . . . . . . : DOMAIN.lan
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : DOMAIN.lan
                                        DOMAIN.lan

Ethernet adapter Local Area Connection:

    Connection-specific DNS Suffix  . : DOMAIN.lan
    Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connection
    Physical Address. . . . . . . . . : 34-CD-B2-9C-43-FA
    Dhcp Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IP Address. . . . . . . . . . . . : 10.0.0.118
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 10.0.0.254
    DHCP Server . . . . . . . . . . . : 10.0.0.4
    DNS Servers . . . . . . . . . . . : 10.0.0.4
                                        10.0.0.147
    Primary WINS Server . . . . . . . : 10.0.0.4
    Secondary WINS Server . . . . . . : 10.0.0.2
    Lease Obtained. . . . . . . . . . : Monday, October 25, 2010 8:06:10 AM
    Lease Expires . . . . . . . . . . : Monday, October 25, 2010 10:06:10 AM

I've been unable to find anything on it and giving it one last day before I just reimage the machine again.

Answer 1

I saw this once before. All of the tests you ran worked, but it still couldn't pull down the group policies. NSlookup worked just fine, it could talk to and resolve the DCs just fine. And yet, no policies.

What ended up being the problem was the "TCP/IP NetBIOS Helper Service" was turned off for some reason. This setting came from the image, as it happened, so the image had to be re-baked, but it worked just fine once enabled.

Answer 2

Go into device manager and uninstall the NIC card(s), and then reboot and try again. Sometimes the networking components get messed up, and that should reset everything.

Answer 3

When you remove from the domain, try going one step further and delete the Computer account from AD. Let AD replicate and retry the domain join.

Answer 4

Perhaps having some more info would help.

1. Does the client obtain the IP address via DHCP? If so, try manually assigning the IP. If the ip is manually assigned, make sure the subnet mask matches that of the server/domain.

2. Is DNS Active Directory Integrated? More than one DC? If so, have they replicated all the info to one another? Do all the _KPASSWD,_KERBEROS,_ldap records exist in DNS for the correct DC?

3. Try plugging in a different network card and see if it could be a hardware issue related to that.

4. Does the client see any other machines on the network i.e. clients and other domain controller(s)/member servers? What about the other way around? Do other machines see this one?

Answer 5

Finally just ended up replacing the computer and reimaging it.