Setup: Broadband Business Cable>Cable Modem>Linksys Wireless Router>Primary Domain Server>50 Port Switch>25 Client Win XP Pro Router has the ISP’s Static IP settings given to me, i.e., IP, subnet, gateway, DNS, DNS. I have disabled the Nat and DHCP within the router. Also included in the router is 10.0.0.1 for local IP. 255.255.255.0, etc. Server has been configured with Active Directory, DHCP, DNS. IP Settings for Server: (Default from MS Support online) IP: 10.0.0.2 SubNet: 255.0.0.0 DefGat: 10.0.0.1 DNS: 127.0.0.1 I am able to Logon a new Client machine and it takes the settings well receiving within the range I chose. The only problem I am having is the clients not getting internet access and clients can’t reach the router home page. Server can do both. The client I tested on has administration rights. I would do away with the router had I not needed wireless, but some feel they can’t do without. Am I not setting something up right from what you can see? Is the router the problem? If I need to supply more info, let me know. Thanks in advance, Chris

I see 2 things. One is the DNS can't be 127.0.0.1 It should be the the IP address of the server or the ISP's DNSes. Secondly, you have a class C subnet mask on the router, which is correct and a class A subnet mask on the server. Shouldn't both of them be 255.255.255.0 ?

u r using private IP address within your network; which mean u need to enable NAT. Private address cannot access the internet. another problem is the DNS IP address. 127.0.0.1 is a loopback address; which mean you cannot use that to assign to the DNS server. donever

"I have disabled the Nat... within the router" Boy you don't just make one mistake but many! Diabling nat means no network translation which means you are bridging. Not only did you disable the protection of NAT but now you have nothing between you and the internet. You opened pandora's box. Re-engage NAT ASAP Imagine the power of knowing how to internet search http://www.lib.berkeley.edu/Teachin...

“I see 2 things. One is the DNS can't be 127.0.0.1 It should be the the IP address of the server or the ISP's DNSes. “ My ISP gave me the set of addresses to use, and I put that in the router. Microsoft gave me the 127.0.0.1 to put in the server. I was under the assumption the router can’t have identical addresses to the server. I’ll look into this. “Secondly, you have a class C subnet mask on the router, which is correct and a class A subnet mask on the server. Shouldn't both of them be 255.255.255.0 ? “ Again, Microsoft Support said to use 255.0.0.0 for the server. However, I forgot to mention I did change this to 255.255.255.0 on the server already so this is the setting. ------------- "u r using private IP address within your network; which mean u need to enable NAT. Private address cannot access the internet." Thanks, I will check into this. "another problem is the DNS IP address. 127.0.0.1 is a loopback address; which mean you cannot use that to assign to the DNS server." Again, I will check into this ----------------- “Boy you don't just make one mistake but many!” Thanks for the observation.:) “Diabling nat means no network translation which means you are bridging. Not only did you disable the protection of NAT but now you have nothing between you and the internet.” I disabled on the router, should this not be correct I if I enable it on my server? (2xNIC’s) “You opened pandora's box.” Good thing it’s not connected to the net yet huh? (not even physicaly wired) “Re-engage NAT ASAP” I shall look into this, Thanks ----------------------- I appreciate the help guys. Tomorrow will hopefully bring good results. Go easy on me, I’m self taught, and learning as I go. :)

On the LAN side, all subnet mask's need to be the same. If you have a router, I wouldn't waste my time doing NAT on the server and I'd get rid of the second NIC on it....just not necessary. Plus, allowing the router to do your NAT removes a service from your DC and that's not a bad thing. I'd probably enable DHCP on the router as well and remove that service from the DC as well. When doing dcpromo to create your DC it's ok to use the localhost/loopback address internally on the server (ie: 127.0.0.1) but all other clients must point at the server's IP for their DNS (ie: 10.0.0.2). It is worth noting though that you can put 10.0.0.2 in for your DNS address on the server, this won't cause any problems as both are not only correct, they are also valid. Once you have DNS configured correctly internally, in order to get resolution for external zones you must forward your server's DNS to the DNS address(es) of your ISP. So look up forwarding and have a look at the interface, it's pretty simple to figure out.

Curt R Thank you, that sounds so helpful. If I understood right, here is what I did. Changed the DC Servers DNS from 127.0.0.1 to the DC Servers IP Address, 10.0.0.2 I forwarded the DC Servers DNS to the IPS's DNS. The addresses I used are the 2 addresses I have set up in the router which were the DNS addresses my ISP gave me when I asked for all the Static IP info. Is this correct? I also enabled the NAT and DHCP on the router and disabled the 2nd NIC on the server. (I disabled the DHCP as well on the server.) I have to find a good spot in the day where everyone will gripe the least when I disconnect the old server and router and test this on the net to see if this will work, but if I have heard you correctly, and it looks to you I have done exactly what you said to do, I’m confident this will work. If you see any error in what I have said I did, let me know as when I shut down the old system for testing the new, I want it to take the least time possible. Thanks again, Chris