« Previous Next »

Thread: Cannot verfy access to path

Last post 10-05-2009 12:36 PM by drummelhart. 20 replies.

Average Rating Rate It (5)

RSS

Page 1 of 2 (21 items) 1 2 Next >

Sort Posts:

  • 03-05-2008, 6:47 AM

    • Tomte0
    • Not Ranked
    • Joined on 03-05-2008, 11:35 AM
    • Posts 2

    Cannot verfy access to path

    Hello!!

    I have a problem with acess to my site, i add Network Service to wwwroot and give network service access to read, But not working!?

    The message: The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that <domain>\<computer_name>$ has Read access to the physical path. Then test these settings again.

    I don't understan what is wrong?!  

    I'm newbe on IIS7, i know my website work, ihave runnit on IIS 6.0 and working fine! 

    Thanks for help!  

  • 03-05-2008, 7:19 AM In reply to

    Re: Cannot verfy access to path

    Make sure the computer name Server$ has permissions on the remote path.  When a computer is added to an active directory domain, it's account is name MachineName$ (with a dollar sign at the end  of it).  You can use Windows Explorer to grant Share and NTFS permissions on your physical folder.  When the network services accesses a remote resource, it uses the machine account as the actual account.  Hope that helps.

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
  • 03-05-2008, 3:45 PM In reply to

    • Tomte0
    • Not Ranked
    • Joined on 03-05-2008, 11:35 AM
    • Posts 2

    Re: Cannot verfy access to path

    Ok, thanks! I hope this work! if this not working can i fix this on another way?
    Because i have not Active Diretory install on this network i have my webserver on.
       

  • 03-07-2008, 5:08 AM In reply to

    Re: Cannot verfy access to path

    In that case, you'll probably need to look at using a local user account on each system with the same name and password.  When you connect from ServerA to ServerB, which based your description are in a workgroup , having the same user id and password will help get over authentication issues between machines. 

    Another option would be to look at NULL sessions, which in itself is a security risk. Here is more information on NULL sessions. http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/a4939515-b651-4ee0-b327-867b31fd8c9a.mspx?mfr=true

    I would recommend going the route of using local accounts with the same password.

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
  • 03-07-2008, 5:10 AM In reply to

    Re: Cannot verfy access to path

    One additional thing that can help identify errors is Process Monitor.  Running this on both machines when accessing is invaluable.  I didn't mention that before. 

    http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
  • 10-09-2008, 12:58 PM In reply to

    • Tom B
    • Not Ranked
    • Joined on 10-09-2008, 4:54 PM
    • Posts 1

    Re: Cannot verfy access to path

    I'm having the identical problem, on a newly configured Exchange 2007 server, Windows 2008 (64 bit) with OWA.

    Maybe I'm dense, but I'm having trouble with the idea that a computer account needs to be given permissions on a folder on its own drive?

    Anyhow, I did it, gave <domain>\<servername>$ read permissions to the folder, and rebooted the server, and am continuing to get the identical problem.

     I'm really missing IIS  6

  • 10-10-2008, 8:07 AM In reply to

    Re: Cannot verfy access to path

    The idea of granting a machine account access is to a remote UNC share, not local to itself.  Have you checked over at http://msexchange.org forums to see if anyone else has seen this issue?  I'm not familar with Exchange 2007 on w2k8.

    http://www.msexchange.org/articles_tutorials/exchange-server-2007/migration-deployment/installing-exchange-2007-windows-server-2008.html

    Steve Schofield
    Windows Server MVP - IIS
    http://weblogs.asp.net/steveschofield


    http://www.IISLogs.com
    Log archival solution
    Install, Configure, Forget
  • 02-17-2009, 11:34 AM In reply to

    • jcwhite
    • Not Ranked
    • Joined on 02-17-2009, 4:18 PM
    • Posts 1

    Re: Cannot verfy access to path

    Has anyone run across this error and found a resolution to it? I am having the same thing happen to me. Exchange 2007 on Server 2008 (64bit)

  • 02-18-2009, 9:07 AM In reply to

    Re: Cannot verfy access to path

    what error ? can't verify path? if you using built-in account this won't get verify until runtime. just make sure the app pool id has required permission on the resource, then you'll be fine.
    Cheers,
    Bernard Cheah
  • 03-23-2009, 9:01 PM In reply to

    Re: Cannot verfy access to path

    Does anyone have a solution for this?  In my case there is no remote resource and the app pool's Process Model Identity is simply 'Local Service'.  I've given 'Local Service' Read access to the web application's folder.  It keeps spitting back the same error:

    "The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that <domain>\<computer_name>$ has Read access to the physical path. Then test these settings again."

  • 03-31-2009, 4:33 AM In reply to

    Re: Cannot verfy access to path

    Did you read the previous response. built-in account can be verfiy until run time, you can ignore the msgs.

    Cheers,
    Bernard Cheah
  • 06-01-2009, 4:00 PM In reply to

    Re: Cannot verfy access to path

    Just like another posting on this page, I have Exch 2007 on a Win Server 2008 and OWA is not working and I get the following error when testing the OWA accessin IIs:
    "The server is configured to use pass-through authentication with a built-in account to access the specified physical path. However, IIS Manager cannot verify whether the built-in account has access. Make sure that the application pool identity has Read access to the physical path. If this server is joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that <domain>\<computer_name>$ has Read access to the physical path. Then test these settings again".

  • 06-09-2009, 9:14 AM In reply to

    Re: Cannot verfy access to path

    And ? did you read the previous replies?
    Cheers,
    Bernard Cheah
  • 07-01-2009, 3:17 PM In reply to

    Re: Cannot verfy access to path

    I'm getting the same message on Windows SBS 2008 running Exchange 2007. I checked all of the applications that use that particular application pool and they all have the same message w hen yo9u "test connection" under Authentication/Basic Settings. Therefore, if it does not test correctly here, it will not work at runtime. Did anyone else solve this problem? MikeD
  • 07-07-2009, 10:08 AM In reply to

    • norvak
    • Not Ranked
    • Joined on 07-07-2009, 2:07 PM
    • Posts 1

    Re: Cannot verfy access to path

     I am having this same error on my server.  I am not running exchange, but TSweb on Server 08.  I have read all the previous messages and none of them work for me.  I am still getting the error. 

Page 1 of 2 (21 items) 1 2 Next >
Microsoft Communities