• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 194
  • Last Modified:

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
0
philipgecko
Asked:
philipgecko
  • 4
  • 2
2 Solutions
 
philipgeckoAuthor Commented:
I must point out that the old windows 2000 server dns settings are pointing to internet based IP address not itself, perhaps this is the problem..? The new server's dns is pointing to the old server being 10.0.0.1
0
 
NJComputerNetworksCommented:
All clients and member servers must point to the internal Windows DNS server to participate in the domain properly.
0
 
KCTSCommented:
That is the problem. The pereferred DNS server must be that of the domain - normally that of the domain controller. You need to set this. Your own DNS server should have a forwarder set that points to your ISP's DNS server. This way you machine will be able to locate the domain controller and names will be resolved internally first with the ISP's DNS being called on to resolve internet DNS queries.
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
NJComputerNetworksCommented:
The Windows DNS server must point to istelf for DNS...
0
 
philipgeckoAuthor Commented:
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..?
0
 
philipgeckoAuthor Commented:
do you think i should do a dcpromo on the new box and then make the dns point to itself that way?
0
 
philipgeckoAuthor Commented:
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.
0

Featured Post

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now