Solution for "No network provider accepted the given network path"

News

Follow me on twitter: @nuoyan
Make a donation to this Blog by PayPal. Thanks!

Nuo is currently a Software Development Engineer in a Seattle-based software company.

The information in this weblog is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my school or employer. It is solely my opinion. Inappropriate comments will be deleted at the authors discretion. All code samples are provided "AS IS" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Community

Email Notifications

Solution for "No network provider accepted the given network path"

When you try to access a network path (FQDN) by “start”-“run”-”\\machine_name\share_name”, and meet 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.

If you meet this situation, run “sfc /scannow” may be able to solve the problem. If this method shouldn't work, you may also try this tip:

http://www.jsiinc.com/SUBR/tip8500/rh8517.htm

One of them will resolve the problem and enable you to access a shared location successfully by “start”-”run”-”\\machine_name\share_name”.

Posted: Sun, Nov 7 2004 21:30 by Nuo Yan | with 117 comment(s)

Filed under: 2. Windows Server

Comments

Nuo Yan said:

i´ve used both method but neither worked for me , what else can i try?

# January 7, 2005 9:53 AM

Nuo Yan said:

same here. solution did NOT work.

also of no help:
http://www.windowsbbs.com/showthread.php?t=40579

# February 11, 2005 12:58 AM

Nuo Yan said:

I am experiencing this error on a Windows 2003 Server running Veritas 9.1 I cannot connect to the media server.

What is causing such an error?

# February 28, 2005 2:21 PM

Nuo Yan said:

I was suffering from this problem, the solution just poped up.

To Solve This Problem,

1. Make sure you are able to ping the Workstation by FQDN
2. Simply Enable File and Print Sharing For Microsoft Networks From Properties of Local Area Connection.

Regards,

Nabil Makarem-MCSE™
nabilmakarem@hotmail.com

# March 4, 2005 2:10 AM

Nuo Yan said:

I ran the first suggestion:

sfc /scannow

It took a long time to complete but it did correct the problem.

Ed Meyer
PC Maintenance Tech II
Spencer Municipal Hospital

# March 8, 2005 8:37 AM

Nuo Yan said:

Change the Security Policy
Network security: LAN Manager authentication level: Send LM & NTLM responses

# March 25, 2005 10:20 AM

Nuo Yan said:

Because Microsoft in it's infinite wisdom has made security decisions in Win2003, they have locked down the ability for the systems to communicate. You need to all LanManager communication... use this

Change the Security Policy
Network security: LAN Manager authentication level: Send LM & NTLM responses

