Two domains sharing resources setup problems

[ccie2b2004]

I have this office with an existing domain I created for the a while back. Now they want to have a secondary domain, but both domains will share internet, firewall, DHCP from the router. I got the new servers for the new domain set up, plug them in, now the new domain server can ping addresses from the old domain, but the old domain servers or PC's cannot ping the new servers IP!!!! So I cannot get the necessary PC to join the new domain because they cannot see the server for the new domain. I have been working at this for several hours. the new server has DNS and Wins configured... nothing. I even tried to set up on the PC I wanted to join the new server, to setup DNS in tcpip properties to be the IP from the new server.... nothing. I tried to set up a trust relationship between the domains, it was created but cannot be verified. I am at a point that I want to jump out of the roof....

Please HELP!!!!

 

[ccie2b2004]

I forgot to mention that all servers are Windows 2003 Enterprise and all PCs are Windows XP Pro

 

[ccie2b2004]

Well, the problem is a bit different now. probably because last night I remove the domain name on the router. So this morning all PC's can ping the new server. So I thought, great, I should be able to joint this PCs (currently joint to the old server), to the new server. But I am getting the error: "The specified server cannot perform the requested operation"

Why not? *&^*#@()@..... sorry, lots of frustration, I only got about 5 hours sleep so far, and all this needs to be ready for tomorrow morning

Also, I forgot to mention: I can ping on any of the PCs (which at this moment all are part of the old domain) with the name of the server, so the name resolution is working correctly. Lastly, My network neighborhood shows both domains, and if you click on the new server, it requests the ID and password, and once it is provided, you gain access to the server!!!! So why I cannot joint any of these PCs to the new domain?

 

[Cstorms]

Have you switched these client machines to a workgroup, deleted the computer account in AD and rejoined them? I am a bit confused at your setup, is this setup a whole new domain with a whole new AD structure? Are your client machines able to login at all? Can you logon locally maybe try clearing the dns cache as they maybe trying to locate srv records on an old dc to authenticate to (ipconfig /flushdns), if you are able to see the new server and you have AD and DNS setup on it you should be ok. Check you dcdiag, and netdiag for any errors as well... Good luck

 

[ccie2b2004]

The new domain is a child domain from the main domain. The server is new, but some existing PC's from the original domain supposed to join this new child domain. I did tried to change the PC to a workgroup, flush DNS cache and tried to join the PC to the child domain. The PC asks for the Id and password, but then I get the error: "The specified server cannot perform the requested operation" The new server has DNS and it replicate from the DNS server from the father domain since I can see all the entries there, including a new one for the child domain.... I run dcdiag and netdiag, in there I noticed and event warning for Netlogon: Event ID: 5781

TCPIP is set up to have as DNS entry first the Father domain DNS server IP and second I have the server itself's IP since that is the DNS server for the child domain. Is this incorrect?

 

[ccie2b2004]

Update: I can still ping the DC for the child domain from any PC but I cannot gain access anymore from a PC. Also, the parent domain DC DNS cannot replicate with the child DNS because it cannot establish connection. It looks like it is getting worse before it gets better.....

 

[dtrtel]

Which DNS servers are being returned by the DHCP
service in your router? Also make sure you only
have one DHCP server configured for your LAN.

My personal rule for small networks is to set up
DHCP on the router but only for roamers. Static
IP is the way to go for servers, workstations
printers etc that don't move.


--jeff

http://linkedin.com/in/JeffLynch