Windows XP/Pro can not conneect to NT 4.0 domain

[Guest]

Problem Description: The problem is that I can not connect this computer to
our Windows NT 4.0 domain. This computer came installed with Windows XP Home.
I upgraded it to Windows XP Professional/SP2. I CAN browse the network and I
can see the other machines on the network, but I can neither see nor connect
to the domain controller (NT 4) machine. Oddly enough, though, I CAN ping the
server.

In an effort to fix the problem, I added NETBUI protocol - which helped only
in so much as I can now see additional machines on the network. I also read
an article that implied that "NodeType" could be the problem, so I added that
key to the registry, so not the NodeType is 'Hybrid'. I also added an LMHOSTS
entry ('ping server' now works). I also forced the machine to NOT
be a Master Browser.

I suspect the problem is a DNS issue BUT: The NT Server has not been acting
as a DNS server nor it is a WINS server -- It's a fairly OLD machine and it
is touchy enough to make me want to avoid adding any new services to it.
(I'm under the impression that the LMHOSTS file will suffice to resolve the
name...) One last thing that I tried was that I added the DNS suffix
(cable.rcn.com) to this (XP) machine, since ipconfig reports such a suffix on
the server. This changed nothing.

Any ideas??

Here is the report if ipconfig/all:

Windows IP Configuration

Host Name . . . . . . . . . . . . : JakeLap
Primary Dns Suffix . . . . . . . : cable.rcn.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : cable.rcn.com
cable.rcn.com
rcn.com

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . : cable.rcn.com
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG Networ
Connection
Physical Address. . . . . . . . . : 00-0E-35-24-AF-08
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.118
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 207.172.3.8
207.172.3.9
Primary WINS Server . . . . . . . : 192.168.1.115
Lease Obtained. . . . . . . . . . : Thursday, August 12, 2004 4:48:12 P

Lease Expires . . . . . . . . . . : Friday, August 13, 2004 4:48:12 PM

Problem Area: Can't connect to the network
Frequency of problem: Always Happens
Operating system / version:
Computer manufacturer and model:
Processor model and speed:
Memory (RAM): MB

 

[adrian916]

have you tried adding an entry under DNS servers in the
LAN properties to point to a dns server on your network
which holds a record for the domain controller.

I've had several occaisions where a machine can ping the
DC and recognises itself as having a machine acccount but
still says it can't find a domain controller! - adding
the dns server under LAN properties has always overcome
this. (Ihave to say though, that in every case, the DC
has also been the DNS server -so a different situation to
yours)

 

[Doug Sherman [MVP]]

Not clear whether XP machine is joined to the NT4.0 domain. If not, try
joining with the NetBIOS name of the NT domain - you should create the
computer account in Server Manager on the domain controller first.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP