In the absence of a router, which can act as a DHCP relay agent, the only way to make the DHCP server to assign IP addresses is to delete the existing scope and re-create a new scope that contains the IP range, which is in the same subnet as the DHCP server.
However, the exception is that the DHCP server should have multiple NICs, which have IP addresses configured on them and the subnet of those IP addresses should match the subnets configured in the DHCP scope. In this case, a new scope with an IP range of 10.141.232.0/24
is created (the same subnet as the DHCP server), after which the issue was resolved.
The following image illustrates the Wireshark capture, when DHCP leased an IP address to SBR:
In the SBR debug logs, the following messages are displayed:
05/31/2012 07:40:49 User NATIVEGUY being passed to attribute editing authentication methods
05/31/2012 07:40:49 DHCP Requester: Allocated address 10.141.232.100 via DHCP (pool POOL1)
05/31/2012 07:40:49 Class subattribute: DistName : String Value = NATIVEGUY
05/31/2012 07:40:49 Class subattribute: AuthType : String Value = 0
05/31/2012 07:40:49 Class subattribute: IpAddr : String Value = 10.141.232.100:POOL1
05/31/2012 07:40:49 Class subattribute: DhcpInfo : String Value = 000A8DE83E4FC782F100000002,10.141.232.63:67,86000