Either DHCP failed or we were unable to access http://(ip)/fog//index.php for connection testing
![0_1583348843679_DHCP erro FOG.JPG](Enviando 100%)
@kevinnew22 In the scripts we use
curlwhich does work out of the box! I am sure this is a spanning tree issue. I won’t repeat this anymore.
@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 Certo vou fazer outros testes então.
@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.
@Sebastian-Roth a foto abaixo com o comando pedido, sim esta personalizado com NÓ de rede esta com NAS da Seagate.
@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.
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:
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.
I think we have 2 errors here.
- Lets just call it spanning tree that is keeping the target computer from getting an IP address.
- 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?
@george1421 Fiz certo agora, foto com o comando wget e configurações no switch, tenho varios desses switch.
@kevinnew22 Very good the pictures show complete connection.
I think I see what the problem is with your
The error was "bad address ‘http’ "
I see you typed
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.
@george1421 aqui esta a foto do ping, ip addr show e traceroute.
You can ping the fog server at that address but
wgetfails? That is very strange.
Will you show us a picture of this command
ip addr show?
@george1421 Consigo sim
@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.251to see what network route it takes to get to the fog server.
@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.
@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.
wget http://192.168.4.251/fog/index.phpfrom 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 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.