Discussion Locked

Win 2K Server in NT4 Domain 1000 pts!!

0 helpful
14 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I just installed a Win 2K server in my windows domain. I want to use it as my proxy server running Proxy 2.0 (no money in budget for ISA). My problem is that I cannot get my NT4 DNS to synchronize with my Win 2K server. I can log into the network from the 2K server, but none of the other machines can access the shared drives on the new server, nor can they get to the internet. How do I get this machine to allow the Primary controller to sync with it so that the other computers have internet access. I need my Exchange server to get to the internet.

Please help.....Thanks, Pat

14 replies

by joseph moore

I have a few questions, since your setup is not clear to me.
Did you join the Win2K server to the NT4 domain? Or did you run DCPROMO on the Win2K server so it would be a Domain Controller in its own domain? I can't tell from your description where the Win2K box is.
So, right-click on My Computer on the Win2K box, choose Properties -> Network Identification tab.
What does it say there?
Clearing this out will help.

by joseph moore

Ok, when you add the Win2K server to your NT4 domain, did you get an error message, or did it work?
Right click My Computer -> Properties -> Network Identification tab. What does it say under Domain? Is it the name of your NT4 domain?

Also, what machine name does the Win2K server have? Is it the same as any other machine in Server Manager on the NT4 PDC, even a machine you no longer have?
For example, if you had SERVER27 in the past as a NT4 domain member, then you got rid of the server, but the entry is still in Server Manager (it would be a light grey colour), then you will have problems setting up a new server with the same name. I think you would be able to add the new machine (with the SERVER27 machinename) to the domain successfully, but everytime you tried to access domain resources from it or try and connect to it from another domain member, you get error messages. This is due to the fact that the SID the old SERVER27 had would be different from the SID this new SERVER27 has. And since you would have a SID conflict, the domain trust between machine and domain would fail.

by patrick horn

The 2000 Server is being added to an NT domain. I don't want it in it's own domain. The problem is the 2000 Server doesn't trust the other computers on the network.

by cedrictrappeniers

is the new 2k server defined as gateway on the clients? or if you are using some autoscript(dhcp) you might need to adapt it?
hope this helps...

by timwalsh

Not sure I understand totally. What on the Win2K server are you trying to synch your NT4 DNS to?

A Win2K server cannot act as a domain controller of any kind in an NT4 domain. If you ran dcpromo in an attempt to create a "BDC", things are already botched. Your best bet is to wipe the drive and start again from scratch.

Once Win2K is working correctly, you need to join the Win2K server to the NT4 domain.

by tictag

ASSUMPTIONS
1. You have a Win2k member server and you have joined it to an NT domain.
2. You have a primary DNS zone on the NT4 server.
3. By *syncing* you mean zone transfers between NT4 DNS and Win2K DNS.

NT4/WIN2K DNS
- Win2k can hold resource records that NT4 DNS servers are not aware of. They can transfer zones but see http://support.microsoft.com/default.aspx?scid=kb;en-us;203009 for conditions.
- NT4 servers and clients do not need DNS to function, WINS maybe but not DNS. If you want to use DNS to resolve Internet addresses why not just use Win2K (caching only) DNS on the proxy server. I presume this would be your Internet gateway anyway.

SHARED DRIVES
- I?m not 100% on this one but check to see that the NT4 Domain Users group is a member of the Win2K Users local group.
- Ensure you have NetBIOS enabled on your Win2K adapter
- Ensure you have File and Print sharing enabled on your Win2K adapter
- Can you even see the server in a NET VIEW \\ command?
- Permissions? Try NET USE * \\\C$ /USER: to rule out logged on user permission issues.
- Prove resolution issues by replacing names with the IP address

CLIENT PROXY INTERNET ACCESS
- Ensure you have configured your clients (by whatever mechanism) for the proxy server address and port (e.g. 192.168.0.10, port 8080)
- Instead of using MS Proxy 2.0 why not use the inbuilt (and free) Routing and Remote Access Service (RRAS) on Win2K Server? There?s even a wizard to install an Internet connection proxy service (NAT).

I hope some of this helps,
Tictag.

This discussion is closed to new replies.