Re: NT workstations cant see shares on Windows 2000 server

From: Steven L Umbach (n9rou_at_n0-spam-for-me-comcast.net)
Date: 09/30/04

  • Next message: Steven L Umbach: "Re: Security Treats" 
    Date: Wed, 29 Sep 2004 22:24:41 GMT

    Verify that they can ping the problem server by IP address and name. Double
    check that netbios over tcp/ip is enabled on the problem domain controller
    in tcp/ip properties/advanced/wins. When you run nbtstat -n on that server
    it should show at least three entries as registered names. Use " net config
    server " to make sure it is not configured to be hidden. Check it's tcp/ip
    configuration to see if it is also a wins client [if wins is used] and that
    it points to the Windows 2003 domain controller and/or itself as it's
    preferred dns server. See if users can access it using unc as in
    \\computername\sharename or \\xxx.xxx.xxx.xxx\sharename using it's IP
    address if computer name does not work. If the problem dc has multiple nics
    or is a rras server that can sometimes cause problems with the browse list.
    Check Event Viewer on it for any pertinent errors. Software firewall, ipsec
    policy, or tcp/ip filtering can also cause access/visibility problems. Look
    in Local Security Policy on that dc and under security settings/local
    policies/security options the first security option for additional
    restrictions for anonymous access. If it is set to no access without
    explicit anonymous permissions, that has been known to cause problems with
    the computer browser service. If that setting is enable I am not
    recommending you disable if it was enabled for security purposes it but
    beware of the affect it can have on network browsing. --- Steve

    "tkam" <tkam@discussions.microsoft.com> wrote in message
    news:C5B6C375-7382-4AA6-8409-F9FCE7B5B662@microsoft.com...
    >I have a Windows 2003 DC (first DC in my network) with two Windows 2000 DC.
    > My WinXP and Win 2000 workstations have no problem seeing share drives on
    > one of the Win 2000 DC, but it cannot see the second Win 2000 DC shares. I
    > have created shares and setup the proper permissions on the second Win
    > 2000
    > DC.
    > The second Win 2000 DC has the latest patches.
    > Any Ideas
    > Thanks for your help.

  • Next message: Steven L Umbach: "Re: Security Treats"

    Relevant Pages

    • Re: SBS 2003 and TS-App Mode
      ... It's not secure... ... functionality over security and now you want functionality back. ... open and easy to use...they want TS on a domain controller back. ... Do not enable application server mode on a domain controllers. ...
      (microsoft.public.windows.server.sbs)
    • Re: Microsoft Security & Configuration Tool (MSCT)
      ... > install into the server become problem. ... How to undo the security configuration that I had already applied ... basicsv.inf is the Domain Controller Security Policy, ...
      (microsoft.public.security)
    • Re: SBS2003 and Terminal Services....
      ... SA loads so low in the TCP stack to not be an issue and protects the box ... Apply the Notssid.inf security template to TS running permissions ... Do not enable application server mode on a domain controllers. ... On Locally user right at the domain controller. ...
      (microsoft.public.windows.server.sbs)
    • Re: Security - Compromised!
      ... policy, no auditing/intrusion detection, etc. So I would say top things are ... to have properly configured firewall (test with external security scanner) ... Changes could have been made at domain or domain controller ... clean it would be time to run dcpromo on your new server. ...
      (microsoft.public.win2000.security)
    • Re: Unable to logon(Critical)
      ... chris made a post then I commented ... > Domain controller security policy also I configured as same ... Event log errors as well, on the client and on the server, and post the ID ...
      (microsoft.public.win2000.active_directory)