Cannot Join Win2K Wkstn to NT 4.0 Domain domain cannot be found.

All:

We have a test enviornment network which has an NT 4.0 domain controller.  Nearly all the workstations in the test enviornment/domain are W2K Pro and XP Pro.  All are joined to the NT 4.0 network with no apparent problems.

We have one W2K machine which was previously on our production enviornment network, but we tried to disjoin it from that domain and join it (for the first time) to a NT 4.0 test enviornment/domain called CSI.

The error I receive is that the domain CSI cannot be found.  However the machine does get an IP address, and I can ping the PDC by netbios name AND IP address.  Yet when trying to join the domain I get the error DOMAIN CSI CANNOT BE FOUND.  

Anyone connecting a W2K or XP box to an NT 4.0 domain knows that this is a common Windows flake, and the work around is usually (in no particular order)...

At Workstation:
Join machine to workgroup
Reboot
Join machine to domain
Reboot

At Server:
Remove Computer account from PDC
Re-add computer account to PDC

Another suggestion was delete the COMPUTER account from the server manager on the PDC, then RE-ADD IT using a different name other than the original.  On the client machine rename it to match the new name/account created on the PDC (so the SAM db would have a new SID for the client machine).  To no avail also.

However even this isn't working.  Right now I'm running a Windows Repair but I don't suspect that will resolve this issue.

Any ideas?  I've also rebooted the PDC and Client machine several times and have been trying nearly all day.  Could this be a WINS issue?  
LVL 2
TheBrothaULuv2H8Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

stevenlewisCommented:
Try adding an lmhosts file and use the #DOM and #PRE tags
info on lmhosts
http://www.realcomputerguy.com/lmhosts.htm
and
http://support.microsoft.com/default.aspx?scid=kb;en-us;314884

>>Could this be a WINS issue
more likely a dns issue
w2k relies heavily on dns
0
TheBrothaULuv2H8Author Commented:
I'm going to give that a shot tommorrow when I'm back in the office.  My question now is once I use LMHOSTS am I going to have to update this everytime I add another machine to the domain?  Or are you providing this as a workaround for the flaky PC.  In other words our setup was working just fine before without us having to update LMHOST files on each machine and I'd really prefer not to have to update these files everytime.  

Here's another question, someone else told me to try deleting the WINS database (which was probably a really stupid idea) but I did =( .  I figured since WINS acts like somewhat of a DNS server that it would automatically rebuild it's data when I log off a workstation and reboot.  Could this be adding to the problem?
0
stevenlewisCommented:
>>Or are you providing this as a workaround for the flaky PC
a workaround for this one
since the other ones work fine, it would appear this is due to the fact that tis box was in an other domain, and is probably looking for that DC
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

TheBrothaULuv2H8Author Commented:
That makes sense, great I can handle a workaround for one PC but I'm very anal, somewhat obsessive compulsive when it comes to things being unorganized.  You know the type, I can let my rice touch my fish when I'm eating, the air in my car is either all the way COLD or all the way HOT.  I think you get the point.

I'll try tommorrow if all goes well I'll increase the points are yours.  Gracias.
0
TheBrothaULuv2H8Author Commented:
Correction, If all goes well the points are yours ...PS:  I've increased them to 300
0
stevenlewisCommented:
LOL, you sound a lot like my real brother *grin*
0
JusnetworxCommented:
Goto a command prompt and type ipconfig /all

Does the DNS Suffix still have the old domain listed?  
0
TheBrothaULuv2H8Author Commented:
Jusnetworx.....yes it does...even though I thought I recall removing the old SUFFIX in the network configuration section.  Where are you going with this one?
0
TheBrothaULuv2H8Author Commented:
LMHOSTS file doesn't seem to be doing the trick either.  Any other suggestions....now the error I'm getting is...

The domain name CSI might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location
(SRV) resource record used to locate a domain controller for domain CSI:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.CSI

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child
zone:

CSI
. (the root zone)

For information about correcting this problem, click Help.
0
TheBrothaULuv2H8Author Commented:
Also, none of the workstations will register with the DC now.
0
stevenlewisCommented:
check  your wins db and make sure it has rebuilt
also please paste the contents of the lmhosts file you created here
0
stevenlewisCommented:
what dns do you have setup on your network?
0
TheBrothaULuv2H8Author Commented:
Stevenlewis...

I rebuilt the WINS database as a result of something I read yesterday and for a while, it was working, I was able to get 2 workstations re-registered on the Network, then I began experiencing the same problem(s) again.  Since the PDC is NT 4.0 (which was running WINS also) and since we can't find the old NT 4.0 disk, I couldn't un-install and re-install the WINS service so I disabled it, and set up another machine on my network to handle WINS.  That resolve the problem.

It's obviously a WINS problem it would be nice if I knew why it was doing it...but we plan on scraping the NT 4.0 DC for a W2K or Win 2003 Small Biz Edition.  Thank you all for your help.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
stevenlewisCommented:
Just glad you got it working!
Steve
0
TheBrothaULuv2H8Author Commented:
Aren't I suppose to close this question?  If so...can someone tell me how.  Since I wasn't able to accept an answer.
0
stevenlewisCommented:
Go here
http://www.experts-exchange.com/Community_Support/
and ask them to PAQ this one
include a link to this question in the body of that one
0
stevenlewisCommented:
I agree :~)
0
YensidModCommented:
Question has been PAQed and 350 points refunded.

YensidMod
Experts Exchange Moderator
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.