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

[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.

[kevinnew22]

@george1421 1: vou verificar novamente STP, 2: dhcp esta local, tenho Vlans também no meu cenário. exites firewall mas esta liberado os ips para acesso.

[kevinnew22]

@Sebastian-Roth a foto abaixo com o comando pedido, sim esta personalizado com NÓ de rede esta com NAS da Seagate.

[Sebastian Roth]

@kevinnew22 Definitely a spanning tree issue. Try connecting a dumb mini switch in between and I am fairly sure you won’t see that error anymore on that machine.

[kevinnew22]

@Sebastian-Roth Certo vou fazer outros testes então.

[kevinnew22]

@Sebastian-Roth Analisem a foto eu verifiquei que servidor WEB faz a troca automática se eu digitar http://192.168.4.251/fog/index.php para
http://192.168.4.251/fog/management/index.php, e por algum motivo no client do fog nao esta redirecionando anisem a foto por favor .

[Sebastian Roth]

@kevinnew22 In the scripts we use curl which does work out of the box! I am sure this is a spanning tree issue. I won’t repeat this anymore.