It worked for me after I installed a new server (so I didn't have it cludged)

I tried the other fixes and they didn't work.

Do this:
Go to Administrative Tools | Local Security Policies
In Security Options
Change the
Network security: LAN Manager authentication level: Send LM & NTLM responses

# March 25, 2005 10:26 AM

Nuo Yan said:

Event ID 1000 on the client XP machine - Windows 2003 SBS

One day, my logon.vbs script (from default domain group policy) which maps a certain shared folder to a particular user drive Z: based on their login name simply stopped working. I suspect an automatic Microsoft update is the culprit.

I had to employ 2 of the suggested solutions here :
1. Enable file and print sharing on the XP client machine (sp1, this had NEVER been enabled before, and my script worked like a charm until yesterday)

2. Set Send LM & NTLM responses under Network Security inside of the Default Domain group policy on the Windows 2003 SBS (the default domain policy is the only policy being enforced, and is presedence 1)

*VERY* strange - I could ping the server by name the entire time I was getting this error (only on *1* XP client), yet I could NOT run my .vbs successfully any more. The script maps 3 drives, 2 of the drive are mapped by all successful logins, the final drive "Z:" differs from machine to machine. the "X:" and "Y:" drives would map correctly, but not the "Z:" drive until I applied the above suggestions to my little problem.
Ah, if only the solution could be "Well, is the Mac turned on? No? Problem solved : )"

# March 30, 2005 10:43 AM

Nuo Yan said:

Better Solution is demote it from the domain to workgroup and then again promote to member server

# April 1, 2005 4:29 AM

Nuo Yan said:

Make sure client for microsoft networks did not get deleted from the properties of the network connection, that fixed it for me.

# April 12, 2005 7:09 AM

TrackBack said:

^_~,pretty good!

# April 16, 2005 9:49 PM

TrackBack said:

^_~,pretty good!

# April 17, 2005 8:14 PM

Nuo Yan said:

I just put the computer in my hosts file and it works perfectly.

# April 28, 2005 10:09 AM

Nuo Yan said:

"Make sure client for microsoft networks did not get deleted from the properties of the network connection, that fixed it for me."

^ Thanks, that fixed it for me!

# May 11, 2005 11:12 AM

TrackBack said:

Solution for

# May 24, 2005 3:02 AM

Nuo Yan said:

i run both the solution but couldn't resolve the problem.
Please guide me if you have any solution.

# June 5, 2005 10:40 PM

Nuo Yan said:

I was having problems getting group policy updates with the "no network provider" error. I turned on the TCP/IP Netbios helper service on and set to automatic and I was able to get GP updates.

# June 10, 2005 12:08 PM

Nuo Yan said:

If you get the error while trying to access an xp sp2 client, try turning off the microsoft firewall.

# June 23, 2005 2:14 PM

Nuo Yan said:

I have a unique rendition of this problem. I get the No network... message when I try to access my wife's machine (XP Home SP2). Her machine can access the shared files on my machine (XP Pro SP2) with no problem.

However, if in the Run window, if I enter \\192.168.1.3\c I can access her shared c: drive. \\Darlene\c results in the No network... eroor message.

If all else fails, I can create desktop shortcuts using her IP address for each of her shared directories and go from there.

# June 24, 2005 11:03 AM

Nuo Yan said:

Same problem here, but after enabling file&printer sharing in the WinXP firewall settings, the adminshare works again

# July 16, 2005 4:16 PM

TrackBack said:

Solution for

# July 22, 2005 7:18 PM

Nuo Yan said:

I had the same issue while pushing out Altiris Clients.

Enabled File and Print exception via GP. Now am able to push to all clients.

http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/mangxpsp2/mngwfw.mspx

# August 8, 2005 1:51 PM

Nuo Yan said:

Currently I have a Dell 1855MC server running windows 2003 server connected to a Win NT computer. I can succesfully ping from one to the other with both the computer name and IP address. However I am unable to access share folder on the 2003 OS server. I have tried all the recommendations above with no success. Both 2003 server and NT are in a workgroup environment. Any adivice would be appreciated.

# September 22, 2005 12:55 AM

Narinder Jit Singh said:

Workstation should be started.

Problem can be solved.

Thanks.

Regards
Narinder Jit Singh
India
9815300975

# December 20, 2005 3:53 AM

Gustavo said:

"Make sure client for microsoft networks did not get deleted from the properties of the network connection, that fixed it for me."

That worked for me too....don't know how I fought with this issue...and the answer was always here, in front my eyes...

Thousands thanks...;-P

# December 22, 2005 10:03 AM

eric said:

The problem for me was that Microsoft Firewall was enabled on the machines. Disabling it on the client machines fixed the problem. Wish I would've tried that first instead of editing the security policies, reinstalling File/Printer sharing, etc. Thanks!

# January 3, 2006 4:56 PM

argiope said:

The problem started for me yesterday (accessing an XP machine from a Win2k3 machine). I happened to install SP2 for XP yesterday. I figured that it was the firewall. Disabling this made everything work again (as GreenMonster mentioned above).

If you want to keep the firewall, you can try the other options as well. But disabling it is the quickest way to regain access.

# February 7, 2006 2:30 PM

mazroe said:

After trying everything suggested, I found that I had to disable my wirless card on my laptop and then I could reach the server through the lan.

# March 15, 2006 3:11 PM

Boneill said:

I was getting this problem when trying to access a share that resided on a XP Sp1 PC. The XP Sp1 PC had Internet Connection Firewall turned on. I had to add a Service into the ICF properties which allowed TCP ports 445 and 139 from the connecting IP address and I could then access the share.

# April 12, 2006 10:15 AM

PRO said:

Installing Client for Microsoft Network solved my problems.

Thanks so much for providing the answer

# April 13, 2006 9:19 PM

Jonny the Finch said:

I wanted to share only because I tried the two suggested methods and it did not work for me...

Frustrated, I continued to troubleshoot... and *smacks head* turned off my personal firewall...

Problem sovled. I'm kicking and laughing at myself...

# June 8, 2006 2:46 PM

Jonny the Finch said:

Kept reading... for the gentleman that can only map drives using an IP address... check your services. If you have disabled "TCP/IP NetBIOS Helper" you have disabled NetBT and NetBIOS name resolution and on a home network Windows may have no other alternative for name resolution except the hosts file. Many security web sites will tell you to disable this service. At its simplest NetBIOS on your LAN may just be a necessary evil. NetBIOS on your WAN or over the Internet, however, is an enormous security risk. All sorts of information, such as your domain, workgroup and system names, as well as account information is obtainable via NetBIOS.

# June 8, 2006 3:00 PM

Raj Mandalia said:

I was having this problem with the new AOL \ XDrive client; resolved by abalbling the "TCP/IP NetBIOS Helper" service; I had it disabled to increase the machine's performance by disabling all unnecessary services about a month ago.

# September 27, 2006 4:07 PM

Lee said:

"I was having problems getting group policy updates with the "no network provider" error. I turned on the TCP/IP Netbios helper service on and set to automatic and I was able to get GP updates." - This did it for me!!

# November 2, 2006 8:14 AM

Dylan said:

Turning off windows firewall worked for the error. Dylan

# November 8, 2006 2:36 PM

Nick said:

I am having this problem connecting to a virtual drive - part of MS shared portal - none of the above fixes

# December 1, 2006 4:05 AM

Andy said:

Thanks to the suggestion submitted July 16th 2005, I am now able to access the PC which I could previously only ping successfully but not access across the network. ------QUOTE------ >>> "Same problem here, but after enabling file&printer sharing in the WinXP firewall settings, the adminshare works again" <<<

# December 1, 2006 9:02 AM

Brian Lewis said:

Found the WORKSTATION service not started, even though it was set to auto, I started it and still couldn't do \\server\share but \\ipaddress\share works at least. I believe a root kit or worm screwed up something in the registry

# December 1, 2006 12:50 PM

Yoram said:

Enabling "TCP/IP NetBIOS Helper" did it for me after i tried everything else liseted above! I'm on a domain. I just changed it from Manual to automatic and pressed Start. Voila! You people ROCK!

# December 18, 2006 4:19 PM

Helen said:

for whatever reason, when I created a share on a 2003 server it was created without a $ at the end. I did not notice this little detail till I tried everything and nothing worked. As soon as I changed the name, it worked.

# January 19, 2007 1:27 PM

Jayesh said:

Hi, I'm having similer problem but with Accesing the shares from WIndows NT server system. I can access the shares of win2003 server from NT m/c USING IP Address, BUT can NOT access it by using Host name. Got the same Error "No network provide ... " . I updated the WINS server entry, but still in vain. Can someone suggest on it?

Thnx.

# May 18, 2007 6:28 AM

Jon Stone said:

I checked the second NIC and it didn't have the file/print sharing turned on. Opps.

# June 22, 2007 2:44 PM

JC said:

I tried EVERYTHING here, but to no avail. Winsock XP Fix 1.2 did the trick for me!

# June 22, 2007 2:52 PM

Passing Thru said:

"I turned on the TCP/IP Netbios helper service on and set to automatic and I was able to get GP updates."

Worked for me, thanks (2 yrs later!)

# July 16, 2007 3:42 PM

zul said:

thanks alot my problem solve

# July 19, 2007 11:35 PM

tripperdan said:

Hope they can clean out the Spam crap.

Anywho, the "TCP/IP NetBIOS Helper" being enabled resolved the issue for me. Not sure if one of the last critical updates killed the service or not.

# September 25, 2007 8:00 AM

Redback said:

Also make sure that the Workstation, Server and Computer Browser services are running

# October 23, 2007 7:32 AM

Bob Smith said:

Lost connection with network storage device, LaCie, 2TB capacity. Cannot remap. Cannot use crossover cable connected to host and get data. Can ping. Can cahnge ip address through console on internet. I really need some help.

# November 1, 2007 10:26 AM

Ravindran said:

In my sbs2003 server not ping ip from my clientpc.

when i try to open clientpc from server(sbs2k3)run:\\machineName

error "No network provider accepted the given network path"

# November 19, 2007 6:11 AM

Srinivas said:

Starting workstation from service control panel solved my issue

# December 4, 2007 12:52 AM

savo said:

I had this problem too. It was a map share using the variable %username%, in a VBScript.

I changed it to a NT command file (and the syntax to net use) and the script ran fine. I don't know if VBscript doesn't recognize NT variables.

That solved it for me.

# December 12, 2007 9:40 AM

Jack said:

Hey My computer was also giving same message when I was trying to access shared folder using UNC path.

there i realize that i have more than one computer with the same netbios name.

I changed the netbios name of the computer and

booom it worked

# December 14, 2007 6:46 PM

Mohammed Safiuddin said:

Dears,

I have installed Symantec Bakup server on DC, trying to install Backup Remote agent on my Proxy Server but unfortunately I'm not able to connect my share folder at proxy & even can't see access the resources over the network

I tried all the above solution but didn't work at all plz provide me the solution.

Thanx

# January 5, 2008 2:39 AM

Ardien said:

Check your Windows firewall exceptions (assuming you have it on) and make sure that you have "file and printer sharing" selected as an exception. I have seen this happen before (to me) =)

