# Windows; second hop auth delegation; NetApp device

**URL:** <https://forum.ansible.com/t/windows-second-hop-auth-delegation-netapp-device/24678>\
**Category:** Ansible Project\
**Tags:** windows\
**Created:** [June 8, 2017, 10:14am UTC](https://forum.ansible.com/t/windows-second-hop-auth-delegation-netapp-device/24678 "2017-06-08T10:14:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\
**Post date:** [June 8, 2017, 10:14am UTC](https://forum.ansible.com/t/windows-second-hop-auth-delegation-netapp-device/24678/1 "2017-06-08T10:14:02Z")

</div>

Hello,

Has anyone else encountered problems when using a netapp file storage device in a second hop (with kerberos and auth delegation turned on)?

In one environment we have a NetApp Model: FAS3220, OS: 7 mode v8.2.1 which refuses to let us write to storage via a windows host.

The storage admins tell me its not presenting a username although from the logging I’ve seen I’m not convinced this is the case.

In other environments we have a different NetApp model FAS3220 OS: 7 mode v8.2.1 where it works.

Anyone else found a solution for this (or even a way to debug it)?

Many thanks

Jon