Strange DNS/Sharing Problem

  • Thread starter Thread starter Esteven1
  • Start date Start date
E

Esteven1

Recently we had to upgrade one of our Windows 2000 Machines to a Domain
Controller in order to have it run some services, reguardless now we're
having all kinds of issues.

Setup:

We have two existing DC's: HF217870 and DMESERVER both servers have
worked prior to the upgrade. Now we have upgraded the Windows 2000
machine to be another Domain Controller and shares have blown up.

We have a DFS with a root, and no branches or other folders off the
root. The main problem is that I am getting tons of errors when it
tries to route to the FQDN of the DFS

\\x.priv.m.edu\sysvol\x.priv.hfh.edu\

Is routable on some machines but not others (in Explorer)
Thus our GPO's are not being distributed to users because they can't
browse to there. Meanwhile some of our computers ARE able to access
this, but again not all.

On the machines that are not able to browse to the above, browsing to
\\x\sysvol\x.priv.m.edu works 100% of the time. However I believe that
the x is simply referring to the Primary DC not to the AD
"x.priv.m.edu" I would like to if possible TOTALLY remove DFS and FRS
from the Windows 2000 Machine, ie. have it not participate in
replication. However I have yet to find any place to remove it from the
AD. I can however, of course, stop the DFS and FRS services, but it
does not remove the links in AD. Where would I go to do this and/or is
it possible? If not possible then any ideas what my problem could be?

Thanks,

Eric Stevens
 
Well I figured out the problem myself. The problem was that for some
reason the new server was multi-homed. That is it had two NIC cards
both on separate sub-nets. This was used as a legacy issue and was
never fixed back to standard operation. Thus any clients who mistakenly
chose the 'other' IP address for their replication/ DFS site would
receive the error that it was inaccessible. Quite a strange error, but
after disabling that NIC on the server, resetting the whole lot of
them, it seems to be fixed. Everyone can browse their appropriate
drives and GPO's are enforced again.

Thanks kinda sorta,

Eric
 
Back
Top