An outsite is running a simple router on a stick configuration and has a dhcp pool configured corresponding to the subinterface connected to vlan 10. User computers reside in vlan 10.
Everything functions correctly except for ifthe local admin tries to boot a computer from a PXE server. When attempting it, the computer is assigned an IP address from the local DHCP scope but the process fails there. Our configurations are below:
Routing
-interface G0/2.10: 10.100.58.190 255.255.255.240
DHCP pool configuration:
network 10.100.58.174 255.255.255.240
default-router 10.100.58.190
domain-name XXXXXX
dns server XXXXXXX
option 66 ip 10.100.210.8
option 60 ascii PXE
option 67 smsboot\x64\wdsnbp.com
ip forward-protocol udp 4011 (applied in global config).
Since there is a local DHCP scope that includes int G0/2.10, we did not need the ip helper-address command on that interface. However, once we added the PXE configuration, we added the ip helper-address pointing to the PXE server onto G0/2.10.
Also, we added the ip forward-protocol udp 4011 command to the global configuration so that the sub-interface would forward the PXE traffic as well. I applied an inbound ACL so I could track the hits for that UDP port and I haven't seen any so far. Lastly, I verified connectivity exists between the vlan 10 subnet and the PXE server by doing an extended ping.
I only have a background in networking and I am not smart on SCCM and PXE, so I'm trying to at least rule out a networking configuration error before I get with the SCCM guy.
