Microsoft Forefront Unified Access Gateway Product Team Blog : File Access

Configuring and Troubleshooting File Access through IAG 2007 – Part 2 of 2

edgeaccessblog — Thu, 10 Jul 2008 22:39:00 GMT

1. Introduction

Most of the problems that could potentially occur with this feature are usually exposed during implementation. In many situations problems happen because key points were not considered or addressed prior to the implementation. During the troubleshooting phase the most important thing is to know how to gather the right information in order to analyze and identify the root cause. This part of the post will focus on this piece and it is an important one.

2. Scenarios

For the purpose of this guide, there it will be presenting two problems and the approach for the troubleshooting. Let’s start with the first problem:

I’m configuring the File Access, when I click in Domain and then click in Refresh, the right pane shows up blank and the status bar is already showing as Ready.

Before even start to troubleshoot this, it is important to find out if you are really capable to browse the Network Neighborhood / Windows Network through Windows Explorer. If you are not, than fix this first before move on. A good start to address issues with computer browser in the OS side is by following the KB 188305.

I fixed this part, now I’m able to browse using Windows Explorer and also through IAG. However, when I select a computer, click apply, select share and click in refresh it says: No shares in this server. But it does have because I can access directly from start / run and type the UNC path for that share.

The question remains: are you able to access this share using Windows Explorer? If not then you need to fix this first before move on to IAG. Simply access directly the UNC path just proves that you have the path (no roadblock in the middle) and the authorization to access, but the browser list it is different. This is the reason why you need to address the browsing side first.

What you can also do in order to get more information about the error is by enabling the IAG File Access tracing. To do that, follow the steps below:

1) Open the folder \Whale-Com\e-Gap\von\InternalSite\inc\ and edit the trace.inc file.

2) Change the value trace_on to true (trace_on=true) and save the file.

3) Open the folder \Whale-Com\e-Gap\common\conf\ and edit the trace.ini file. Go to the bottom of the file and add the line below:

[Trace\ShareAccess]

*=xheavy

Note: hit ENTER after *=xheavy to commit.

4) Save the file and reproduce the problem.

5) The log files will be located at \Whale-Com\e-Gap\logs and the file name will be following the standard below:

SERVERNAME.ShareAccess.default.DATE.TIME.log

If you want to go beyond, what you can do is also enable Netmon in the internal interface of IAG and starts the capture while trying to configure the resource.

Ok I got the file, now what should I do?

This file is really verbose and has lots of information that can help to identify the root cause for the problem. Let’s take a look in the main portion of this log file:

Here we start validating the user:

** 19.06.08 16:23:27.161 SHAREACCESS:GENERAL T3860

SetUserData start: domain=[contoso], user=[administrator]

* at line 129, file "src/ShareEnum.cpp".

The validation is done successfully:

** 19.06.08 16:23:27.171 SHAREACCESS:GENERAL T3860

SetUserData end: domain=[contoso], user=[administrator] - SUCCESS

* at line 143, file "src/ShareEnum.cpp".