DFS namespaces disapear on machines running Windows 7 SP1

I am going to explain the problem, but we are going to have to work with script writers to create a group policy.

---Distributive File shares are accessed by Netbios resolution.

Netbios broadcasts are sent out by clients every 15 minutes and servers every 5 minutes. This broadcast holds information that will populate things like My network places, printers, and some other forms of software.

Also when these netbios broadcasts are sent out, the information is used to select a "domain Master browser". This process is called a browser election.

Traditionally, through a browser election. The latest and greatest operating system with holder of roles wins the election process. The holder of roles in this case is the FSMO role holder, (Domain Controller). However, Newer OS versions like VISTA or WIN7, as well as Linux and MAC operating systems may periodically fight the domain controller for control of the master browser service, (because of this election process).

What you have to do is tell the clients, they are NOT the domain master browser. Then, you have to tell the DC (with FSMO roles) it IS the domain master browser. This is done with a registry edit.

What I am going to do is provide you with a Microsoft Article on the domain master browser. It explains a registry edit that needs to be performed. (So, this is background information)
http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/net/chptr3.mspx?mfr=true

Here is the solution provided by Experts Exchange, Pber:
https://www.experts-exchange.com/questions/22135295/batch-file.html

We have tried the suggestions and it made no difference.

DFS is still unavailable to users with Windows 7 SP1, but available to the rest of the company using Windows XP or Windows 7 RTM.

Any other idea's that could help lead us in the right direction??

Upon installing SP1 for Windows 7, maybe it re-enabled Windows firewall. Windows Firewall on a client computer traditionally blocks netbios resolution. In order to resolve this issue, go into windows firewall and make an exception to Netbios, (otherwise known as 'file and print sharing')

I know that upon installing Serivice packs with XP and Vista, Windows Firewall re-enables itself.

There are also a couple of tests I would like to look at:

1) explore your "network" to see if you can see computers and shares on your network.

2) also go to the command prompt and type IPconfig /all to see if netbios is enabled, and what node type you are working with.

3) can you ping computers using netbios name (host name)?

4) if not, can you ping by IP or FQDN?

We can resolve NetLogin and Sysvol regardless of OS level.

We can also see SOME of the DFS shares from the Windows 7 SP1 machines, just not all.  This is where the query lies,  How is the DFS OS restricted?

All folders are available in previous versions of OS prior to Windows 7 SP1.  WE have a machine on Windows 7 with a user. they can see everything, Upgrade to SP1 and same user now can't see Folders with the DFS.  No changes to DFS folder security, or anything changed, same user logs back onto either Windows XP or Windows 7 workstation and had full access again.

We have checked the firewall and all is correct, hence they can see some of DFS folder structures.

1) explore your "network" to see if you can see computers and shares on your network.
      Yes we can.  The users can see some of the DFS structure within the environemt and other server shares as well

2) also go to the command prompt and type IPconfig /all to see if netbios is enabled, and what node type you are working with.
   Node type is 0x8

3) can you ping computers using netbios name (host name)?
  Yes - but all shortcuts and users use FQDN by default.  Netbios is only used as a last resort

4) if not, can you ping by IP or FQDN?
      All work.  Regardless of server we point at, certain folders remain unavailable.

go to the domain controller and look in event viewer  logs, for events in the 8000's. These events tell you of problems with netbios resolution and the master browser.

8021 or 8032 should look like this:

XXXcomputer thinks its the domain master browser, the browser service has stopped and an election has been forced.

Do you see any of these errors??? If so, what client computer is "XXXcomputer"

This took too long to solve as there is no document occurences or solutions. We were just luckky a fellow staff member found a solution