Cannot read or write files to sync with gdrive

[sli4]

Hello fellow freefilesyncers,
I just set up a new computer with a fresh copy of windows 11 and Freefilesync. I've set up a few systems just like this but on this one I can't transfer any files at all to or from google drive with freefilesync. The drive connects and gives permission when I log in. It scans the google drive fine but upon starting the sync the transfer starts for a second and then the speed drops to 0 without transferring a file. The error I get is:
Cannot write (or read, depending on direction) file "gdrive....", and "CURLE_OPERATION_TIMEDOUT: Operation too slow. Less than 1 bytes/sec transferred the last 30 seconds"
I've tried different variations of access time and retry attempts- as I read in numerous posts here that you need to make it more than 15 seconds.. I don't have an issue with access times on other machines.
I tried disabling the drive lock feature with no change. Ignoring the issue doesn't matter because any files after will also yield the same error.
I've also read other posts stating windows defender was a culprit as it could be blocking ffs but:
I don't use windows defender - I use ESET endpoint security and have ffs added to every exclusion I can find.
I also have two other computers with the exact same version of ESET and it works fine without having to add any exclusions.
Just to be sure I've also disabled all security and the issue persists.
I've tried disconnecting the google account and reconnecting as well as reinstalling ffs and trying the previous version of ffs (I'm updated to the latest).
I can manually upload or download from google drive's website and I have rclone mounts with google drive working fine. (ffs is syncing directly to gdrive - not through the mounts).
ffs works fine attempting the same transfer to or from local drives so it seems to be just when using google drive.

Is there another place that google might be blocking read/write access? I know gdrive has api limits but I can transfer with the same account on other computers fine....or maybe a setting on ffs I'm missing?
Does anyone have any ideas?

Thanks

[sli4]

update: after tinkering with every setting i could possibly think of I went against my will and disabled ipv6 on my network adaptor and it worked again.
So... the issue seems to be ipv6 based? I don't know much about ipv6 but I do notice it causing a ton of issues with google in general.

Has anyone else experienced this with ipv6?

edit: I found a post about a completely different issue someone was experiencing and was able to solve my problem by switching my router's ipv6 wan configuration from dhcpv6-pd to either 'none' or 'static - auto configure'
Very strange since similiar computers on the network were not affected by this and did not have the issue at all.
This fixed everything for my computer but then caused the issues to start on one of the computers that was working fine... so this is not the fix.