When you move the new vlan, you can not got a new vLan 's membership ip address from DHCP

오랫만에 영어로 글을 올리네요.
다중 VLAN 환경에서 Client를 VLAN간에 이동을 할 경우 DHCP서버에서 IP를 못 가져 오는 경우가 있습니다.

확인 해보면 relay agent의 ip도 잘 받아 오고 있는데 왜 그럴까요?
보통 이 경우는 DHCP를 구성 할 때 VLAN 구간의 IP 영역을 대 영역의 하위 영역으로 포함시킨 경우 발생하게 됩니다. 즉 대 영역을 쓰지 않으면 IP를 잘 받아 옵니다.

[Symptoms]
Your Switch are configured multi vLans and you have 1 DHCP Server (Windows).
DHCP clients across router from DHCP server are unable to get an address from the server.

Through relay agent’s ip address is correct, DHCP sent incorrect ip address (it is same as ex vlans ip address)

This is netmon reply packet from DHCP Server
-DHCP
          -Your IP : 192.168.40.101
          -RelayAgentIP : 192.168.40.1

> DHCP Reply Packet
 

[Solution]
Microsoft suggest like this (http://support.microsoft.com/kb/197197/)

A DHCP server can provide IP addresses to client computers spanning multiple subnets if the router that separates them can act as an RFC 1542 (BOOTP) relay agent.

1. Configure a BOOTP/DHCP Relay Agent on the client segment. This can be the router itself or a Windows NT computer running the DHCP relay service.
2. Configure a DHCP scope to match the network address on the other side of the router where the clients are. Make sure the subnet mask is correct. - Do not configure a default gateway on the DHCP server's NIC such that it is the same address as that of the router supporting the subnet where the clients are. - Do not include that subnet's scope in any superscope that is configured on the DHCP server's LAN segment.
3. Make sure there is only one logical route between the server and the remote clients.

The most frequently caused mistake is including superscope.
If you got a this problem, We should check about superscope.

“Do not include that subnet's scope in any superscope that is configured on the DHCP server's LAN segment.“