# January 9, 2008 7:32 PM

Hamid from Iran (Network Administrator) said:

I tried all of these solution but at least Just Turn off the windows fire wall. I bet it will work.

# January 15, 2008 9:00 AM

Ben said:

I had this problem

removing and re-adding the file and print service in TCP/IP fixed it for me

Thx

# January 17, 2008 4:25 AM

efriendfreee said:

the solution is to restart the workstation service for services in computer management

(I try it, it works ;)

# March 6, 2008 3:51 AM

Zep said:

I need to goto the Firewall setting and change the option to allow File and Print Sharing.

# March 19, 2008 12:19 PM

don said:

make sure both RCP services are running. by default, one is on and one is off

# April 10, 2008 10:14 AM

Keshav M T said:

I tried first one i got the connectivity

# May 10, 2008 2:49 AM

Keshav M T said:

Hi the first one is working fine

# May 10, 2008 2:50 AM

Dwight Nearing said:

easy fix - make sure the user has client for microsoft networks installed if not add then disconnect old drive mapping and readd the drive this will resolve this issue everytime.

# May 13, 2008 8:58 AM

Michael Collard said:

Netbios helper fixed me.

# June 10, 2008 12:25 AM

Jay said:

Stopping and restarting the Workstation service worked for me.

# August 6, 2008 8:56 PM

