Solved

Server 2012 R2 DHCP

Posted on 2016-08-30
6
54 Views
Last Modified: 2016-09-01
I have a physical server running 2012 R2 (replacing an older server running Server 2003), and I'm trying to use one of the NICs for a Ghost network. The old server runs to an unmanaged switch, and we connect PCs to this network to PXE boot into Ghost. However, we cannot get DHCP to run when connecting the new server to the network, and cannot even ping back and forth. We are disconnecting the cable from the old server and are using a different port on the switch, but we can't get this NIC to communicate with any other machines on the network, much less obtain an IP address. Is there something simple we're missing, i.e. firewall issue, NIC configuration, DHCP configuration, etc?
0
Comment
Question by:maximjon
  • 3
  • 3
6 Comments
 
LVL 21

Expert Comment

by:CompProbSolv
ID: 41777116
What happens if you configure the NIC statically?  Are you able to ping other devices?  That will help you decide if it is a DHCP issue or not.

It sounds as if there is a problem with the NIC, the cable, or the port on the switch.  Do either of the lights on the NIC light up when you connect the cable?  What about the lights on the port on the switch?
0
 

Author Comment

by:maximjon
ID: 41777972
We've actually been able to ping back and forth from a client with a static IP once we tweaked the firewall. The NIC looks okay, and the ports on the client and switch all light up as they should. At this point it definitely looks like a DHCP issue.
0
 
LVL 21

Expert Comment

by:CompProbSolv
ID: 41778359
What is doing DHCP?  Can the server in question ping the DHCP server when using a static IP?  If you would post the results of ipconfig /all from the server in question when configured for a dynamic IP address it would be helpful.
0
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

 

Author Comment

by:maximjon
ID: 41778514
It's a server with Windows Server 2012 R2, with a static IP address running DHCP. Everything looks like it's configured correctly, but we're not sure where to double-check. We're trying to get it to hand out a DHCP address to a client running Windows 7 at this point. There's an unmanaged switch in between, and the server will eventually be used to push Ghost images. We have an older server running Server 2008, which has been able to distribute addresses without any issues. We don't have them on the (very limited) network at the same time, and there are no other devices connected.

If we set a static IP address for the client, it and the server can ping each other. However, when we set the client to DHCP, it gives an APIPA IP address (169.254...) and cannot contact the server.
0
 
LVL 21

Accepted Solution

by:
CompProbSolv earned 500 total points
ID: 41778565
OK.... so I misunderstoodd the original post.

You have set up DHCP on the Server 2012 box and it isn't handing out addresses.  If the workstation has a static address then it can ping the Server.  This says that there are no physical obstacles (bad cable, switch, etc.) to DHCP working properly.

It is almost certainly a setting in the DHCP server configuration on the Server 2012 box.  Are you comfortable that you've set it up correctly?  Have you authorized it?  Do you have it listening on all NICs?

To test if it is a firewall issue, turn off the firewall (temporarily) on the Server and run ipconfig /release
ipconfig /renew
on the workstation and see if it gets an IP address.
0
 

Author Comment

by:maximjon
ID: 41779719
We found the issue, it was a conflict with authorizations within AD, even though this was for a separate LAN. Thanks for pointing us in the right direction!
0

Featured Post

Three Reasons Why Backup is Strategic

Backup is strategic to your business because your data is strategic to your business. Without backup, your business will fail. This white paper explains why it is vital for you to design and immediately execute a backup strategy to protect 100 percent of your data.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Every now and then, Microsoft does something that totally impresses me. It doesn't happen often, but in this case I must say I am thoroughly impressed with Windows Server Backup. One of the long time issues with Windows Backup has been the ability t…
You might have come across a situation when you have Exchange 2013 server in two different sites (Production and DR). After adding the Database copy in ECP console it displays Database copy status unknown for the DR exchange server. Issue is strange…
In this Micro Tutorial viewers will learn how to use Windows Server Backup to create full image of their system. Tutorial shows how to install Windows Server Backup Feature on Windows 2012R2 and how to configure scheduled Bare Metal Recovery backup.…
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

840 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question