Server 2008 as dhcp server problems

[Fkacn_tt]

I have setup a workstation with server 2008 to act as a dhcp server for my internal network. The problem is that the dhcp is working perfectly and all clients receive an ip address, but they don't have access to the internet.

The diagram below will help you understand the setup.

WAN---->(Nic 1--MS Server 2008--Nic 2(DHCP))---->Switch---->Clients.

Nic1 config
Static IP
Host IP:192.168.1.102
Gateway:192.168.1.1
Netmask:255.255.255.0

Nic2 config
Static IP
Host IP:192.168.20.111
Gateway:192.168.1.102
Netmask:255.255.255.0

DHCP settings
IP range:192.168.20.1-192.168.20.254
Exclusion range: 192.168.20.1-192.168.20.50
DNS:192.168.20.111
Router: 192.168.1.102

Any help would be greatly appreciated.

[Spazosaurus]

Have you thought about setting up a firewall proxy and use that as the gateway for internet traffic?

[Fkacn_tt]

if it was possible i would not do it this way but the requirements require me to. I have been running wireshark and it seems that it maybe a dns problem, so a new problem to figure out.

[Jarrox]

You need to setup ICS on Nic1 and Remove the gateway from Nic2 and in DHCP put the GW as Nic2.......i think

[Fkacn_tt]

tried that no go.

[Jarrox]

Have you thought about setting up a firewall proxy and use that as the gateway for internet traffic?

This is the best option
but what I said before should work, maybe you missing a step.

[Netizen1]

Windows don't like multiple default gateways. Remove gw on NIC2 as suggested

Is NIC1 connected to a router? Doesn't the router do DHCP?

You have the router in Scope options set to an IP the hosts can't reach

[Fkacn_tt]

Windows don't like multiple default gateways. Remove gw on NIC2 as suggested

I removed the ip of nic1 as the gateway but still their is no connectivity.

Is NIC1 connected to a router? Doesn't the router do DHCP?

I Wish it did but all the ip's are static lease.


You have the router in Scope options set to an IP the hosts can't reach

I have been playing around with the Router IP but still can't connect. I used wireshark on the server and on the client and i saw that the ARP request for hosts on the opposite networks were left unanswered. I many just have to bite the bullet and add a router to be the dhcp server.

[EmperorXavier]

set ur dhcp server to give ur clients the default gateway of your internet link that way your internal network sees the internet (hence the reason it is called a gateway) end result do not use your internal dhcp server as ur default gateway or any internal IPs. can you please tell me which NIC is internal and external (internet)

if you need some help PM your number and we i'll call you we can set this up together over the phone or through a logmein session

=[PT]=

[EmperorXavier]

i also notice that both ur internal and external NICs uses the same IP address this would greatly mess up things please don't do that.
=[PT]=

[MessiaaH]

What alyuh men smoking dread?

That setup will never ever ...EVER work, unless you setup that server as a router.
Presently it have no way for the machines on d internal network, to even know a public network exists. Something has to route d traffic from internal to external.

You can use ICS or NAT, both with specific requirements and setup.

Here are d links:
NAT:
http://support.microsoft.com/kb/816581

ICS:
http://support.microsoft.com/kb/324286

If your internal network has to operate on a specific ip range, you go have to do what capt. awesome recommend, and setup ah seperate firewall/proxy (ISA) to do d magic.

If is a domain environment another option is:

Modem -> Switch
Server Internal -> Switch
Clients -> Switch.

Server DNS forwarder setup -> ISP DNS or Modem.
DHCP Hands Modem as DG, Server as DNS.

But that option, everything on d same network, and d only thing between your machines and d internet is d tstt modem. (Not Safe) But its d easiest option.

[Spazosaurus]

Man buss down some bess options on yuh chest dey. I'd try that nat solution and use rras to assign ips to ur clients.

I know it goes without saying that your wan address would need to be static for any of these options to work long term.

[Arcmanov]

I have done what you require before, but it was in Windows 7, by using the two
NICs to create a network bridge.  The 2nd 'NIC' was in fact, a wireless adapter,
but that is irrelevant.  Any device that connected to the ad-hoc connection would get
internet access.  Swap that wifi adapter with a regular wired NIC, and you essentially
get the same thing.  In your case your 'clients' would get their DHCP settings from the bridge.

[Fkacn_tt]

thanks for all the options guys and a special thanks to you messiah all your suggestions allowed me to broaden my search in which i finally found the solution, kind of.

The solution was to disable RRAS the reable it and redo the NAT, but this time it just seemed to work, even though i selected the same nic for NAT as i did before i.e NIC2.

So again, thanks guys