mongo said:

Client for microsoft networks was missing... that fixed it for me.. thanks!

# August 13, 2008 7:06 AM

Lali said:

Enable client for microsft networks, File and Printer sharing for MS networks and In performance options Turn on DEP for essential Windows programs and services only...

# August 15, 2008 7:32 AM

Hawk said:

I encountered this problem in the following scenario:

Three Windows2003 SP2 servers, two of which are domain controllers (DC).

The client, an XPsp2 and later sp3 machine, could access the first DC via name, but the second DC only via an UNC path containing the machine's IP. Attempts to access the second DC via it's hostname ("netbios" form or FQDN) failed with the "No network provider..." error. I could access the third server (member server) just fine.

All machines were accessible from each other within the three 2003 servers, it was just the XP client that couldn't resolve the 2nd DC's name. I didn't bother with it for a while, until I decided to install DFS and noticed the same error for accessing DFS shares from the XP machine. It gave the "No network provider..." error when attempting to access the DFS name space, or the \\domain.name resource.

I scratched my head and messed around with the DC GPO, comparing the effectively applied ones on the first and 2nd DC, to no avail. No firewalls on the machines, all disabled and I couldn't for the life of me figure out WHY on earth this XP machine would have problems resolving a name that nslookup and ping, or any other TCP/IP application resolved fine.

