Go Back   TechArena Community > Technology > Networking & Security
Become a Member!
Forgot your username/password?
Register Tags Active Topics RSS Search Mark Forums Read SiteMap

Tags: , , ,

Sponsored Links



Failure cause analysis by DHCP server

Networking & Security


Reply
 
Thread Tools Search this Thread
  #1  
Old 14-03-2010
Member
 
Join Date: Feb 2010
Posts: 112
Failure cause analysis by DHCP server

hi all,

In my enterprises, because of the need to save resources or facilities, often on a PC, the deployment of many services, so that the PC, on a part-time more servers Function. Such planning is indeed easier to manage and maintain, but also for the network safe and stable operation of buried potential problems. Once the network fails, the impact of the entire local area network is almost devastating. So i want to know that failure cause analysis by DHCP server.
Reply With Quote
  #2  
Old 14-03-2010
Steve123's Avatar
Member
 
Join Date: Feb 2008
Posts: 2,619
Re: Failure cause analysis by DHCP server

In View exchange machine indicator shows status of normal, no crashes due to congestion resulting phenomenon, then the problem only lies in the DHCP server on the. Next, view the DHCP server, DHCP services on the state, it also shows is also normal, but found server operation response to slow. That is what causes a corresponding DHCP server. Led to a corresponding DHCP server to understand the reasons for slow, we need to look at the working process of DHCP services. If deployed in the LAN DHCP server and the client is set to automatically obtain IP addresses. DHCP client so that when the first time log on the network, that is, the client found that the machine does not have any IP data set, it will send a DHCP discover to the network packet. Check and reply.
Reply With Quote
  #3  
Old 14-03-2010
Milton.J's Avatar
Member
 
Join Date: Apr 2008
Posts: 3,422
Re: Failure cause analysis by DHCP server

The default in the windows by default, DHCP discover the waiting time for default is 1 second, which is when the client will first send out a DHCP discover packet, after 1 not received a response within seconds, they would conduct a second second DHCP discover broadcast. If no response has always been the case, the client will have a total of four times a DHCP discover broadcast (including the first account). In addition to the first time will wait for 1 second, the rest of the waiting time for three seconds, respectively 9,13,16. If you have not received a response from DHCP server, the client will display an error message, declaring DHCP discover failure. Later, based on the user's choice, the system will continue in 5 minutes later to repeat the DHCP discover process. Check and reply.
Reply With Quote
  #4  
Old 14-03-2010
Spyrus's Avatar
Member
 
Join Date: May 2008
Posts: 3,470
Re: Failure cause analysis by DHCP server

When the DHCP server receives DHCP clients broadcast message that it sends to the DHCP client DHCP offer message, in which includes a leased IP address. Once the client receive the DHCP offer message, it will use the server IP address provided. From the DHCP process to analyze the work of students unable to obtain IP address of machine should be the DHCP server does not respond, or DHCP server machine made ring but students did not receive any DHCP server, DHCP offer information on making. After the first test network cable ruled out causes of students due to network hardware, DHCP server machine does not receive the response may be, thus to determine is the DHCP server does not make a normal response. All the best.
Reply With Quote
  #5  
Old 14-03-2010
Snake08's Avatar
Member
 
Join Date: Apr 2008
Posts: 3,328
Re: Failure cause analysis by DHCP server

In testing between the client and the server has a lot of data exchange, these data take up a lot of system resources and network bandwidth, thus creating a DHCP Server the corresponding slow. This has entered a vicious cycle, not only the online examination system does not work, students unable to obtain IP address of machines have no Internet access, but also in the network filled with a large number of repeat request. These spam messages take up a lot of bandwidth, the formation of a network storm. More Coincidentally, this time in the third room there are several systems are being damaged by students during a computer network clone recovery. Servers require a lot of data transfer, thus making the server-side and bus network overload, not only the operating system unable to respond to students in the process of machine issued by the DHCP request. Check and reply.
Reply With Quote
  #6  
Old 14-03-2010
Zachary's Avatar
Member
 
Join Date: Jan 2006
Posts: 3,932
Re: Failure cause analysis by DHCP server

I would say is that the LAN is a complete logic system, it has its own characteristics. Server as a network-enabled core must we have to guarantee its normal work, more than the normal limits and scope of the use of some or the entire network will bring about unintended consequences. Especially for such as the DHCP to provide the best services to the public the underlying servers, not to allow overloading. Because overwhelmed they will strike. All the best.
__________________
90% of everything is crap...except for crap, because crap is 100% crap
Reply With Quote
Reply

  TechArena Community > Technology > Networking & Security


Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "Failure cause analysis by DHCP server"
Thread Thread Starter Forum Replies Last Post
Something wonky with DHCP on Server 2003 after a power failure msk007 Operating Systems 3 26-04-2011 11:30 PM
Dell UltraSharp U2410 Pink or Green Tint Failure Analysis Engunan Monitor & Video Cards 4 29-11-2010 01:39 PM
DHCP Client service does not start because of dependency failure Lanny Lin Windows Vista Network 7 27-11-2010 09:32 PM
DHCP Failure TanujC Technology & Internet 6 02-07-2010 01:18 AM
Migration of DHCP Scopes from 1 DHCP Server to another DHCP Server Tarun Sood Active Directory 4 14-07-2009 06:48 PM


All times are GMT +5.5. The time now is 06:04 AM.