I've discovered an on-going problem on our Windows Server 2003 domain where some clients are unable to access the UNC path using our root FQDN (we'll call it primary.org). This causes some interesting issues: - I can access our mail server via \mail but not via \mail.primary.org - Logon scripts won't run, because \primary.org\SYSVOL can't be accessed - No server will respond if I try to access via the FQDN - sql.primary.org, web.primary.org etc.
A few months ago we got a new router and changed our IP scheme (figured it was a good time to a project we've been wanting to do for a long time). Everything seems to work, except this DNS issue. I've done quite a bit of Googling, read several threads on Experts Exchange and other tech forums/resources and reading on eventid.net which gave me some ideas, all of which are outlined below.
I've tried re-creating the Reverse DNS entry for primary.org, adding primary.org to a user's HOSTS file (which got me into the network browser, but SYSVOL still locked me out), removing my ISP's DNS servers from the GC DC server, running dcdiag /fix, ipconfig /registerdns, gpupdate /force and replacing the default Group Policy object with a new one. ANY thoughts would be very much appreciated.