Server 2003 help!!

[TheGuy]

OK! i turned off the firewall on a xp box and the server could ping it - so could the other pc`s as well, but still cant add it to the domain
Does this mean that i need to disable the firewall on all the pc`s?

Windows Firewall won't block a request to join a domain.

 

[Spazmatic]

make sure all the svr records are created in DNS, the correct A names NS etc etc.

 

[The_Unbeliever]

Make sure that the DNS IP's (on the workstations) all point towards the new server's IP.

For example, if your server's IP is 192.168.20.1 then the DNS IP's on the workstations must point to 192.168.20.1

If the DNS IP is something different, then that's your problem.

 

[Yoda]

turn of any av or firewalls on server and pc's as they could block your pings, double check your ip setting ie subnet mask df gateway.
make sure windows file and print sharing is on all servers and pc's and check wins and dns settings try adding them manually.

 

[The_Unbeliever]

make sure all the svr records are created in DNS, the correct A names NS etc etc.

And that as well.

W2k3 server can be a pain in the **** when it decides to follow its own head. By default the "Create Domain Wizard" does everything, but the chance for borkage still is there.

 

[quik1]

What antivirus software are you running - and is this also running a firewall which ties into the domain?

Client pc`s have MS security essentials and the server has norton

 

[The_Unbeliever]

Client pc`s have MS security essentials and the server has norton

That issue has been resolved.

Now it's a DNS issue. :erm:

 

[Spazmatic]

has your server got a firewall on, if so is it not maybe blocking the DNS requests from the clients, just a thought.

 

[quik1]

Gave the server a new ip. Client dns is pointing server ip now. Flushed dns. Still getting a domain controller cannot be found error

 

[Spazmatic]

Gave the server a new ip. Client dns is pointing server ip now. Flushed dns. Still getting a domain controller cannot be found error

Hmmm, not normally a good idea, you need to check your DNS records if they are correct, if a NS record is wrong it can cause you headaches, etc.

PS. Did you check on your firewall that exceptions have been created for incoming connections on port 53 and the other AD protocols?

 

[quik1]

Must i just remove the DC and then run the setup again?

 

[Spazmatic]

just do what I suggested, it could be a simple solution.

If it is just a record in DNS, easy fix, if its just a matter of opening a port on your firewall, again easy fix.

 

[The_Unbeliever]

Gave the server a new ip. Client dns is pointing server ip now. Flushed dns. Still getting a domain controller cannot be found error

Bleh.

 

[The_Unbeliever]

just do what I suggested, it could be a simple solution.

If it is just a record in DNS, easy fix, if its just a matter of opening a port on your firewall, again easy fix.

Do this first.

 

[PsyWulf]

I have a trick for this specific issue

It's usually related to DNS where they request for a DC named xxx. When the DNS request fails they can't join the domain. To bypass this,configure the DHCP server to serve a WINS address - the DC's IP and install WINS on the DC. Every pc should be able to join fine

 

[Yoda]

go to dos prompt and do a nslookup to cnn.com as an example do you get a return or not

 

[quik1]

I am abit confused here. What should i try next

 

[Spazmatic]

The WINS suggestion is a work around, but doesnt fix DNS.

Check your DNS entries and check the firewall on the server.

 

[PsyWulf]

Somebody who hit this type of snag with DNS isn't likely to fix it quickly

The WINS workaround would serve his requirements till he can fix the DNS or get someone to fix it for him

Do this:

To bypass this,configure the DHCP server to serve a WINS address - the DC's IP and install WINS on the DC. Every pc should be able to join fine

Then get the PCs joined and working,then resume diagnosing the DNS with a test PC

 

[quik1]

I cant find any of the things you guys mentioned?