Unable to Access 192.168.1.99 after factory reset

Forum|Forum|3 years ago
September 11, 2022
6 replies
36451 views

I have a new Fortigate 60F that I am setting up. I upgraded the firmware to 7.2.1 and then used the web GUI to restore factory settings to give me a fresh base to work from.

After the factory reset, I can see that the 60F is acting as a DHCP on the network, but I have been unable to ping it or access the web GUI to set it up. I don’t have a console cable and it may be difficult for me to get one as I am in a somewhat remote area.

Does anyone have any thoughts on what could be causing this behaviour and/or how it could be resolved? Any assistance greatly appreciated.

FortiGate

Best answer by Caeruleus

Thanks for replying @gfleming. Have just resolved the issue as below.

Was able to connect to have multiple devices receive IPs from the DHCP and none were able to connect to the web-GUI despite trying in multiple browsers.

I was connected via a bridged Wifi connection due to MacBook not having an ethernet port, which may have been the issue but I have no way to confirm now.

I have now managed to get access to the device by using FortiExplorer on my iPhone and connecting to the device via my charging cable in the USB port. Once I got in on the iPhone and changed the subnet configuration everything on the network came to life and I am now able to access via the web-GUI. Literally 8 hours from my office out in the mountains, so really glad this has been solved. Hopefully saves someone else who left civilisation without the proper gear in the future :)

gfleming

Staff

Some obvious questions... have you tried some things like using a different browser or a private browsing tab to rule out caches or weird browser issues?

Do you see the 192.168.1.99 IP in the ARP table?

Have you tried a different device?

Are you directly connected to the FortiGate?

CaeruleusAuthorAnswer

Visitor III

Thanks for replying @gfleming. Have just resolved the issue as below.

Was able to connect to have multiple devices receive IPs from the DHCP and none were able to connect to the web-GUI despite trying in multiple browsers.

I was connected via a bridged Wifi connection due to MacBook not having an ethernet port, which may have been the issue but I have no way to confirm now.

I have now managed to get access to the device by using FortiExplorer on my iPhone and connecting to the device via my charging cable in the USB port. Once I got in on the iPhone and changed the subnet configuration everything on the network came to life and I am now able to access via the web-GUI. Literally 8 hours from my office out in the mountains, so really glad this has been solved. Hopefully saves someone else who left civilisation without the proper gear in the future :)

sllu

New Member

I have the same issue. We are an educational institution and don't have tech support contract. I tried so many ways to connect via web interface to our 60F without any success. I can ping 192.168.1.99, though. Very strange! Any other suggestions? I found these low end Firewall gates not very friendly!

CaeruleusAuthor

Visitor III

@sllu I ended up solving the problem (at least a work around) by reallocating one of the LAN network ports as the WAN port. Works fine now and not using the original WAN port. Still no idea why the marked WAN port didn't work.

bsautner

New Member

I think the real solution is people are trying to browse to 192.168.1.99 and not getting a response despite being able to ping it is that you need to use https: https://192.168.1.99

That drove me crazy for an hour so I thought I'd update the thread.

B

btazbt

New Member

leaving this for others since it comes up first in a search

Try an incognito window and ensure you are explicitly typing https://<IP>