Finally, I resorted to enabling the "TCP/IP NetBIOS Helper" service, which was disabled on the XP machine, and voila! The 2nd DC and the DFS/Domain namespace now resolve fine and I can map shares.

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 mean nothing NetBIOS enabled on the servers, it's IP all the way? I mean, with Windows2000 MS was supposed to be getting rid of NetBIOS, what ever did happen to that plan?

Accepting it as a "necessary evil on the local LAN" isn't acceptable to me as I have VPN clients connecting in here that are not supposed to see certain machine names, etc.

Any suggestions as to how to remove NetBIOS completely, be my guest. I'll keep browsing TechNET and related websites for the answers.

Thanks for the tip on the NetBIOS Helper service, whoever originally posted that one.

# September 2, 2008 7:16 AM

Wes said:

I figured this out after reading all the comments and NOTHING worked.

After making sure all requirements were met in the above comments, I turned off the firewall on the server, and yes, my clients could connect. Turned it back on and they could not, so I knew it was something in the firewall. I double checked the firewall to make sure the "File and Printer" sharing was checked in the Exceptions tab to allow through the firewall. It was. HOWEVER, you need to go to the "Edit" button and edit each of your ports on the "File and Printer Sharing" service. There are 4 ports, TCP 139,445, and UDP 137,138. I believe it was UDP 137 that did it for me. You have to click on "Change Scope" on these ports and choose the option to include "Any Computer (including those on the Internet)". Mine was set to subnet only, which is why VPN clients were having problems accessing the server off the LAN.

Voila!!! You can keep the firewall on and fix the problem.

Granted, this is limited to VPN customers or non-subnet customers only. This may not fix everyone's problem above, as already seen by the comments.

Hope this helps!

# September 30, 2008 4:43 PM

Raj said:

Make sure that the Workstation, Server and Computer Browser services are running. This worked for me.

Note: They can be accessed through

Start->Run->services.msc

# October 9, 2008 10:39 AM

Natron said:

Reenabling this service fixed my issue.

"Kept reading... for the gentleman that can only map drives using an IP address... check your services. If you have disabled "TCP/IP NetBIOS Helper" you have disabled NetBT and NetBIOS name resolution and on a home network Windows may have no other alternative for name resolution except the hosts file. Many security web sites will tell you to disable this service. At its simplest NetBIOS on your LAN may just be a necessary evil. NetBIOS on your WAN or over the Internet, however, is an enormous security risk. All sorts of information, such as your domain, workgroup and system names, as well as account information is obtainable via NetBIOS."

# October 14, 2008 8:01 PM

Christopher said:

Assuming that you are on Windows XP:

1. Open network Connections

2. Right-click Local Area Connections (if you are using LAN), Click properties

3. Click Advanced tab

4. Click Settings which is under the firewall group.

5. Click Exceptions Tab.

6. Ensure that "File and Printer Sharing" is Checked.

7. Click OK.

# October 16, 2008 12:53 AM

NT LM Security said:

Worked for me to, Serivces, "NT LM Security Support Provider" was in Manual mode. Descpription even says "transports other than named pipes" (like say IP!!!) started it and it worked! Guess I can set it to Automatic...

# October 21, 2008 10:08 AM

Alexandre Madruga said:

Try to active the services "computer browser", "server" and "workstation".

It's solve my problem!

# October 30, 2008 10:54 AM

Mark Davies said:

Answer = Tuesday, September 30, 2008 4:43 PM by Wes.

Good answer mate worked a treat!

Thanks again

# November 7, 2008 9:15 AM

Muhammad said:

this is really easy & working solution for me must try thnx Raj

re: Solution for "No network provider accepted the given network path"

