Re: Lost local network access

From: Steven L Umbach (sumbach@ameritech.net)
Date: 03/29/03


From: "Steven L Umbach" <sumbach@ameritech.net>
Date: Sat, 29 Mar 2003 22:07:06 GMT


      Has anyone done any changes on that server lately, particularly
import/apply a different security template or otherwise harden?? Was guest
account used for file access?? If so check to make sure it is still enabled
(I am not recommending using guest account though). Do shares still exist?
Other things to check/do. A routine checkdisk, viruscan, and netdiag (on
cdrom under support/tools setup) would be in order. Was a firewall recently
installed on that computer? If so that could be an issue if not configured
to allow necessary lan traffic. Check that file and print sharing is still
enabled and restart server and computer browser service. Make sure netbios
over tcp/ip is enabled in wins properties of tcp/ip configuration and
restart tcp/ip netbios helper service. Check that any local users that are
supposed to be there still exist and are not disabled or locked out. Check
event viewer on problem server for any errors/clues. In local security
policy under user rights make sure users are allowed network access and not
included directly or indirectly in a deny network access group. Under
security options check that additional restrictions for anonymous access is
not set to "no access without explicit permissions" and you may need to try
to loosen lan manager authentication level for a workgroup. Was an ipsec
policy assigned? Those are some things that come to my mind right away and
there are others. Good luck. --- Steve

"Dan Laue" <dan@onestopcollect.com> wrote in message
news:01d901c2f61d$8eafb700$3401280a@phx.gbl...
> Hello all i need your help i have 2 server 2000 machines
> running on my network both have been running as members
> of a workgroup for over a year. Wednesday i noticed some
> of my local desktops could not access mapped paths to 1
> of these servers. yesterday i got time to finally reboot
> that server and i thought it would fix the issue but its
> still not allowing any access from the local network i
> can see it on the network, i can ping it, i can even
> logon through terminal services to it from the local
> network, but i cant browse it or connect network mapped
> paths. when i connect to it through terminal services i
> can browse out of it to all the local machines on the
> network no problem. its almost like its protecting itself
> from inbound connections except for terminal services and
> ping.... i had a certified windows 2000 tech here last
> night he cant figure it out please help??????



Relevant Pages

  • << SBS News of the week - Sept 26 >>
    ... And he points to the info you need to put the file on the server in the ... at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... by the firewall at risk. ...
    (microsoft.public.backoffice.smallbiz)
  • << SBS News of the week - Sept 26 >>
    ... And he points to the info you need to put the file on the server in the ... at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... by the firewall at risk. ...
    (microsoft.public.backoffice.smallbiz2000)
  • Re: << SBS News of the week - Sept 26 >>
    ... > And he points to the info you need to put the file on the server in the ... > at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... An attacker can exploit these flaws in tandem via specially ...
    (microsoft.public.backoffice.smallbiz2000)
  • << SBS News of the week - Sept 26 >>
    ... And he points to the info you need to put the file on the server in the ... at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... by the firewall at risk. ...
    (microsoft.public.windows.server.sbs)
  • Re: << SBS News of the week - Sept 26 >>
    ... > And he points to the info you need to put the file on the server in the ... > at the network perimeter. ... The Symantec Firewall/VPN and the Gateway Security ... An attacker can exploit these flaws in tandem via specially ...
    (microsoft.public.windows.server.sbs)