philipgecko
asked on
cant see active directory from a newly installed terminal server/slow logging on
Hi there,
I have just introduced a new Windows 2003 terminal server on its own hp box that now connects to a clone server running windows 2000 server. I have noticed that the terminal server takes a while, longer than anticipated, to log on to the main 2000 server (which is the current dc). I have also noticed that when I create a new shared folder on the new server I cannot see any of the domain users in teh active directory, I can see all the pc's through My network Neighborhood and can browse them but the I cannot assign specific user rights.
Do I need to do a dcpromo on this new server or is there another way of speeding up the logging in process and seeing the active directory..?
The main 2000 server is just the dc, runs a proxy mail server called mailgate and shares files. the new server is designed to be just a terminal server running only sage apps and office. the ip range is 10.0.0.x
Any answers would be gratefully received and rewarded with points.
Thanks
Phil
I have just introduced a new Windows 2003 terminal server on its own hp box that now connects to a clone server running windows 2000 server. I have noticed that the terminal server takes a while, longer than anticipated, to log on to the main 2000 server (which is the current dc). I have also noticed that when I create a new shared folder on the new server I cannot see any of the domain users in teh active directory, I can see all the pc's through My network Neighborhood and can browse them but the I cannot assign specific user rights.
Do I need to do a dcpromo on this new server or is there another way of speeding up the logging in process and seeing the active directory..?
The main 2000 server is just the dc, runs a proxy mail server called mailgate and shares files. the new server is designed to be just a terminal server running only sage apps and office. the ip range is 10.0.0.x
Any answers would be gratefully received and rewarded with points.
Thanks
Phil
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The Windows DNS server must point to istelf for DNS...
ASKER
I am unfamiliar with mailgate but it seems that all clients point to 10.0.0.1 as a proxy server and then the actual lan dns points to the ISP's dns servers being 212.159.6.9/10.
When I try and create a forwarder on the dns it is greyed out, so I am stumped. I dont want to touch the active directory at all but what can i do to change the dns on the old server to make the new server connect to it properly..?
When I try and create a forwarder on the dns it is greyed out, so I am stumped. I dont want to touch the active directory at all but what can i do to change the dns on the old server to make the new server connect to it properly..?
ASKER
do you think i should do a dcpromo on the new box and then make the dns point to itself that way?
ASKER
Ok, problem sorted. The old server was in fact a root server, so i deleted the (.) from the forward lookup zone and then created forwarders and pointed the server to itself and hey bingo!! Thanks guys for your help.
ASKER