Solved

NT4 and W2K Servers and TRUSTS

Posted on 2000-03-29
5
414 Views
Last Modified: 2010-05-18
My NT4 server can see my Wk2 Server over my home internal network, but not vice versa. I am just about ready to give up on W2K server because it is so cryptic but I'll stick to it if I can get this working.

Everytime I try to browse my network neighborhood using W2K I can see the various domains but every time I try to expand the NT4 domain it times out and says duplicate name found on network.

Also, just trying to establish a TRUST between the 2 domains is impossible since the neither can "contact" the other.

Any help / pointers would be greatly appreciated.
0
Comment
Question by:rascal
  • 3
  • 2
5 Comments
 
LVL 1

Expert Comment

by:MFalcon
ID: 2671609
I had the same problem until I installed active directory services on Win2K.
ADS is required for trust relationship.
0
 
LVL 1

Author Comment

by:rascal
ID: 2671619
I have that installed and it doesn't seem to make a difference. Interesting that my W2K Server can not view and computers on the NT domain but it can view another W2K workstation.
0
 
LVL 1

Expert Comment

by:MFalcon
ID: 2671867
When you installed, there was a choice that asked if you would be connecting to old NT 4.0 (mixed mode).  Did you choose the Win2K only mode?
0
 
LVL 1

Author Comment

by:rascal
ID: 2672273
I believe so, I could connect to the NT server just a week or so ago. At that time I was in the process of setting up a DNS server on that machine since I host a web site on it. Is it possible I need to add a DNS record of some kind to enable the communication?

The NT 4.0 server can browse the W2K domain and drill down into the machine shares, but not vice versa.

The W2K Server can see the domain but can not drill down into the machine.
0
 
LVL 1

Accepted Solution

by:
MFalcon earned 100 total points
ID: 2676929
If you have Active Directory Services installed, you should set a one way trust relationship.  If the Win2K server is the web server, set the Win2K domain as a trusting domain of the NT domain, and set the NT domain as a trusted domain.
0

Featured Post

MIM Survival Guide for Service Desk Managers

Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you try to share a printer , you may receive one of the following error messages. Error message when you use the Add Printer Wizard to share a printer: Windows could not share your printer. Operation could not be completed (Error 0x000006…
In-place Upgrading Dirsync to Azure AD Connect
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question