Make sure that the Workstation, Server and Computer Browser services are running. This worked for me.

Note: They can be accessed through

Start->Run->services.msc

# November 10, 2008 12:21 AM

Shawn said:

Thanks, the simplest solution is usually the best. The "Enable file sharing" option is the one that worked.

Cheers!

# November 17, 2008 7:20 AM

Mike said:

I had this problem this morning. I could ping the name and get a response but was unable to UNC on to it. After reading through this I found that activating TCP/IP NetBIOS Helper solved the problem. Thanks.

# November 27, 2008 5:57 AM

Paul said:

This is what fixed it for me. None of the other fixes helped.

Enabled the WebClient service

# December 1, 2008 6:12 PM

Ashish said:

Try to active the services "computer browser", "server" and "workstation".

Thanx man u rox,this solved my problem

# December 2, 2008 3:30 AM

Paul said:

Enabling the WebClient service fixed it for me.

# December 2, 2008 10:57 AM

Alex said:

If you have Symantec v11 look at your NIC properties and see if you have a selection for Teefer2, if you do uncheck it. This is a new piece from symantec that runs as a firewall....and no they dont tell you that do they !!

That fixed it for the pc's i support.

# December 2, 2008 2:08 PM

Michael Carroll said:

I went into the properties of the NIC and went into Advanced. Under windows firewall within this window I disabled it here and it worked. For some reason going thru control panel and windows firewall this didn't work.

# December 3, 2008 1:24 PM

NetForeverOften said:

When it happened to me, it was the RPC Locater service was stopped and set to manual. Starting it and setting it to automatic fixed the problem right away.

# December 6, 2008 10:21 AM

Lostkiwi said:

Make sure that NetBIOS is enabled over TCP/IP - this was the cause of my problems:

- Network Connections

- Right click network card and select Properties

- Highlight Internet Protocol (TCP/IP) and click properties button

- On the General tab click the Advanced button

- Select the WINS tab

- Make sure 'Disable NetBIOS over TCP/IP' is NOT selected. Either of the other options is fine.

# December 7, 2008 7:12 PM

Manh Dung said:

Hi all,

