Installing 3com boot services causes DHCP service to not start
Kurbycar32
February 25th, 2008
Running server 2003 R2, System runs only as a DHCP and print server. Installing 3com boot services goes without incident and functions perfectly as a PXE/TFTP server. After reboot however the DHCP service fails to start, giving an error about a corrupted DHCP database. If you go manually start the service later it turns right on and works until a reboot. I have this occuring on 2 servers, the only 2 i have the 3com services installed on. ideas?
Filed under: Ghost Solution Suite, Endpoint Management and Virtualization
Hi,
If you disable 3Com PXE and TFTP services, would DHCP start correctly upon reboot?
Krish
no, the service still doesnt start automaticly. if i go manually turn on the DHCP service it starts, and if i start the PXE services they all work properly until reboot. the only thing that made DHCP start properly was completely uninstalling the 3com boot services.
Again, the system specks:
Dell Servers, poweredge 860 & poweredge 2950
2003 Server R2
providing DHCP and print services
mcafee antivirus
The really arent doing much, i dont see what the problem could be
Message Edited by Kurbycar32 on 02-28-2008 07:56 AM
Bumpage..
Hi,
I can't think of any reason why this should happen, I will try if I can re-produce this.
When installing 3Com PXE in the server, did you install it before or after making it a DHCP? Did 3Com PXE added the option 60 or did you have to do it manually?
In the mean time, you can try making the PXE server a dependency service of DHCP as a workaround. This will make sure it is started after DHCP.
Krish
3com services were installed after the machine was an existing DHCP & print server. DHCP option 60 was set automaticly by the software.
Ill try setting it as a dependancy of DHCP.
As a "work around" that actually works much better for me i relocated the PXE service on the ghost server. By entering the IP address of the ghost/PXE server into the value of option 60 on the DHCP server i effectivly relayed all PXE traffic to the seperate server. This works out better because we have multiple DHCP servers, enabling option 60 on all of them would centralize PXE.
Would you like to reply?
Login or Register to post your comment.