Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 500
  • Last Modified:

Setting up Windows 2008 Server as a DHCP client

Hi there.
I have the following scenario. I'm running an internal network, as well as a public Internet cafe.
I've got a DSL router, which get assigned a dynamic IP from the ISP, using PPPoE. This router is the main DHCP and DNS server. The wireless router plugs into this router.

Then, I've got an internal network running, that I want to protect from the public users, with Windows Server 2008. The problem that I have is that if I make the server the DHCP and DNS server, the public clients (including those with wireless access) won't be able to use the Internet, unless I set them up first. That's the reason I want to keep the router as the main DHCP and DNS server.

Is there a way that I can use Windows Server 2008 as a DHCP client? The IP address for the server I've made 192.168.0.2, for the router it's 192.168.0.1.
My IP config for the server is: IP: 192.168.0.2, Subnet: 255.255.255.0, Default Gateway: 192.168.0.1, Primary DNS: 192.168.0.1

The error that I'm getting when I try to ping 192.168.0.1 (router) is: Destination not found (192.168.0.2)

Can somebody please give me some thoughts and insights please? Thanks
0
leniyl
Asked:
leniyl
  • 6
  • 3
  • 2
2 Solutions
 
MarcSpencerCommented:
If you've set the IP Address of the Server manually then it doesn't need to be a DHCP client.

If you have set a reservation on the DHCP server then yes the server can be a DHCP client. But i'd recommend setting a manual IP address on the server and setting up a DHCP exclusion range on the router if possible.

From the looks of it it's either a configuration error that you're typed in wrong or a physical network connection error.
0
 
leniylAuthor Commented:
Hi.

I've also made the server a pure DHCP client, by getting the addresses assigned automatically. It receives the corrent information, IP, subnet, gateway, DNS, etc. But when I ping the gateway (router), I get the same error: Destination not found (192.168.0.x - x being the IP of the server)
0
 
sstopsCommented:
Hello,

does your server has only one or multiple NICs, what Roles are configured on the server.

I had once a similar issue where a server had multiple network cards that were by configuration in the same subnet but in fact weren't.
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
leniylAuthor Commented:
Hi there.

The server only have 1 NIC. The only role configured is Active Directory.
0
 
sstopsCommented:
Hi, that's an odd problem.

do you have any firewall software enabled on the server? If so disable it for testing.
Are you able to ping any other PCs or devices on the network?
Did you try pinging the server from the router?

0
 
leniylAuthor Commented:
The server is a clean install. No other software installed. Can't ping anything. Also can't ping from router or clients to server.

It seems to me like the server is using itself as the default gateway, and not the router.
0
 
sstopsCommented:
Even if you have configured the wrong gateway or it is using the wrong gateway it should matter as both address 192.168.0.1 and 192.168.0.2 are on the same subnet so the gateway is not used.

The windows firewall is also disabled? I am just asking because the default settings for Windows Server 2008 firewall are much more retrictive than with past versions.
As I have experienced the oddest things myself, did you try another hardware port on your switch / router?
Can the server ping itself?
And the clients can ping the router?

Do you have access to another switch or hub that you can put between the server and the router. What type is your server nic and router?




0
 
leniylAuthor Commented:
thanks for your advice.

the server can ping itself, and the clients can ping the router.

i'm going to try and change the nic on the server, maybe a diffferent cable and router port, and will report back.

thanks
0
 
leniylAuthor Commented:
changed nic. still same. i've put one client and the server on one switch, without anything else connected.
put in manual addresses for both. same subnet. can't ping one another.
on server i get destination not found (192.168.0.2) - address of server. or request timed out. switches between the two.

is there something that i'm missing in the configuration? should the network work straight after a clean install, without any roles configured?
0
 
MarcSpencerCommented:
Make sure that you disable the built in firewall as this may be blocking ICMP and/or other packets from being received/sent from the server.
0
 
leniylAuthor Commented:
Thanks to everyone involved.

It seems that the 2nd NIC I installed was also faulty. Working fine now after replacing NIC.
0

Featured Post

Become an Android App Developer

Ready to kick start your career in 2018? Learn how to build an Android app in January’s Course of the Month and open the door to new opportunities.

  • 6
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now