For my case, I am using Win2003 server and have the same error notice when I accessed other computer (by openning RUN => \\Computer-IP.

Just a simple solution by openning the "Services" management Console and start "The Remote Procedure Call (RPC) Locator" (make sure the RPC service is also turn on started).

I works well now,

Good luck

Manh Dung (VN)

# December 8, 2008 9:23 PM

Jagdish C. Sharma said:

"Kept reading... for the gentleman that I tried all the above solution but didn't work at all plz provide me the solution.

These are the steps i already tried..

1. trun off windows firewall

2. Enable file and print sharing

3. enable serives,workstation,RPC, Rpc locator, server, computer browser,TCP/IP helper serivice,,and above mention if i forgot to add.

4.Set Send LM & NTLM responses under Network Security

5. put the computer in my hosts file

6. Make sure client for microsoft networks did not get deleted from the properties of the network connection

7. Check for viruses

I guess i never miss out above mentioned solution...can anybody help me out with brand new solution....

# December 13, 2008 4:05 AM

S.M.Hawk said:

In my situation the solution proved to be the following:

In the DNS records of the AD Controller, the workstation in question had lost the right to update its own record (SID entry corruption). Therefore, when trying to resolve through DNS, an old DHCP assigned IP address kept coming up. I deleted the record, waited for the host in question to re-report to DNS ... new record with current IP showed up--UNC access restored.

Basically, delete the entry from DNS and let it rebuild.

Hope that helps someone.

# December 23, 2008 11:05 AM

John Wiersma said:

I had an odd issue. From the DC in my test domain, I could resolve \\<computer name> but not \\<domain name>.

If you can't resolve the domain name, things like group policy and such fail to start.

After going nuts for a month or more, I found this site and then looked at the TCP/IP NetBIOS Helper service. Once I turned that on, my problems all went away.

Thanks everyone.

# January 6, 2009 1:07 PM

Ryan said:

Under Local Area Connection Properties (or Wireless, depending on your connection):

• Select Internet Protocol (TCP/IP)

• Click Properties

• If you use DHCP, make sure both options on the General tab are set to Obtain IP/DNS address automatically

• Click the Advanced button

• Click the DNS Tab

• Remove all the DNS entries from the top window (if any)

• Make sure "Append primary and connection specific DNS suffixes" and "Append parent suffixes of the primary DNS suffix" are both Checked (this will uncheck "Append these DNS suffixes (in order)" and clear any entries in the bottom field.

• Check "Register this connection's addresses in DNS", Uncheck "Use this connection's DNS suffix in DNS registration."

• Hit OK on all open windows and Restart Computer.

# January 21, 2009 11:23 AM

qaiser said:

Go to Administrative Tools

then

Local Security Policies

In Security Options

change the settings to

Network security: LAN Manager authentication

level: Send LM & NTLM responses

# January 28, 2009 10:46 PM

Tamil Selvan said:

Thank to Raj for I had started the workstation and server services it able comunicating to the other system

# February 20, 2009 12:48 PM

Wilbert said:

If you have Symantec endpoint protection, disable 'network threat protection'. Worked for me.

It automaticly changed a setting after an update.

# February 26, 2009 3:34 AM

amate said:

I've found a solution...(for Windows XP Professional)

1. Go to "Network Connections"

2. Right click "Local Area Connection" and select "Properties"

3. Uninstall "Client For Microsoft Networks"

4. Restart your computer

5. Reinstall "Client For Microsoft Networks"

*Cheers* =)

# March 25, 2009 11:25 AM

Ganesh said:

Start the SERVER service. Its works for me.

# March 27, 2009 3:20 AM

Erick Menezes said:

In my case I solve the problem by starting two process that was down, in Start menu - run - services.msc

then start the process "server" and "computer browser"

that it.

Cheers

# April 22, 2009 7:26 AM

ru01 said:

Was struggling with this issue, and when i disabled the windows firewall, it was working.

# June 9, 2009 2:23 AM

Anand said:

Just removing the system from the domain & readding worked for me

# June 24, 2009 11:24 AM

Shibaprasad said:

Hi, Can anyone please tell me the use of $ sign to check the shared files of other system in LAN?

Thank you.

Shibaprasad

# July 1, 2009 2:38 AM

Windows XP Clients k??nnen keine Netzwerkfreigaben auf einem Windows Server 2008 erreichen – Vista-Clients schon « pmd-media's Blog said:

Pingback from Windows XP Clients k??nnen keine Netzwerkfreigaben auf einem Windows Server 2008 erreichen – Vista-Clients schon « pmd-media's Blog

# July 14, 2009 3:58 PM

sands said:

Disabling Symantec Endpoint Protection 11's Network Threat Protection fixed it for me. However, I just left it on and created a firewall rule in there to allow all traffic across specific subsets of servers.

# July 27, 2009 2:06 PM

sandeep kumar said:

goto services.msc restart workstation and computer browser service.and chech again

# August 7, 2009 1:38 AM

sandeep kumar said:

# August 7, 2009 1:39 AM

Vince said:

Enabling the Workstation service worked for me.

Thank You :)

# August 7, 2009 9:07 AM

braj said:

no solution helped me.

# September 15, 2009 8:41 AM

Mac said:

Same with me.... buddy none of this worked for me... is there anyone to help me out

# September 16, 2009 12:20 PM

sean said:

efriendfreee said:

the solution is to restart the workstation service for services in computer management

(I try it, it works ;)

THANKS IT WORKED!

# September 23, 2009 5:19 AM

Tony Toni said:

Just try using the \\computername\ with no sharename after and all the shared folders would be presented to you after you login with the correct username and password then simply dopuble click the share you wish to open

# October 1, 2009 8:41 AM

Chuck said:

YES!!!!!!!!!!!!!!!!! I tried ALL the solutions suggested to no avail and about 2 hours into it I found this:

Enabled the WebClient service

YEAH!!!!!!!!!!!!! That did it. Or that and a combination of everything else I tried ; - ).

