DFS Access using NetBIOS name - stopped working?

We have DFS setup on a 2003 domain, and it has been been setup for a few years without any issues - however, we restarted some servers over the weekend and since then we have had several users that are unable to access the shares using the domain NetBIOS name...

Using the FQDN name works fine:
\\domain.local\shares

Using the NetBIOS name fails
\\shortname\\shares

It looks like pre-Windows 7/server 2008 machines can connect OK, but newer machines are having difficulty (network path cannot be found) - (that may be coincidence...)

One thing I have noticed, when doing "ipconfig /all" - machines that can access the share OK have WINS servers specified, the newer machines / machines that cant access the shares do not have wins servers listed... I don't know if that is significant or not - and I have never noticed that before, so it may be normal and unrelated.

Does anyone have any ideas on what is going wrong / how to fix it?

Thanks :)
BergstrAsked:
Who is Participating?
 
BergstrConnect With a Mentor Author Commented:
I'm a domain admin so that's definitely not the problem... I think we have just found the problem though...

I searched the problem I mentioned in my previous post and came across this thread:

http://www.experts-exchange.com/Software/Server_Software/Microsoft_Server_Applications/Q_24990630.html

The last post mentions a link between AD and DNS - after looking through the event viewer, I could see there were problems with replication between our primary and secondary DNS servers.. our primary had already been restarted, but the secondary hadn't... and restarting the secondary has fixed the problem! - we also have an event log under file replication that says the following:

The File Replication Service has enabled replication from SECONDARY to PRIMARY for c:\windows\sysvol\domain after repeated retries.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Anyway... simple fix in the end.... but the thing to note is DNS, AD and DFS ALL have to be up and running correctly (replication must be stable) or things which shouldn't really be going wrong, go wrong!

Thanks very much for your help anyway :)
0
 
costanosNetwork EngineerCommented:
Are ALL the windows 7 machines having this problem, or just some of them?
0
 
BergstrAuthor Commented:
I think its most of them - all the ones I've tried have failed.. but we have quite a few machines and I've not been around to check all of them...!

Thanks
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
costanosNetwork EngineerCommented:
What you are explaining sounds to me like the lack of WINS configuration is the cause on the Win7 machines..  Can you configure one of the Win7 machines with the WINS information and see if that machine can browse the DFS after without FQDN?
0
 
BergstrAuthor Commented:
Just manually added the wins settings into the adapter, and i'm now getting a slightly different error:


"\\shortname\shares is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

The target account name is incorrect"
0
 
costanosConnect With a Mentor Network EngineerCommented:
Can you try this with a domain admin account if you havent already to eliminate legit security permission restrictions?
0
 
costanosNetwork EngineerCommented:
Glad you got it working :)
0
 
BergstrAuthor Commented:
Found the solution :)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.