Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
Do i need DHCP running on my server so my other xp machine can join the Domain?
At this moment DNS is runing and DHCP is installed but not runing. I can ping the XP machine from the Server and ping the server from the XP machine.
When i trie to join the domain it says Domain not found.
The server is promoted as a DC
PLS help
You should be able to join the xp machine to the 2003 domain if you have the domain setup correctly, have you setup active directory etc.. I currently have my network running behind a router and that hands out the DHCP while leaving the server on a static offcourse, If the XP machine is receiving an ip from somwhere (DHCP on the server, DHCP on a router, Staticly, whatever, etc....) and the domain is correctly setup then they should connect, but which version of 2003 are you running, if it is small buisness server then to join it to the domain you must do <serverip>/connectcomputer or <server-netbios-name>/connectcomputer into a browser or the run menu etc..
Hope this helps some
0 
You need to configure your client with the DNS server that contains the domain's DNS records.
Please help survivors of Hurricane Katrina.
www.redcross.org
0
Thanks
I am using 2003 Enterprise Edition
Server has static ip. I have dsl so i have dsl modem and liknsys router WRT54G.
What other ways exept the Properties of My Computer can you join a domain?
0
Appologies if im being ignorant but what dose joining a computer to a domain have to do with DNS ON the server the server automaticaly resolves netbios names, It is after all possible to run a domain without a DNS server using an external one. As far as I know DNS should have no impact on joining clients to a domain. Dont mean to shoot you down in flames so If im wrong i appologise, could you elaborate a little.
0
2003 Enterprise edition just uses the standard My computer properties as u say, to join computers to the domain. What is the actual name of your domain? Also and this is a long shot i have experienced this on windows 2000 server with 200 clients, computers simply wouldnt join the domain, but would join the domain by inputting the first part of it (eg domain = temp.com) joining temp.com domain wouldnt work but joining just temp would and the computer would end up on temp.com
also note make sure the computer your joining, isnt allready on a domain, if it is take it off, reboot then join, this is just a m$ problem that one.
Not sure if all of that is relivent but I hope its edgining you closer to solving your problem.
0
I had the same problem at the last before on a Domain with 2000 servers.
At this moment i need to go home and apply some of the stuff that you told me.
I am looged on remotely to my server at this moment and i can ping the Xp machine but i can't log on remotely from work to my server and after to the XP pro machine. I don't know if that is even possible.
Anyway if i still have a question i will post tonight or tomorrow.Thanks for your help
0
That is possible actualy, XP has its own version of RDP on it, enabiling it from the my computer properties (remote tab) will allow you to login to it from the server using the standard RDC Program (note its not EXACTLY the same as the one in 2003 it will lock the XP machine) but never the less that will allow you to access the machine from the server providing the xp machine allows the server thru its firewall, Obviously u cant play with this till you get home thou.
Good luck
One word questions will always receive one word answers.
0
"As far as I know DNS should have no impact on joining clients to a domain."
How does a client know which computers are domain controllers on the network? Hint: NetBIOS broadcasts don't say anything about whether a node is a domain controller. ;-)
"It is after all possible to run a domain without a DNS server using an external one."
AD specifically relies on DNS as a core service. When a client authenticates, it does a DNS lookup for service records that tell what are the DC's in the client's domain. And what do you have to do when joining a client to an AD domain? Authenticate with a domain account that has rights to add computers to the domain. ;-)
To use an external DNS server, that DNS server must be able to resolve DNS queries for the service records and A records of the domain controllers. Typically external DNS servers hosting domain resource records is an incredibly bad idea, since hackers could then find out rather easily what servers to attack to breach the domain.
Bottom line, if the client is configured without a DNS server that contains the proper DNS records for the domain, the client will not be able to connect to the domain.
Please help survivors of Hurricane Katrina.
www.redcross.org
0
Yes yes, ur right, my bad I was mumbiling in my mind somthing about netbios lookup but offcourse your domain wouldnt function correctly without a DNS Server. Aint called DomainNS for nothing :)
ps. centauri how did u get on?
One word questions will always receive one word answers.
0
NT4 domains don't require DNS...
Please help survivors of Hurricane Katrina!
www.redcross.org
0
It works fine.
After 13 hours being from one job to an other going home and having you workstation join the domain it just makes you happy.
Thanks guys.
I've worked before only on 2000 server and 2000 advanced server, this one was a little pain.
Thanks
0  |
 logging on troubles
|
Deploy/Assign Network Con...
|
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
