DHCP Relay with Windows Server 2008 R2

Hi, We have a Windows 2008R2 DC which is also used as a DHCP server. The users are currently in the same IP range as the DHCP server which is 192.168.1.x. We are in the process of moving our users to a different subnet 10.0.1.x/16. A new VLAN has been created for this purpose on our Nortel switches. DHCP relay has been enabled on the Nortel 5520 and 4550 switches. The test desktops running XP & Windows 7 don't get an IP from the DHCP server although the DHCP server indicates that an IP has been leased to the MAC address of the test desktop. The test desktop is connected through an IP phone which has VLAN tagging. The ports on the switch are tagged with the new VLAN. Is there anything that is being overlooked to get DHCP working for the users on the new subnet?

Who is Participating?
cpcitConnect With a Mentor Author Commented:
Thanks iwaxx. We managed to sort out the issue by using the second NIC on the DHCP server and tagging its port on the switch with "pc" VLAN as default. The desktops are now working fine with DHCP.
The port of your switch must be configured in a specific way to allow tagged trafic (IP Phone) and none-tagged trafic (pc).
On Avaya/Nortel switches, this is done by configuring your port as "Untagged PVID Only", which will tag all your VLANs except one (your pc in your example)

* Configure your port to "Untagged PVID Only" (It must be "tagged" currently)
* Add VLAN "Ip Phone" to your port
* Add VLAN "Pc" to your port
* Configure the PVID of your port to the VLAN "Pc"
* Check the config: both your Pc (with ip static first to test the VLAN config) and your IP Phone must have access to their respective gateway, through the same port.
* Then you can debug the DHCP thing...
cpcitAuthor Commented:
The port on the switch is already configured as "Untagged PVID only" with the default VLAN as "pc". Static IP on the pc works fine, its only the DHCP that is causing a problem.
iwaxxConnect With a Mentor Commented:
I guess you'll have to take a packet capture with Wireshark both on your pc and on the DHCP server, to see if the whole flow is ok.

* Do packets arrive systematically to the DHCP server (It seems yes if a lease is granted, but we must be sure)
* Do Pc receive an answer from the DHCP server ? If not, it maybe a route/VLAN problem on the way back, or a misconfiguration in the DHCP relay.

A packet capture on the pc will definitely to narrow down the problem.
cpcitAuthor Commented:
Solution provided by iwaxx has partially correct although it was not the solution to the problem.
All Courses

From novice to tech pro — start learning today.