When I go to configure the File Access in UAG, I get an error of "Failed to enumerate domains." During some troubleshooting, I noticed when I disable the TMG Firewall service, I can then access the domains under the FileAccess Admin.
I checked the TMG logs and I'm seeing a lot of messages saying "FWX_E_BROADCAST_PACKET_DROPPED" as well as "Default rule - FWX_E_POLICY_RULES_DENIED".
I do have a publishing rule that is enabled and at the top (which I assume is created automatically) of "PublishingRule::NetBiosNameService" and the description states it's for "File Access".
Yep. Also, I can browse shares manually by \\machinename\share.
Another note, I added a rule in TMG to allow all protocols from internal and local host to internal and local host. It's almost as if TMG isn't applying these rules.
< Message edited by fusky -- 30.Sep.2010 9:50:37 AM >
If you're using UAG, you should never (well, almost never) go into the TMG console. For File Access, there are no rules you need to create. Make sure the UAG server is a domain member.
That's exactly what I thought. The server is a member of the domain. It's just weird that when I stop the TMG Firewall service, I can go into the File Access and see the domain listed. But when the TMG Firewall service is enabled, I get the enumeration error.
I have the same problem with UAG and file access. If I stop TMG, I can browse the domains and teh file servers, but when I start it, all the netbios traffic is dropped.
Yes I followed these steps. But when TMG is running I cannot browse the network. However, if I stop it, all the servers appear and I able to browse the domain. I have exactly the same problem than fusky.
The UAG internal network card is in a different subnet than the other servers.