Hello,
I've stopped DHCP and DNS on the win2k3 server and made the router works as DHCP and DNS ( ADSL router Dlink DSL-500 ).
Problem is when I try to setup a new computer to be a member of the domain it just fails giving an error that it can't resolve the name, while from the same computer I can access Internet without any problem.
Does this means that the DHCP and DNS servers have to be always on the win2K3 ? Or what ?
By the way current computers which are already a member of the domain logon normally without any problem.

Why did I stoppthe DHCP and DNS on the server, because stoping it on the router didn't allow me to make the router works like a modem only.


Greetings

After a quick look on D-links site Here (http://support.dlink.com/products/view.asp?productid=DSL%2D500),this has been discontinued and, In my opinion, may just be easier to replace than try and trouble shoot.
It maybe something as simple as a incompatablilty with 2k3 and Domains, but as the firmware hasn't been updated since 2001 I would cut and run.

You might want to check the setting on the router, especially DNS. Does your ISP specify a primary and/or second dns server? I am also assuming you have rebooted the server.

Yes, my ISP provide 2 DNS.

OK there's part of your problem, the ISP supplied DNS settings.
This will work fine for external comms, but as they aren't set to recongnise your domain controller you won't be able to join the domain.
Have you tried setting the router DNS to look at your DC's DNS and use your ISP's DNS setting on your DC ?

You shuld still be able to use the router as DHCP server.

Ben is right! (there I said it :D damm that spread reputation thingy) the clients are ignoring the server and going straight out to the internet.

I would definitely use w2k3 as both dhcp and dns, your clients will have severe problems without this. Turn off DHCP on the router, leave DNS as is on the router and use the "forwarders" section in the server properties of the DNS window to specify the router as a dns forwader.

In my opinion the dhcp on win servers is better than the routers anyway as you can specify reservations (effectively static ip's) and also configure the dns server addresses to go out with the DHCP addresses (also should be server ip not router - use with forwarders on server).