How To Fix Windows Error No Network Provider Accepted The Given Network Path (Solved)

Home > Windows Error > Windows Error No Network Provider Accepted The Given Network Path

Windows Error No Network Provider Accepted The Given Network Path

Community Sponsors Advertisement Windows Exchange Server SharePoint Virtualization Cloud Systems Management Site Features Contact Us Awards Community Sponsors Media Center RSS Sitemap Site Archive View Mobile Site Penton Privacy Policy Reply lexus says: November 8, 2006 at 4:51 am Good site… visit my site about LEXUS! Open the required ports You are required to open the following ports in the firewalls of the client systems: 135 139 445 5000 5001 5002 Applies to: Agent/Distribution server installation failure, note: servername: and name: too. this contact form

Thanks all! Or that and a combination of everything else I tried ; - ). Cause This error could be due to one or more of the following reasons: You do not have access to admin$ of the client system You are unable to ping the Reinstall "Client For Microsoft Networks" *Cheers* =) Reply Ganesh says: March 27, 2009 at 3:20 am Start the SERVER service.

Click Apply, and then click OK. OK, so enabling a service on the XP machine fixes the problem, but WHY on EARTH would I have to have a "NetBIOS Helper Service" when I have nothing and I Reply Nikki says: October 19, 2006 at 6:55 am goodsite.NikkfromLA.(USA) Reply Cabbage says: October 24, 2006 at 4:59 pm Thanks this worked for me! 1.

Goto run type "services.msc" without quotes. 2. share|improve this answer answered Jan 8 '10 at 16:29 squillman 33.4k868126 Thanks for responding, there are 2 NICs in the box, only one is physically connected and active. Both 2003 server and NT are in a workgroup environment. Somehow it got disabled, I enabled it and started the service.

Advertisement Related ArticlesQ. All programs>Run> then type "services.msc" (without qoute) 2. Because I also having the same problem, please let me know if you have the answer. A simple reboot cleared out the cache and everything was back up to normal.

Open configuration windows. 3. Click the Start button, then click Shut Down. Reply Mark says: July 4, 2010 at 6:17 pm I still get the error.. Click close and here you go..

I double checked the firewall to make sure the "File and Printer" sharing was checked in the Exceptions tab to allow through the firewall. We just virtualized our file server and most of the Vista machines can connect. Resolution You can resolve this problem as follows: Check your access to admin$ of the client systems To check your access to admin$ of the client systems, follow the steps given Thanks a lot sir regards A MOHAN RAO +919826061122 INDORE INDIA Reply MOHAN says: February 23, 2010 at 3:51 am when i tried to open network any desktop its given msg

What is causing such an error? Petergal

Comments (0) Cancel reply Name * Email * Website Follow UsArchives June 2007(1) April 2007(1) January 2007(1) October 2006(1) September 2006(2) July 2006(1) June 2006(1) May 2006(3) April 2006(3) March Open a CMD.EXE window. 2. It has ran for a couple of years with zero issues.

It's solve my problem! Thanks for the tip on the NetBIOS Helper service, whoever originally posted that one. this has had me stumped for a few months, i would never have guessed it was NTLM related... Permalink 0 Terrence April 30, 2012 20:12 Adam, What is even more unusual is that I get this error from a scan on an XP (284 computers) workstation but not from

I would share something out and would get complaints from some people saying "you NOOB, give me access" (or some other choice words). Note: They can be accessed through Start->Run->services.msc Reply Shawn says: November 17, 2008 at 7:20 am Thanks, the simplest solution is usually the best. If you want to keep the firewall, you can try the other options as well.

Can someone suggest on it?

Mobile:410-978-7981. I installed the hotfix and bang it all worked again.. solution is START- RUN-TYPE (sfc /scannow) insert the operating system cd then problem was resloved. Reply Josh says: March 9, 2010 at 11:51 am On a Windows 2003 sp2 server, I fixed it by installing KB968389 as in the article below.

Thank you, Reg, wcnw Wednesday, January 09, 2013 10:02 AM Reply | Quote 0 Sign in to vote Dear Jared, Do you find an answer for your problem ? However, I just left it on and created a firewall rule in there to allow all traffic across specific subsets of servers. I have a Windows 2003 R2 SP1 server, with an Windows XP SP3 client that is having difficulty accessing it via UNC (\\servername). I really need some help.