New Member

Question

Networking Printer speed became very slow from Branch VPN 30E to HQ 80C

Forum|Forum|8 years ago
February 1, 2018
4 replies
7383 views

Dear Guru,

Our company has 5 branches, which are all using Fortigate VPN firewall connection.

HQ-80C 192.168.1.x

Branch1-30E 192.168.2.x

Branch2-30E 192.168.3.x

Branch3-30E 192.168.4.x

Branch4-30E 192.168.5.x

Recently, after the HQ firewall restarted due to power shutdown, we have encountered an issue, the branches stuffs send a print job from their branch to another branch, (for example, print from 192.168.2.21 to 192.168.1.15)the connection speed became very slow, ususally should reach to 200kbs, and now only 30bps... (the ISP speed is upto 1000MPS)

Appreicate if you can reply asap, as we had struggling for few days..

Thanks.

SGeoAuthor

New Member

Dear Gurus,

Anybody help?

ede_pfau

SuperUser

hi,

and welcome to the forums.

This is wild guessing but maybe the internal flash has been corrupted by the power outage. This would matter if you use the 80C for explicit proxying, for instance.

Anyway, if you agree to this theory you could do the following to fix it:

- save a backup of the current configuration (un-encrypted, that is, in clear text)

- prepare to rebuild the flash: get the image file for the firmware you are using, get a TFTP server and a serial connection to the 80C (putty will do, or Hyperterm); connect a notebook to port1/internal via TP cable

- in the CLI via serial: login, "exec reboot" and interrupt the boot process by hitting a key

- F format the disk (this will erase the firmware, the config and all logs!!!)

- load the firmware image using the TFTP server

- boot up the FGT, log in via WebGUI as 'admin' / no password on 192.168.1.99

- restore your config from backup file

- reboot and you're where you took off

This will of course cause noticable downtime. If you don't feel confident to follow this procedure then please get professional help from a Fortinet partner.

Be aware that the config file will NOT contain any certificates which you may have imported yourself! e.g. for IPsec VPN, SSLVPN, admin access etc.

SGeoAuthor

New Member

Dear ede,

Thanks for your reply and support.

This is wild guessing but maybe the internal flash has been corrupted by the power outage. -- Yes, I think so. - save a backup of the current configuration (un-encrypted, that is, in clear text)

-- Thanks for the details of the steps, however, if I even cannot get a backup file, how should I do for this situation?

I found that after the fortigate reboot again, I could get the backup file by click the 'Backup' Button, at this moment, the fortigate just UP for few minutes only. However, I tried to do this again after Fortigate UP for 1 days, the status backup to hanging there, and I could seen the circle rounding at the top of the browser tab only...

I am not sure this is becuase of the hardware issue or software OS issue? the current version is 'v4.0,build0521,120313 (MR3 Patch 6)'

I have attached pic from 80C dashboard, it shows many fields are expired or unlicensed, is this the root causes for the above issues that I mentioned?

Could you advise what is the best way to resolve it?

Appreciated your help and advise, thanks.

- prepare to rebuild the flash: get the image file for the firmware you are using, get a TFTP server and a serial connection to the 80C (putty will do, or Hyperterm); connect a notebook to port1/internal via TP cable - in the CLI via serial: login, "exec reboot" and interrupt the boot process by hitting a key - F format the disk (this will erase the firmware, the config and all logs!!!) - load the firmware image using the TFTP server - boot up the FGT, log in via WebGUI as 'admin' / no password on 192.168.1.99 - restore your config from backup file - reboot and you're where you took off This will of course cause noticable downtime. If you don't feel confident to follow this procedure then please get professional help from a Fortinet partner. Be aware that the config file will NOT contain any certificates which you may have imported yourself! e.g. for IPsec VPN, SSLVPN, admin access etc.

VPN_HQ_dashboard20180212.jpg

Sign up

Login with SSO

Login to the community

Login with SSO