Damon was famously dumped by Williams while he was champion.
Apparently Frank had decided to replace him with HHF long before that, but any insight as to why Frank wanted him gone?
He had been runner up in the championship multiple times by then, the performance was clearly there.
Was it just a pay dispute? or was there a personal conflict? or?
Been running v13 for a while now. The console performance was always slow and seems to only be getting worse.
On boot it can take upwards of 15 minutes for the web services to start, and it takes a few more minutes after that before the console will start to respond and log in.
Once in it's slow and clunky.
Any performance tips?
Is this everyone? Is Veeam working on this?
We have 2 internet connections terminated to our firewall with spare IPs, and SD-WAN is already configured outbound for load-balance/failover.
We have a specific outbound service (SMTP) that we want to attach to a dedicated outbound IP address.
Setting an outbound NAT policy with an IP Pool was easy enough, and that's working, but we only have it setup for one of the internet connections at the moment.
How can we set this up with a dedicated outbound IP for each internet connection and have it failover if the main internet connection goes offline? (active/passive)
Had a call today from a new client that users couldn't access their servers. We got brought in recently because they were unhappy with the previous IT provider and are quickly figuring out why...
Hadn't had much of a chance to poke around there yet, but nothing like a trial by fire right?
Head down there, and everything looks ok at a glance until I realize that the desktops are on a different subnet than the servers and they can't ping through.
Ok, so routing problem, no big deal. Where's the firewall?
Oh there isn't one... it's 2 different cable models plugged directly into the switches.
What we thought was the router is actually a 10 year old gamer router that's being used as a ghetto wireless AP and is sitting next to their rinky-dink UPS that isn't even plugged in.
After an hour of trying to untangle the spaghetti we discover an unmanaged switch in the back room that has 3 network drops plugged into it creating a loop. Cleared that up, and that at least kinda gets the internet working.
Then we discover that each modem has a unique IP range, and one of those is Public IP space for another continent. Oddly though as we test release/renewing we find 3 subnets with DHCP, not just 2.
That's when they told us that the server in question was actually in another building nearby.
That building has its own 2 modems in the same kinda config with a bunch of daisy chained unmanaged Best Buy switches. At some point they decided they needed connectivity between the two buildings and spun up a Ubiquiti PtP and bridged both buildings directly to the existing switches on both sides. So there's actually 4 unique networks all on the same flat switches.
Turns out all the servers and industrial controllers have static IPs. Desktop wise whenever something didn't work they were told by the previous IT people to just keep rebooting until they presumably got a DHCP lease from the correct network and stuff started to work.
After some digging with the users we find out there had been a power outage so all the devices dynamic IPs had changed. Since the internet had stopped working they called the ISP to figure that out and their techs had come down and just started unplugging cables until they got something to work.
A while later when the staff realized the servers didn't work they started to panic and moved around a bunch of cables themselves, plugging in cables that were previously dangling out of the wall assuming that was the problem.
shakes head slowly and painfully
Now that I got all this mess working again with duct tape and bailing wire, you'll have to excuse me while I go back in there like Hank Scorpio with a flame thrower and gleefully burn this network down and start over.
Firewalls started dropping all connections today until we rebooted.
Fortigate 120G in HA stack
Logs show:
NAT port exhaustion
We have a single WAN IP for guest wifi + staff networks.
We've dropped the default NAT timers down from 1 hour to 5 minutes.
config system session-ttl
set default 300
Reviewing this guide:
https://community.fortinet.com/fortigate-3/technical-tip-avoid-nat-port-exhaustion-172790
Trying to assign a dedicated VIP to our Guest Wifi to drop the number of connections.
Any other options or ideas we should be aware of?
EDIT:
By default Fortgates have only 24,000 ports available for NAT
Default:
set ip-src-port-range 1024-25000
Change to:
set ip-src-port-range 1024-65000
That was part of the issue.
The longer term fix was to assign a dedicated WAN IP to our Guest Wifi to get that traffic onto a different public IP and NAT pool.
We also applied a DOS policy to limit the number of sessions per device on the Guest wifi in case one of the devices was rogue and using up tons of sessions.
Getting this error on a brand new Hyper-V host.
7/11/2026 9:06:35 PM :: Unable to allocate processing resources. Error: On-host proxy [SERVERNAME] requires upgrade before it can be used.
Host doesn't show a need to upgrade the on-host services.
Services version numbers match a healthy host.
I restarted the services, removed and re-add the services, even removed and re-added the host to Veeam but same error.
Any ideas?
Have to wait for Monday to put in a ticket.
Trying to configure the dedicated management port on our firewall to be accessible from another subnet. We need to apply a couple static routes for the interface to route to a downstream layer 3 switch. But when we try to apply the routes the required commands don't appear to exist in the CLI?
The mgmt port is effectively default other than us having changed the IP address on it. It isn't in its own VDOM or anything, but my understanding is that Fortinet by default treats the MGMT port as it's own VRF so it has it's own dedicated routing table? or is that untrue?
Found this in the documentation to apply static routes to MGMT interface but the command set device mgmt doesn't exist in the CLI?
config router static
edit 0
set dst <destination-ip/subnet>
set device mgmt
set gateway <management-gateway-ip>
next
end
What are we missing here?
Taking over an SMB that has all their IP cameras exposed directly to the web. Not going to leave it that way obviously.
Typically I'd move the cameras to their own isolated network and force users to VPN in to access, but the owner is being stubborn.
The boss insists on being able to access the cameras on demand from his cellphone, but also came to us to beef up their security because he got hacked. You can't have it both ways dude...
There's a VPN client for his phone, but before I go down that route wondering if anyone has any other tricks of the trade for dealing with remote access for cameras and NVRs in SMB?
Currently running a pair of older Cisco SMB switches with 24x 10gb ethernet that we are looking at replacing.
Looks like they've discontinued these switches and there's no equivalent in the C1200/C1300 range...
What has everyone been using for 10gb Ethernet switches?
Do we need to go up to enterprise class switches now? that's going to blow our budget.
Was re-listening to The Fragile in the car today and thinking that the Day the World Went Away is said to be about Trent's reaction to his grandmothers death (who raised him after his parents divorce)
The lyrics to me are about getting that phone call that you know will happen but you never want to get.
I just realized the vocalizations at the end are "Nana"
Struggling to get our fortilink switches to be able to see our servers for RADIUS + NAC.
We've added firewall policies from Fortilink > servers LAN to allow the traffic but we can't SSH to the switches and the switches can't see or ping any of the servers.
Are we missing something basic here?
It feels like the Fortigate refuses to route traffic in and out of the fortilink subnet by default.
Fixed: The interface for the Fortilink isn't available as an option in the GUI, it's only available in cmdline. What appears as '_default Fortilink' in the gui isn't the actual Fortilink interface.
As the title says, what's your favorite superstition in IT?
Don't speak the servers name... it can hear you and will start acting up.
User is reporting getting disconnected from NetExtender ever 10-15 minutes. Client reconnects automatically.
Client is latest version.
Firewall log shows his session as constantly active for the past 200 minutes.
His internet seems ok, constant ping test shows no drops.
NetExtender Log on the client shows disconnect and reconnect events, but just gives a generic error.
Anyone else run into this?
Back in the day I remember having to disable IPv6 on the network adapter but that was ages ago and older version.
We're starting the process of converting our 4-node vSAN cluster to Hyper-V.
Our support contract is expiring, etc etc
We're going to be running Hyper-V as 4 hosts with standalone storage, we've moved most of our production workloads to SaaS/Cloud already so our VM footprint is a lot smaller and we're willing to take the risk of not having a SAN anymore.
Unfortunately this also means it isn't in the budget to replace any of the hardware so we have to convert them over 1:1
The plan is to leverage a temporary 5th swing server to add some capacity.
Convert as many VMs as we can to Hyper-V on server #5, then take down 1 vSAN node at a time and reformat them to Hyper-V and continue the conversions until the remaining vSAN nodes are depopulated at which point we'll reformat them to Hyper-V.
With 4 nodes, how many can we take offline before it's a problem?
Can we run a healthy cluster with just 2? or do we need to have 3?
Is it better to properly decommission and remove a node? or Just shut it down and leave the cluster as is? ...given that we are decommissioning it anyway.
If something goes catastrophically wrong in the process, we have Veeam backups of everything. We'll just reformat the vSAN hosts to Hyper-V and restore the VMs.
Firewall logs are spamming the error:
'credential auditor file download failed'
Device has internet access and DNS is resolving correctly. Any idea how i can clear the error and download this DB?
Found a few other posts on this, but there were for obsolete firmware versions
Trying to connect 2 distinct sites together using a Point-to-Point wireless device.
There's a Gate and Fortiswitches + APs on both sides, totally independent of each other.
The PtP is plugged into LAN ports on Fortiswitches on both sides, and is just a regular VLAN trunk. So it effectively just acts as a long (but wireless) ethernet cable.
However when we bring the PtP up the Gate discovers the Fortiswitches on the other side (and vice versa) and tries to register them. The interface also switches to 'Fortilink' mode and loses all the VLANs we configured.
Is there a quick way to disable Fortilink discovery on a physical interface? or on that entire VLAN?
We have a dedicated Management network and Fortilink network, there's no need to register Fortilink devices on our LAN for example.
Will be replacing our Firewall soon with a different brand but hit a snag, we also have FortiAPs and have to keep the Fortigate as a wifi controller for the foreseeable future.
The APs are on the standard LAN network (not a Fortilink) and get DHCP addresses
If I change the LAN IP of the Gate will the APs phone home and find the Gate ok? or will I have to reconfigure them?
Setting up a net new IPSEC VPN instance and we need to perform user based access control.
Restricting what users can access what services based on group membership. Restricting access by destination IP + ACL is fine for what we are looking to accomplish.
We are running IPSEC VPN with SAML auth with Okta
Wondering what our options are to implement something like this?