up vote 0 down vote favorite
share [g+] share [fb]

I'm trying to setup a home server (to tinker with) as a domain controller. I've setup the domain and I've installed DHCP and setup a scope without any exclusions (with the default range of 192.168.0.1-254).

My client machine is a Windows 7 (RC) machine and it has a connection but can't get an IP address.

Even if I try setting the IP to a static 192.168.0.2 and there is still no connectivity. I can ping it from the server, but pinging the server from the client just times out.

The only thing between the server and the client is a 24 port switch (D-Link DES-1024D).

edit> Ok, it turned out that the interfaces were setup backwards in the NAT settings (the internal nic connection was set to public and the external nic connection was set to private).

I changed this and all was OK.... sort-of.

Problem is now: If I set a static ip on the client (where I am typing this from) all is fine. BUT; when I set it to get it from DHCP, I get a correct IP from the server (192.168.0.2) but there is no internet on the client; but I can still ping the server fine from the client (which makes sense cause I was able to get an IP from it).

edit> I ended up just removing the Routing and DHCP server roles and just going with ICS for the time being until I get my hands on some better learning tools.

link|improve this question
76% accept rate
This sounds like a NAP problem, if you're not familiar with it, read: capitalhead.com/articles/… – l0c0b0x Oct 10 '09 at 16:28
Just to confirm, you have authorised the DHCP server, right? – Sam♦ Oct 10 '09 at 22:20
@Sam: I have. But see my edit please. – SnOrfus Oct 10 '09 at 23:20
Dumb question perhaps, but did you setup the DNS Server options in the DHCP Server ? – Entity_Razer Mar 18 '10 at 7:59
feedback

closed as off topic by MDMarra, voretaq7♦ Mar 7 at 2:32

Questions on Server Fault are expected to generally relate to servers, networking, or desktop infrastructure, within the scope defined in the faq.

5 Answers

up vote 0 down vote

You could use Windows 7's "Network and Internet Troubleshooting" > "Network Adapter"

You can open the window from Control Panel > "Troubleshooting" or using this command on the command prompt:

msdt.exe -id NetworkDiagnosticsNetworkAdapter

Depending on your hardware configuration, you'll have to select the network adapter to diagnose (wireless or LAN). Just click Next and wait for Windows finishing the analysis.

link|improve this answer
I did that and all it came up with was 'not a valid ip address for local area network connection' – SnOrfus Oct 10 '09 at 21:36
feedback
up vote 0 down vote

Try turning off the firewall on Windows 7 and see if it helps. Also, some AV programs have an additional firewall that will block your access to the server. I just had this problem with Trend AV running on Vista.

link|improve this answer
I turned off the windows firewall for all locations, with no results. – SnOrfus Oct 10 '09 at 21:35
feedback
up vote 0 down vote

I see you did resolve the issue with the DHCP server not handing out addresses; good. You problem now seems to be only in Internet connectivity for the client, while the client and the server can otherwise talk to each other. Am I right?

About this: did you configure the client to use the server's internal IP address as its default gateway (either statically or via DHCP)?

link|improve this answer
When I set the IP on the client statically, I do set the server's internal IP as the gateway. I'll try it with DHCP, but that's ideally not what I'd like. I'd prefer to just create the computer/account in AD on the server and have the client just set its computer name to that and allow logins from and AD user account. – SnOrfus Oct 11 '09 at 0:34
Unfortunately, no dice setting the gateway to the server. No internet (so no change from regular DHCP). – SnOrfus Oct 11 '09 at 0:43
feedback
up vote 0 down vote

What IP address range is the server external NIC getting?

If that's already a 192.168.x.x address, you may find double NAT is giving you problems. Move the internal address range to one of the other private IP address ranges would resolve this.

link|improve this answer
feedback
up vote 0 down vote

Problem is now: If I set a static ip on the client (where I am typing this from) all is fine. BUT; when I set it to get it from DHCP, I get a correct IP from the server (192.168.0.2) but there is no internet on the client; but I can still ping the server fine from the client (which makes sense cause I was able to get an IP from it).

Your answer is very simple, you need to configure the Scope Option.

Click on the Scope Option, double click router, enter the IP address of your router :) Ensure your DNS IP address is correct (it should be pointing to the server itself).

The best way to troubleshoot is on the client machine type is "ipconfig /all", you need to see the gateway IP address as the router, and ensure you can ping the gateway, that's the missing part...

Remember the DHCP hands out more then just an IP address, it contains various important information.

link|improve this answer
feedback

Not the answer you're looking for? Browse other questions tagged or ask your own question.