Either DHCP failed or we were unable to access http://(ip)/fog//index.php for connection testing

[kevinnew22]

@george1421 tenho maquinas mais velhas tipo Dell 790 que tambem ocorre o erro, mas se eu uso o FOG local funciona, so nao funciona quando passa pela vpn!, pode me ajudar?

[george1421]

@kevinnew22 Ah OK. Everything works except from remote site across the VPN.

What is the IP address of the FOG server?

Looking at your picture I see uhdcpc trying 3 times sending a discover but no response from your dhcp server. This makes me things that this computer is plugged into a network switch port that is running STP (standard) and not RSTP or port-fast.

We can try to debug this if you have a IT technician that can touch the keyboard on this computer over the VPN.

[kevinnew22]

Qual é o endereço IP do servidor FOG?
192.168.4.251
Podemos tentar depurar isso se você tiver um técnico de TI que possa tocar o teclado neste computador pela VPN. Tenho Sim

[george1421]

@kevinnew22 I will write the debugging steps now. I will return in about 5 minutes.

[george1421]

@kevinnew22 If you have a running capture or deploy task for the target computer, stop it.

1. If the target computer is not registered in FOG. Manually register the computer using the FOG web user interface. You will need to know the MAC address of the target computer.
2. Schedule a new deploy task, but before you press the Schedule Task button, select the Debug option then press the Schedule Task button. You can either select deploy or capture it will not matter since we will run in debug mode and will not capture or deploy now.
3. PXE boot the target computer. You will see the same error message about the network as you see the first time, but now you can pass this error. You will see 3 screens of english text that you will need to clear by pressing the enter key. After the last screen is cleared you will be at a linux command prompt. This is the FOS Linux command prompt.
4. Key in ip addr show to get the name of the network adapter. If you are using the Dell 7070 then from your picture the network interface name is eno1. IF you are using the 790 then the name may be different. In the ip addr show output look to see if the target computer finds an IP address from dhcp.
5. If no IP address is assigned, wait 60 seconds. Then issue this command /sbin/udhcpc -i <iface_name> --now You will need the network interface name you collected from the ip addr show command. If you are testing on the Dell 7070 then the command should look like /sbin/udhcpc -i eno1 --now Does the target computer get an IP address now?

If the answer is NO, then we need to see a picture of the results from this command lspci -nn|grep -i net I need to see the numbers in the square braces. As an example the numbers look like this [8086:1fc2]. But I make that number up and its not real.

[Sebastian Roth]

@kevinnew22 Is spanning tree enabled on the switch where the machine is connected to? Normal STP (spanning tree protocol) or RSTP?

[kevinnew22]

@Sebastian-Roth Sim ja verifiquei obrigado.

[kevinnew22]

@george1421 Bom dia,
O computador pegou o ip logo apos o comando estarei colocando o print, em anexo, qual é próximo passo? desde ja agradeço.

[kevinnew22]

@george1421

[Sebastian Roth]

@kevinnew22 Try wget http://192.168.4.251/fog/index.php from that command line. Take another picture and post here.

This is definitely a spanning tree issue from what we see in the picture! No IP on boot but DHCP picks up one when running a bit later.

[george1421]

@kevinnew22 I agree with Sebastian that it is a problem with your network switch it time fixes the problem.

When you boot no IP address, wait 60 seconds and then query for dhcp and get IP address. This is a flag that says original spanning tree is used.

Another test would be to placed a very inexpensive (cheap) unmanaged switch between the pxe booting computer and the building network switch. If that fixes the problem then it is positive a spanning tree issue. You will need to turn on portfast or RSTP on those network ports.

[kevinnew22]

@Sebastian-Roth Boa tarde, fiz alguns testes aqui tenho outra maquina na filial que possui um linux instalado, nela consigo baixar a pagina, mas no cliente Fog não.

[george1421]

@kevinnew22 Can you ping the fog server [192.168.4.251] from this computer?

I don’t know if that target computer has traceroute command but try too traceroute 192.168.4.251 to see what network route it takes to get to the fog server.

[kevinnew22]

@george1421 Consigo sim

[george1421]

@kevinnew22 hmmm…
You can ping the fog server at that address but wget fails? That is very strange.

Will you show us a picture of this command ip addr show?

[kevinnew22]

@george1421 aqui esta a foto do ping, ip addr show e traceroute.

[george1421]

@kevinnew22 Very good the pictures show complete connection.

I think I see what the problem is with your wget check.

The error was "bad address ‘http’ "
I see you typed http|//192.168.4.251/fog/index.php
Look at the pipe symbol ( | ) after the http instead of the colon ( : ) that should be there. That is why the wget was not happy. My guess is that the wget will work.

You are back to the problem that time fixes your network connection on this target computer. Please have your networking group look at the switch port this target computer is connected to. Make sure that RSTP is enabled.

[kevinnew22]

@george1421 Fiz certo agora, foto com o comando wget e configurações no switch, tenho varios desses switch.

[george1421]

@kevinnew22 said in Either DHCP failed or we were unable to access http://(ip)/fog//index.php for connection testing:

I think we have 2 errors here.

1. Lets just call it spanning tree that is keeping the target computer from getting an IP address.
2. The wget command.

For number 1
Do you have an unmanaged switch you can connect the target computer to and then connect the unmanaged switch to the building network switch. I see that RSTP is enabled, but for some reason its not working.

Is the dhcp server at the remote site?

For number 2
The wget command should respond with success. Is there some kind of firewall on the vpn tunnel that might stop http traffic but allow pings?

[Sebastian Roth]

@george1421 @kevinnew22 Seems like the wget commmand behaves a bit strange. I have just tried myself and it’s somehow awkward. Lets better try using curl:

curl -Ikfs http://192.168.4.251/fog/index.php

Possibly there is some kind of webfilter or firewall between the host machine and your FOG server? Both are on different subnets.

As well I just noticed that you seem to have another node in your network as one of the pictures shows: storage=192.168.0.151:/shares/fog/

So there is a lot more than you’ve actually told us about. It seems to be a customized and more complex setup and we can’t properly help you if we don’t know all the details.