Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Failed when conecting to new AD domain

Status
Not open for further replies.
jmartin

jmartin

MIS
Aug 31, 1999
68
PE
I have computers with XP Professional and loaded a new W2000 server with its Active directory. The problem is when this XP client logs to AD. THe first problem is that XP look for and a DNS server and shows a message that ´can´t find a DNS server´ when I didnt installed this. After some tryes other pcs could log on to new domain, it shows the welcome screen ´Welcome to xxxxx domain´. When restart this pc and log on to domain, the result is a extreme slow in this task. Someone tell me it is due a Netbios protocol. After this pc logs and load desktop, when open the network icon and find the server via windows xp ask me logon with its logon screen (username / password). why is the reason for this if the pc had logged to domain? .. what could it be the reason for slow access??
All replys welcome.
 
Sort by date Sort by votes
First is this the only PC with the problem. Also is it the only XP machine on the network. Next you want to verify that your dns server has the appropiate SRV records. Make sure that if you use static ip addresses that the client is pointing to the correct dns server. Because with XP and windows 2000 DNS is the key to being able to authenticate with Domain Controllers
 
Upvote 0 Downvote
Hi ecunupe...
Not..this is not the only pc...there are 6 pcs with windows 98se and this computers works fine...there are only 2 pcs with xp professional and both have the same problem, and my w2000 server doesn´t have a dns server configuration..when i setup active directory with the wizard i choose it setups in automatic...You ask me verify the SRV records...but I dont know where to find this information..All the computers has static IP (192.168.1.xx)What could be the next step? Thanks for your suggest..
 
Upvote 0 Downvote
You need to point the XP clients to the domain controller for their primary DNS server.
 
Upvote 0 Downvote
DNS is required for Active Directory.

When you ran the AD wizard it automatically configured and started DNS on that server.

You need to make sure that DNS server is in your DHCP config.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

rzammit82
  • Locked
  • Question
Windows Server 2016 - DNS/AD problem
Replies
1
Views
905
suncit
suncit
goombawaho
  • Locked
  • Question
Domain join from wifi connected laptop
Replies
4
Views
1K
goombawaho
goombawaho
DTGMI
  • Locked
  • Question
WIN 10 Pro PC & Adding back to our Network
Replies
0
Views
585
DTGMI
DTGMI
MattM1975
  • Locked
  • Question
Domain Admin Logon 1
Replies
2
Views
356
ADB100
ADB100
DrB0b
  • Locked
  • Question
Hybrid on prem AD with Azure AD
Replies
2
Views
398
DrB0b
DrB0b

Part and Inventory Search

Sponsor

Back
Top