Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

One DC LAN Hosed "No network provider accepted the given network p

21 views
Skip to first unread message

Mat...@yahoo.com

unread,
Nov 9, 2005, 3:09:29 PM11/9/05
to
NETWORK: 1 Domain Controller - Windows Server 2003 sp1 standard and 4
WindowsXP sp2 (firewall turned off) clients and all are setup to
automatically update from Windows Update fully patched. This small
production LAN has been working just fine for over 1 year.


PROBLEM: on 11/6/5, SUDDENLY without any major change/cause; now when you
try to access a network path (FQDN) "start" "run"
"\\machine_name\share_name", and get error message “No network provider
accepted the given network path.” But when you open the Command Console
(“start“-“run“-“cmd“), you can ping that machine successfully by using the
FQDN. Network shares and browsing across the LAN is inaccessible!


TROUBLESHOOTING DONE: I verified DNS is operational along with DCDIAG
/test:dns, check workstation, netlogon, workstation & other pertinent
services are running and ran system file checker “sfc /scannow” utility. I
removed one workstation from the domain then tried to re-add only to get
error message 'domain controller can not be contacted' even though I can ping
it by IP address.

I search Google.com & support.microsoft.com but have not found anything to
resolve this sudden and dumbfounding problem. Any & All ideas, input and
solutions is GREATLY appreciated.

Any IT genius out there who leads me to solving this problem and saving me
from having to rebuild my W2K3 gets lunch on me!

~Matt
--
Feel free to contact me about this or other IT Systems Administrator things
at Mat...@Yahoo.com

Phill

unread,
Jan 18, 2006, 5:09:54 PM1/18/06
to
Is your dns server working correctly and are all your clients and server
registered in it?


<Mat...@Yahoo.com> wrote in message
news:DFEF13D7-4F9E-4AAC...@microsoft.com...

FumbleThumb

unread,
Dec 3, 2009, 12:03:02 PM12/3/09
to
Hi Matt, a couple of thoughts
1> If you are using DHCP have you verified that the client IP adresses are
the actual scope you expect (ie not the class C address that the clent gets
when it can't find the DHCP server ) as you would still be able to ping ok.
Also are the clients "Authenticated Users" , I can't remember exactly but
this was one of the choices when setting up the DHCP, though if this was
working I don't really see why it would stop.
Have you changed any network topology ie hub/switch as some operate in
different modes by default at the port level ?
I would make a backup of the Domain Group Policy and Domain Controller
policy ensuring I don't overwrite my original backups of group policy objects
and restore the originals to see if there is anything weird in the security
settings. Hopefully you have backup policies. I would do this first as
having the backups its simple to do. Failing that I would carefully go
through error logs to see if all services are running correctly and verify
rights to the OU/Domain users
I have assumed also that you have Turned off your server rather than just
restarted it, I would also do that to any hub/switch/router on the path from
client/server
Hope this helps
regards

--
To Server them all my Days

0 new messages