Posts made by roee

Thank you all.
I will update in case resolved.
Take care!

Hey guys!

Any other ideas or notions or should I just abandon FOG?

Thanks

@Wayne-Workman

I couldn’t find on VMWare workstation anywhere a DHCP settings, or anything else that might use as DHCP of some sort.
The NIC is set to bridge for sure. see attached file.

@Wayne-Workman

Definitely not. The Windows 7 is the host of the fog server VM.
DHCP is on a dedicated Windows 2008R2 server Dell R620.

The FOG server is installed as a VM hosted on a Windows 7 VMware workstation 12.
IP of the Windows 7 machine is 192.168.1.83.
VM Lan card is set to bridge, I made sure it has comm with dhcp, dns, client and www.

Does that shed some light?

Thanks for the interest you’re taking in this.
I will try to answer all questions.
I don’t have any other PXE service in my network. I did try Acronis but removed it completely along with all components and all dns/dhcp related records. Wjen I tried Acronis I had the same issue, and before I tried the Acronis this DC (DHCP server) was installed fresh.
The client machine is a laptop Dell E7440, boot order is NIC first, when fails it holds until a key is pressed to continue to boot from HDD.
WOL settings were disabled, but I did another boot attempt using the LAN only - same result.
I think the issue is that option 66/67 are ignored and port 4011 is still being used rather then UDP.
DHCP server is 192.168.1.6, client receives 192.168.1.59. FOG servers is 192.168.1.14.

Thanks again!

@Sebastian-Roth

My DHCP server is the 192.168.1.6.
It has option 66 with string 192.168.1.14 which is the Fog server.
192.168.1.59 is the IP address assigned to the client which was trying to boot to PXE.
This pcpap file recorded all my DC (which is also my DHCP server) traffic during the boot of the client machine.
Option 67 is also enabled with parameter undionly.kpxe which I don’t really know what to do with it.

Thanks

Well, did a clean install again.
Option 66 and 67 applied. no option 60.
Still the same thing.
Client receives IP from DHCP but than this error: “PXE-55: ProxyDHCP service did not reply on port 4011”.
Attached pcap file. I didn’t see anything out of the ordinary but I hope you will…
0_1453907925957_pcap.pcapng

thanks a lot you all!

I decided to install the VM and Fog from scratch cause the web interface stopped accepting my login.
I think I messed it up way too much…
Will update.

Thanks guys.

@Sebastian-Roth

Thank you for the reply.
My DHCP server is a Windows 2012R2. I tried setting up the the options but that didn’t cause to any different result.
The fog and dhcp server are on the same subnet.
According to the attached articles, I need to remove option 60, do I keep options 66 and 67?

Hello,

I just installed FOG 1.2, normal setup, dhcp on a different server.
I feel like i’m missing something because when I boot a machine using its NIC it fails to reach PXE with the error “ProxyDHCP service did not reply on port 4011”.
Tried with and without options 60, 66 and 67 - same error.
Fog installation says I need these optoins, Microsoft say I don’t. I’m a bit confused.
Am I missing something?
do I need to upload something? file? is there a FULL guide on how to boot to pxe?

** had the same issue when tried to work with Acronis PXE so its probably a very basic thing that I’m missing.

Thank you