06-08-2015 08:56 AM - edited 03-08-2019 12:27 AM
I had a failure of my windows 2003 Ad/DHCP/DNS server so I rebuilt on 2008 R2.. Same server address etc. The server is in VLAN 90 and it will hand out addresses in VLAN 90. If I hard code an address in any other vlan, I can ping and connect no problems.
I do not see any errors in the server DHCP log , but the local PC says it cannot contact the DHCP server. All the IP helpers are there. Here is a sample of the vlan interfaces the .20 is the DHCP windows server. The windows server is running on a UCS c220M3 latest COMC coed etc. VMware is 5.1.
I must be missing something but I have no idea what, Any thoughts
interface Vlan100
description Need second helper for ISE
ip address 172.16.100.1 255.255.255.0
ip helper-address 172.16.90.20
ip helper-address 172.16.90.10
!
interface Vlan101
description Need second helper for ISE
ip address 172.16.101.1 255.255.255.0
ip helper-address 172.16.90.20
ip helper-address 172.16.90.10
06-08-2015 09:12 AM
Is your windows server able to ping its default gateway in vlan 90? if not please check the port settings, if you are trunking to the UCS system please ensure that the vlan 90 is being trunked. Create it on the vswitch too, and apply the vnic on the server in the correct vlan.
You should from your switch be able to ping the dhcp server IP. If you cant then dhcp will not work.
06-08-2015 09:20 AM
Thanks for quick reply,, I can set the ip manually or a laptop and I can ping every subnet I have.. I can ping from both side the server side and the laptop side.
I will look at VMWARE as that is the likely spot.. Maybe I missed something,
i know it sounds strange why would manual work and dhcp not especially when I can ping from any where. I even disabled the windows firewall
Yes VLAN is trunked
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide