Re: Network Browsing error in Win2003

From: bill (huangxiaohua_at_hotmail.com)
Date: 06/23/04 

Date: Wed, 23 Jun 2004 14:19:26 +0800

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

"Steven L Umbach" <n9rou@nospam-comcast.net> wrote in message
news:3A7Cc.162640$Ly.116992@attbi_s01...
> 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
>
>
> "bill" <huangxiaohua@hotmail.com> wrote in message
> news:eFUuGTNWEHA.3120@TK2MSFTNGP12.phx.gbl...
> > 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?
> >
> >
>
>

Relevant Pages

  • Issues migrating SBS 2003 domain to Server 2008 Standard
    ... We are stuck migrating our SBS 2003 domain to Server 2008. ... Fatal Error:DsGetDcName (SRV-EXCH) call failed, ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... The name.local entries are used by my apache server to implement ... change button, more button, the "Primary DNS suffix of this ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... button, more button, the "Primary DNS suffix of this computer", it should ... The Security System could not establish a secured connection with the server ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC (netdiag /v workstation)
    ... DNS Host Name: tonyb-pc.imageproc.imageproc.com ... Testing IpConfig - pinging the DHCP Server... ... Attr: subschemaSubentry ... Owner of the binding path: ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues migrating SBS 2003 domain to Server 2008 Standard
    ... Since you have migrated to standard server 2008 you would be better served posting in a Standard server NG. ... Event String: ... Verify your Domain Name Sysytem (DNS) is ... network connectivity to a domain controller. ...
    (microsoft.public.windows.server.sbs)