XP Media centre+Server 2003

Chris · **29th May 2008, 10:55 AM**

Have just joined one of my XP Mediacentre machines to a windows server 2003 domain. All went well exept the mediacentre cannot access the internet. I have a telstra broadband modem which connects to a TP-Link R460 router 4 port. I have 5 machines so there is a cheap switch in there as well. I have disabled DHCP on the router and assigned the other machines that are not on the domain with static IP's. Is it possible to configure another nic on the server for the WAN and connect it to the switch? Or is there an easier solution?

vlad · **29th May 2008, 11:37 AM**

You have to setup DNS server within AD, and forward it to your SP DNS server.

Chris · **29th May 2008, 05:07 PM**

Thanks for your reply Vlad. I think I might have do do some more reading. It is the first time I have set up DC's and AD's. I have just had a look and the SP DNS server is forwarded. The server can connect to the Internet alright. I might leave it to the weekend and have another play.

vlad · **29th May 2008, 05:17 PM**

Try to resolve some outside addresses like www.xpmediacentre.com.au from client computer using command prompt and typing nslookup www.xpmediacentre.com.au
What is the DNS server youd AD server is using. You should point it to itself.
Is your DHCP scope configured correctly? does it have default router and DNS server?

Can you resolve name to ip address and type ip address instead of name in web browser.

You need to find out if you have a routing problems or DNS problems.

logifuse · **29th May 2008, 06:57 PM**

In very simplistic terms, any PC in the domain (including the domain controller) should only have the domain controller's IP address as their only DNS server in their network settings.

The domain server must then have the outside ISPs DNS server addresses in the DNS server settings (under administrative tools). You right click on your server from the list (it's the only one) & go to properties & the forwarders tab - you add the external DNS servers there (for all other DNS domains).

Justin

vlad · **29th May 2008, 08:08 PM**

Thanks Justin, it makes more sense than my quick notes during busy working day

Chris, why domain? Supporting domains of stupendous complexity at work I am trying to avoid them at home

Workgroup is not that bad, I am running 2008 server and another 6 computers of mixed XP flavours at home (ask me why as there are only 3 of us here) and workgroup doing just fine.

Chris · **29th May 2008, 08:44 PM**

Thanks for that Justin. I will check what Address I have put in there on the weekend, it must have been the wrong one. Vlad I did know what you where suggesting me to do,your quick notes are better then no notes at all. Why a domain you ask, well I am going to try and get my MCSE certification and I was a bit worried that the reg hack I did to allow xpmedia centre to join a domain was causing the issue.

vlad · **29th May 2008, 09:17 PM**

Quote:

Originally Posted by Chris

I am going to try and get my MCSE certification and I was a bit worried that the reg hack I did to allow xpmedia centre to join a domain was causing the issue.

I thought so, then yes good idea. I was running some domains at home when was learning.
I am still learning, must admit

logifuse · **30th May 2008, 10:40 AM**

Yeah, domains can be tricky beasts - best avoided on a home network if possible.

Just about all my customers have Small Business Servers - they're easy as most (all?) of the domain & DNS set up is handed to you on a plate, but I set up a new Windows 2003 R2 server the other day & had to put everything together from scratch.

It made me realise how easy SBS makes it.

One clarification - you should be able to just put the router's local IP as the external DNS server in the forwarders tab.

Justin

Chris · **30th May 2008, 07:16 PM**

Thanks for the help fellas. The router's local IP did the trick