You are getting a complaint from one of your client machine that he is not able to communicate with server. you checked the dhcp server and it is running wjat could be the reason
Answers
Answered by
0
it means the client is playing a prank with you.Jokes apart here's your ANSWER
This behavior may be caused by one of the following scenarios:
Scenario1
Changed IP address on DHCP server and now clients cannot get IP addresses.
Scenario2
DHCP clients across router from DHCP server are unable to get an address from the server.
Scenario3
Multiple DHCP servers exist on the LAN.
To resolve each possible cause, use one of these solutions:
Solution for Scenario1
A DHCP server can only service requests for a scope whose network ID is the same as the network ID of its IP address.
Make sure that the server's IP address falls in the same IP network ID as the scope it is servicing. For example, a server with IP address in the192.168.0.0 network cannot assign addresses from a scope like10.0.0.0, unless superscoping is used.
Solution for Scenario2
A DHCP server can provide IP addresses to client computers spanning multiple subnets if the router that separates them can act as an RFC1542 (BOOTP) relay agent.
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.
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.
Make sure there is only one logical route between the server and the remote clients.
Solution for Scenario3
Make sure that you do not configure multiple DHCP servers on the same LAN with overlapping scopes.
In case of Small Business Server, the DHCP service will automatically stop when it detects another DHCP server on the LAN.
This behavior may be caused by one of the following scenarios:
Scenario1
Changed IP address on DHCP server and now clients cannot get IP addresses.
Scenario2
DHCP clients across router from DHCP server are unable to get an address from the server.
Scenario3
Multiple DHCP servers exist on the LAN.
To resolve each possible cause, use one of these solutions:
Solution for Scenario1
A DHCP server can only service requests for a scope whose network ID is the same as the network ID of its IP address.
Make sure that the server's IP address falls in the same IP network ID as the scope it is servicing. For example, a server with IP address in the192.168.0.0 network cannot assign addresses from a scope like10.0.0.0, unless superscoping is used.
Solution for Scenario2
A DHCP server can provide IP addresses to client computers spanning multiple subnets if the router that separates them can act as an RFC1542 (BOOTP) relay agent.
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.
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.
Make sure there is only one logical route between the server and the remote clients.
Solution for Scenario3
Make sure that you do not configure multiple DHCP servers on the same LAN with overlapping scopes.
In case of Small Business Server, the DHCP service will automatically stop when it detects another DHCP server on the LAN.
Similar questions