Access to pandey is denied Network type is OnPremise IP: fe80::603a:ba7:ae5e:9ba0%13

Question

Access to pandey is denied Network type is OnPremise IP: fe80::603a:ba7:ae5e:9ba0%13

pandey munna 0

User's image

Pilladi Padma Sai Manisha 7,985 Reputation points Microsoft External Staff Moderator

2026-05-15T11:29:01.9133333+00:00

Hi
Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

3 answers

Your answer

Pilladi Padma Sai Manisha 7,985 Reputation points Microsoft External Staff Moderator

2026-05-15T11:29:01.9133333+00:00

Hi
Following up to see if the below answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 1

Hello Pandey !

Thank you for posting on MS Learn Q&A.

ADF is trying to reach pandey but it resolves to an on-prem addressfe80::603a:ba7:ae5e:9ba0%13 and that is not reachable from the default AIR.

For an on prem machine, local PC, VM or file share, you must use a SHIR.

After you install it on pandey or on another machine in the same network, in the linked service you must set connect via integration runtime to that SHIR. The file system linked service uses connectVia to decide which IR connects to the source.

If the folder is on the same machine where SHIR is installed, run PowerShell as admin on the SHIR machine:

cd "C:\Program Files\Microsoft Integration Runtime\5.0\Shared"
.\dmgcmd.exe -EnableLocalMachineAccess
.\dmgcmd.exe -DisableLocalFolderPathValidation
.\dmgcmd.exe -Restart

Answer 2

AI answer

The error indicates that the on-premises runtime (network type OnPremise, IP shown as a link-local IPv6 address) cannot reach the target resource “pandey” over the network, or that the target is rejecting access.

Based on similar “access denied” and network-plane issues in the context, the following checks and fixes apply:

Verify basic network connectivity from the self-hosted integration runtime (SHIR) machine to the target:
- From the SHIR server, ping or nslookup the hostname pandey.
- If DNS does not resolve, add or correct the DNS entry (on-prem DNS or hosts file) so that pandey resolves to the correct IPv4/IPv6 address.
- Ensure the SHIR is not using only a link-local IPv6 (like fe80::...) path that cannot route to the target.
Check firewalls, ACLs, and routing between SHIR and pandey:
- Confirm that required ports for the target system are open (for example, 1433 for SQL Server, 445 for SMB, etc., depending on what “pandey” is).
- Ensure no network ACLs or perimeter firewalls are blocking the SHIR subnet from reaching pandey.
- If Private Link or managed private endpoints are used, validate routing and DNS so traffic goes over the correct private path, not the public internet.
Validate access control on the target resource:
- Confirm that the account used by the Data Factory linked service has permission to access pandey (for example, SQL login, Windows/AD account, or service account).
- Check for policies like “Deny access from network” or “Deny access to this computer from the network” that might block the account, similar to the “user account is not allowed the Network Login type” scenario.
If using Private Link / private endpoints to reach Azure resources from on-prem:
- Verify that the private endpoint connection is approved and in a Succeeded state.
- Confirm DNS for the Azure resource resolves to the private endpoint IP, not a public IP.
- Use tools like nslookup or Test-NetConnection from the SHIR machine to confirm the path.
If the error is coming from an Azure PaaS resource (for example, Key Vault, Storage, App Configuration):
- Check that public network access and firewall rules allow the SHIR’s public IP or that a private endpoint is configured and reachable.
- For “IP address rejected” / 403 scenarios, ensure the request originates from within the allowed virtual network or via the configured private endpoint and that DNS points to the private IP.
Re-test from the SHIR host:
- After fixing DNS, firewall, and permissions, re-run the Data Factory pipeline or linked service test connection.
- If it still fails, capture the exact error message and HTTP status (for PaaS targets) or OS-level error (for on-prem targets) to narrow whether it is network, authentication, or authorization.

These steps align with how similar “access denied” and network-plane errors are resolved for other Azure services when using private endpoints or restricted network access.

References:

AI-generated content may be incorrect. Read our transparency notes for more information.

Answer 3

Hi pandey munna,
it looks like you’re hitting the built-in security control on the File System connector in a Self-Hosted Integration Runtime (SHIR). By default, local file-system access is blocked (“network type is OnPremise”), so your path (“pandey”) is refused. Here’s how to fix it:

Enable local file‐system access on your SHIR
- Option A: PowerShell (Az.DataFactory module)
```
     Install-Module Az.DataFactory

     Connect-AzAccount

     Set-AzDataFactoryV2IntegrationRuntime `

       -ResourceGroupName <YourRG> `

       -DataFactoryName <YourADF> `

       -Name <YourSHIRName> `

       -Properties @{ enableLocalFileSystemAccess = "True" }
```
- Option B: Edit the host.json on your SHIR node (usually under “C:\Program Files\Microsoft Integration Runtime\4.0\host”) • Add or update "allowLocalFileSystemAccess": true • Restart the “Azure Integration Runtime” Windows service.
Verify Windows-level permissions Make sure the Windows account running the SHIR service has read/write rights to the folder you’re pointing your linked service at.
Re-test the linked service and re-run your pipeline The “Access to pandey is denied” message should go away.

References

• Troubleshoot File System connector (enable local FS access)

https://learn.microsoft.com/azure/data-factory/connector-troubleshoot-file-system

• Troubleshooting Data Factory pipeline/script activity access-denied errors

https://learn.microsoft.com/azure/data-factory/self-hosted-integration-runtime-troubleshoot-guide?tabs=data-factory#resolve-pipeline-script-activity-failures

• Self-Hosted IR troubleshooting guide

https://learn.microsoft.com/azure/data-factory/self-hosted-integration-runtime-troubleshoot-guide

• Azure Integration Runtime IP addresses

https://learn.microsoft.com/azure/data-factory/azure-integration-runtime-ip-addresses

• ADF security & access control troubleshooting

https://learn.microsoft.com/azure/data-factory/security-and-access-control-troubleshoot-guide

Share via

Access to pandey is denied Network type is OnPremise IP: fe80::603a:ba7:ae5e:9ba0%13

3 answers

Your answer