Deployed SSIS package has access denied to file directories and work fine in VS

I’ve tested a couple of things out with different packages that have been deployed to SQL Server. I noticed that within the same package, I can have a script task which fails to connect to a file directory but I don’t have an issue with connecting a flat file data source task to the same directory. If I use a flat file destination task, that fails also. It sounds like something doesn’t have full permissions because the flat file source task just reads the file without issue. I run this in VS and there are no problems. when I check the logs of the deployed package it shows my id as the Executed As Name and the Caller Name. The network guys say that the ids being used have read/write access.