Network Browsing error in Win2003

  • Thread starter Thread starter bill
  • Start date Start date
B

bill

My Server is running Windows 2003 Enterprise, are connected directly to LAN.
When I try to access any sharing directory in the LAN, such as
\\otherserver\d$


I got a error said "No network provider accepted the given network path."


The Computer Browser service is enabled.
TCP/IP is the only network protocol installed.

There is no any error log in event viewer.



Any thoughts?
 
Are you running a domain? If so make sure the domain controller points only to itself
as it'd preferred dns server in tcp/ip properties and that all domain computers point
only to domain controllers running dns for the domain. If you need to reconfigure dns
on the dc, reboot it after you are done.

If you are not in a domain, try to use the IP address of the server instead of the
name. If that works, you have a name resolution problem. If that does not help go
into the security options of the Windows 2003 server in Local Security Policy and
look for Microsoft Network Server: digitally sign communications (always) and disable
that setting. That setting may also need to be disabled in Domain Controller Security
Policy if you are in a domain. --- Steve
 
Hi Steven,

Thanks a lot for your reply.
No, I did not run any domain in this server, it's just a standalone server.
I also try to use the IP address to access the sharing directory, but I got
the same error.
But I could not find the "Local Security policy" as you mention, I just
could find "Local Computer policy" and go through all the settings, I found
there is no any change, all of them is "not configured".

Any idea?

Thanks
Bill
 
Use secpol.msc to bring up Local Security Policy. Go to security settings/local
policies/security options where you will see the setting I am talking about and set
it to disabled. --- Steve
 
Hi Steven,

Thanks again.
I got the setting that you mention, but it is disabled already. So any other
idea?

Thanks
Bill
 
What kind of clients are denied access?? Did this just start happening? Also try to
ping the W2003 computer from computers that do not have access to the share to
establish basic network connectivity and make sure the built in ICF or other software
firewall are disabled on it. Verify that the tcp/ip netbios helper and server
service are running and run netdiag on it looking for failed tests/errors/warnings.
Using a packet sniffer like Ethereal on the client computer to capture the packet
sequence of the share being denied may prove helpful. Look in Event Viewer of the
W2003 for any error events that may be helpful and enable auditing of logon events on
it to see if any failed logon events show in the security log in Event Viewer that
may help explain the problem.--- Steve
 
Back
Top