ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Solved Unable to mark NAS location trusted in Office

    IT Discussion
    microsoft office security trust center
    7
    18
    1.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • triple9T
      triple9 @JaredBusch
      last edited by

      @JaredBusch I had same problem recently. Solution was to use name instead of IP address.
      I had to map folder as \\FILESERVER\Data

      JaredBuschJ 1 Reply Last reply Reply Quote 0
      • JaredBuschJ
        JaredBusch @triple9
        last edited by JaredBusch

        @triple9 said in Unable to mark NAS location trusted in Office:

        @JaredBusch I had same problem recently. Solution was to use name instead of IP address.
        I had to map folder as \\FILESERVER\Data

        as I noted in the OP, that did not work.

        Looks like I have to do the same.

        1 Reply Last reply Reply Quote 0
        • JaredBuschJ
          JaredBusch @BraswellJay
          last edited by JaredBusch

          @BraswellJay said in Unable to mark NAS location trusted in Office:

          I have a similar issue with a 3rd party developed application that uses an access database. The only way I could find to workaround was to add the trusted location through a registry edit. Here is the notes I have on what I did

          I was able to add \\FileServer\Data\ via the built in GUI, by clicking Add new location and then browsing to Network and clicking on the FileServer item, etc. This added the location like this. This works, as I can open the file and have no warning about disabled macros, but is a work around. The Mapped Drive should work also.
          b400d8b7-bff7-4a9a-8ab1-efcf5425d628-image.png

          I then exported the key and tweaked it to add K:\ in Location1.
          No luck opening the file via K:\ does not work.
          2cd94233-8f1f-4178-9f27-1d6f90959add-image.png

          Even though it does show up in trust center after adding via the registry.
          0f5caf6c-b5ab-449b-ab27-2b50a731467d-image.png

          As a side note, I can not click on K:\ entry in the GUI either. I can click on the other two entries.

          triple9T pmonchoP DashrenderD 3 Replies Last reply Reply Quote 0
          • triple9T
            triple9 @JaredBusch
            last edited by

            @JaredBusch https://docs.microsoft.com/en-us/deployoffice/security/internet-macros-blocked

            1 Reply Last reply Reply Quote 0
            • pmonchoP
              pmoncho @JaredBusch
              last edited by

              @JaredBusch said in Unable to mark NAS location trusted in Office:

              @BraswellJay said in Unable to mark NAS location trusted in Office:

              I have a similar issue with a 3rd party developed application that uses an access database. The only way I could find to workaround was to add the trusted location through a registry edit. Here is the notes I have on what I did

              I was able to add \\FileServer\Data\ via the built in GUI, by clicking Add new location and then browsing to Network and clicking on the FileServer item, etc. This added the location like this. This works, as I can open the file and have no warning about disabled macros, but is a work around. The Mapped Drive should work also.
              b400d8b7-bff7-4a9a-8ab1-efcf5425d628-image.png

              I then exported the key and tweaked it to add K:\ in Location1.
              No luck opening the file via K:\ does not work.
              2cd94233-8f1f-4178-9f27-1d6f90959add-image.png

              Even though it does show up in trust center after adding via the registry.
              0f5caf6c-b5ab-449b-ab27-2b50a731467d-image.png

              As a side note, I can not click on K:\ entry in the GUI either. I can click on the other two entries.

              Just a WAG, but what if you map K:\ to \Fileserver and then trust K:\data folder. Maybe it wants a specific folder verses an entire drive?

              1 Reply Last reply Reply Quote 0
              • DashrenderD
                Dashrender @JaredBusch
                last edited by

                @JaredBusch said in Unable to mark NAS location trusted in Office:

                @BraswellJay said in Unable to mark NAS location trusted in Office:

                I have a similar issue with a 3rd party developed application that uses an access database. The only way I could find to workaround was to add the trusted location through a registry edit. Here is the notes I have on what I did

                I was able to add \\FileServer\Data\ via the built in GUI, by clicking Add new location and then browsing to Network and clicking on the FileServer item, etc. This added the location like this. This works, as I can open the file and have no warning about disabled macros, but is a work around. The Mapped Drive should work also.
                b400d8b7-bff7-4a9a-8ab1-efcf5425d628-image.png

                I then exported the key and tweaked it to add K:\ in Location1.
                No luck opening the file via K:\ does not work.
                2cd94233-8f1f-4178-9f27-1d6f90959add-image.png

                Even though it does show up in trust center after adding via the registry.
                0f5caf6c-b5ab-449b-ab27-2b50a731467d-image.png

                As a side note, I can not click on K:\ entry in the GUI either. I can click on the other two entries.

                is K mapped with a name or an IP?

                JaredBuschJ 1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch @Dashrender
                  last edited by

                  @Dashrender said in Unable to mark NAS location trusted in Office:

                  is K mapped with a name or an IP?

                  By IP.

                  I assume it will work when I remap it with the DNS entry.

                  DustinB3403D 1 Reply Last reply Reply Quote 1
                  • DustinB3403D
                    DustinB3403 @JaredBusch
                    last edited by

                    @JaredBusch said in Unable to mark NAS location trusted in Office:

                    @Dashrender said in Unable to mark NAS location trusted in Office:

                    is K mapped with a name or an IP?

                    By IP.

                    I assume it will work when I remap it with the DNS entry.

                    Had this same issue, had to map via dns name rather than ip address.

                    Microsoft claims this is a feature.

                    JaredBuschJ 1 Reply Last reply Reply Quote 0
                    • JaredBuschJ
                      JaredBusch @DustinB3403
                      last edited by

                      @DustinB3403 said in Unable to mark NAS location trusted in Office:

                      @JaredBusch said in Unable to mark NAS location trusted in Office:

                      @Dashrender said in Unable to mark NAS location trusted in Office:

                      is K mapped with a name or an IP?

                      By IP.

                      I assume it will work when I remap it with the DNS entry.

                      Had this same issue, had to map via dns name rather than ip address.

                      Microsoft claims this is a feature.

                      Except this worked until 2 weeks ago by IP. So fuck you Microsoft.

                      user is supposed to be back int he office Thursday, so I can test this.

                      DustinB3403D 2 Replies Last reply Reply Quote 1
                      • DustinB3403D
                        DustinB3403 @JaredBusch
                        last edited by

                        @JaredBusch I get it, 100%.

                        I had a customers entire production shop (who actually has public IP address subnet for their LAN) who came to a complete halt calling in for assistance in sorting out what the hell happened.

                        Microsoft claimed this was a security feature. . .

                        1 Reply Last reply Reply Quote 0
                        • DustinB3403D
                          DustinB3403 @JaredBusch
                          last edited by

                          @JaredBusch Any update?

                          JaredBuschJ 1 Reply Last reply Reply Quote 0
                          • JaredBuschJ
                            JaredBusch @DustinB3403
                            last edited by

                            @DustinB3403 said in Unable to mark NAS location trusted in Office:

                            @JaredBusch Any update?

                            Waiting on the user to schedule time.

                            DustinB3403D 1 Reply Last reply Reply Quote 0
                            • DustinB3403D
                              DustinB3403 @JaredBusch
                              last edited by

                              @JaredBusch said in Unable to mark NAS location trusted in Office:

                              @DustinB3403 said in Unable to mark NAS location trusted in Office:

                              @JaredBusch Any update?

                              Waiting on the user to schedule time.

                              the best part, waiting. . . lol

                              Well have a good weekend.

                              1 Reply Last reply Reply Quote 0
                              • JaredBuschJ JaredBusch has marked this topic as solved on
                              • JaredBuschJ
                                JaredBusch
                                last edited by

                                Tested and it works all the time by hostname instead of IP.

                                1 Reply Last reply Reply Quote 1
                                • 1 / 1
                                • First post
                                  Last post