Thanks all!

# October 6, 2009 2:40 PM

Peter said:

I have a similar problem which occured on a number of PCs at a simailr time...I believe it was caused by a .NET update from MS, as the work around was to go into .net admin and increase the level of trust to fully trusted for the local Intranet. ALll my NAS drives came back...

Still trying to figure out the correct fix.

# October 18, 2009 2:33 PM

etene said:

What kind of software will (or do you think) will come out for the iPhone when the software development kit comes out in February? And how will it be transfered to the iPhone? Will there be a software upgrade put out?

________________

[url=www.youtube.com/watch]unlock iphone 3g[/url]

# October 18, 2009 4:03 PM

etene said:

Im from california, & i have an iphone 2g, jailbroken, and im planning to give it to some1 in the philippines but i dont knoe if its gonna work with globe prepaid sim?pls help.thnks!

________________

[url=http://unlockiphone3g.webs.com]buy unlock iphone 3g[/url]

# October 21, 2009 3:04 AM

Amanat said:

sfc /scannow has nothing to do with this problem. SFC means System File Checker which only restores original operating system files.

# October 23, 2009 12:29 AM

Elmer said:

Double click on your network LAN icon then properties. Make sure your Client for MICROSOFT NETWORKS is CHECKED

# October 23, 2009 5:51 PM

tureeffofEWar said:

Hi!

New here and first post.

I am male, 29 years old from England

I enjoyed here.

[url=sencillamentesimple.wordpress.com/.../acai-berry-nuevo-engano]Botijos[/url]

# October 29, 2009 10:11 AM

Nhanner said:

Thank you Very Much MUHAMMAD, your my angel in my shoulder, God bless you always.......

# November 9, 2009 9:52 PM

Nhanner said:

muhammad, i thought my problem was solve of that suggestion. but your so good you try to help thus people who are yelling to solve this problem. For all you to know, i was happy as of now. i solve that problem on my own.... If somebody would like to know how to solve this problem. just reply this message or email me nhannerc@yahoo.com.au i love to help people and teach...

# November 10, 2009 12:07 AM

etene said:

i have downloaded .ipa files for free off of different websites etc. then i put them in the library then press sync. and this message comes up: the application was not installed on the IPhone because it could not be verified. anyone help please??

________________

[url=http://unlockiphone22.com/]unlock iphone 3g[/url]

# November 15, 2009 2:35 AM

Nuo Yan

Recent Posts

Tags

News

Make a donation to this Blog by PayPal. Thanks!

Community

Email Notifications

Archives

Solution for "No network provider accepted the given network path"

Comments

Nuo Yan said:

Nuo Yan said:

Nuo Yan said:

Nuo Yan said:

Nuo Yan said:

Nuo Yan said:

Nuo Yan said:

Nuo Yan said:

Nuo Yan said:

Nuo Yan said:

TrackBack said:

TrackBack said:

Nuo Yan said:

Nuo Yan said:

TrackBack said:

Nuo Yan said:

Nuo Yan said:

Nuo Yan said:

Nuo Yan said:

Nuo Yan said:

TrackBack said:

Nuo Yan said:

Nuo Yan said:

Narinder Jit Singh said:

Gustavo said:

eric said:

argiope said:

mazroe said:

Boneill said:

PRO said:

Jonny the Finch said:

Jonny the Finch said:

Raj Mandalia said:

Lee said:

Dylan said:

Nick said:

Andy said:

Brian Lewis said:

Yoram said:

Helen said:

Jayesh said:

Jon Stone said:

JC said:

Passing Thru said:

zul said:

tripperdan said:

Redback said:

Bob Smith said:

Ravindran said:

Srinivas said:

savo said:

Jack said:

Mohammed Safiuddin said:

Ardien said:

Hamid from Iran (Network Administrator) said:

Ben said:

efriendfreee said:

Zep said:

don said:

Keshav M T said:

Keshav M T said:

Dwight Nearing said:

Michael Collard said:

Jay said:

mongo said:

Lali said:

Hawk said:

Wes said:

Raj said:

Natron said: