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”.
i´ve used both method but neither worked for me , what else can i try?
same here. solution did NOT work.
also of no help:
http://www.windowsbbs.com/showthread.php?t=40579
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?
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
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
Change the Security Policy
Network security: LAN Manager authentication level: Send LM & NTLM responses
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
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 : )"
Better Solution is demote it from the domain to workgroup and then again promote to member server
Make sure client for microsoft networks did not get deleted from the properties of the network connection, that fixed it for me.
I just put the computer in my hosts file and it works perfectly.
"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!
i run both the solution but couldn’t resolve the problem.
Please guide me if you have any solution.
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.
If you get the error while trying to access an xp sp2 client, try turning off the microsoft firewall.
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.
Same problem here, but after enabling file&printer sharing in the WinXP firewall settings, the adminshare works again
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
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.
Workstation should be started.
Problem can be solved.
Thanks.
Regards
Narinder Jit Singh
India
9815300975
“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
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!
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.
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.
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.
Installing Client for Microsoft Network solved my problems.
Thanks so much for providing the answer
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…
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.
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.
goodsite.NikkfromLA.(USA)http://megspace.com/lifestyles/uldiaz1/10mg-diazepam.html
Thanks this worked for me!
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.
“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!!
Good site… visit my site about LEXUS!
http://lexus.vipautocatalog.info
Turning off windows firewall worked for the error.
Dylan
I am having this problem connecting to a virtual drive – part of MS shared portal – none of the above fixes
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” <<<
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
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!
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.
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.
I checked the second NIC and it didn’t have the file/print sharing turned on. Opps.
I tried EVERYTHING here, but to no avail. Winsock XP Fix 1.2 did the trick for me!
“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!)
thanks alot my problem solve
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.
Also make sure that the Workstation, Server and Computer Browser services are running
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.
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”
Starting workstation from service control panel solved my issue
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.
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
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
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) =)
I tried all of these solution but at least Just Turn off the windows fire wall. I bet it will work.
I had this problem
removing and re-adding the file and print service in TCP/IP fixed it for me
Thx
the solution is to restart the workstation service for services in computer management
(I try it, it works 😉
I need to goto the Firewall setting and change the option to allow File and Print Sharing.
make sure both RCP services are running. by default, one is on and one is off
I tried first one i got the connectivity
Hi the first one is working fine
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.
Netbios helper fixed me.
Stopping and restarting the Workstation service worked for me.
Client for microsoft networks was missing… that fixed it for me.. thanks!
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…
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.
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!
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
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.”
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.
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…
Try to active the services “computer browser”, “server” and “workstation”.
It’s solve my problem!
Answer = Tuesday, September 30, 2008 4:43 PM by Wes.
Good answer mate worked a treat!
Thanks again
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
Thanks, the simplest solution is usually the best. The “Enable file sharing” option is the one that worked.
Cheers!
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.
This is what fixed it for me. None of the other fixes helped.
Enabled the WebClient service
Try to active the services “computer browser”, “server” and “workstation”.
Thanx man u rox,this solved my problem
Enabling the WebClient service fixed it for me.
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.
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.
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.
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.
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)
“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….
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.
I had an odd issue. From the DC in my test domain, I could resolve \\ but not \\.
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.
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.
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
Thank to Raj for I had started the workstation and server services it able comunicating to the other system
If you have Symantec endpoint protection, disable ‘network threat protection’. Worked for me.
It automaticly changed a setting after an update.
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* =)
Start the SERVER service. Its works for me.
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
Was struggling with this issue, and when i disabled the windows firewall, it was working.
Just removing the system from the domain & readding worked for me
Hi, Can anyone please tell me the use of $ sign to check the shared files of other system in LAN?
Thank you.
Shibaprasad
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.
goto services.msc restart workstation and computer browser service.and chech again
hi
Enabling the Workstation service worked for me.
Thank You 🙂
no solution helped me.
Same with me…. buddy none of this worked for me… is there anyone to help me out
efriendfreee said:
the solution is to restart the workstation service for services in computer management
(I try it, it works 😉
THANKS IT WORKED!
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
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!
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.
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=http://www.youtube.com/watch?v=aBoMmqEIsGk]unlock iphone 3g[/url]
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]
sfc /scannow has nothing to do with this problem. SFC means System File Checker which only restores original operating system files.
Double click on your network LAN icon then properties. Make sure your Client for MICROSOFT NETWORKS is CHECKED
Hi!
New here and first post.
I am male, 29 years old from England
I enjoyed here.
[url=http://sencillamentesimple.wordpress.com/2009/07/22/acai-berry-nuevo-engano]Botijos[/url]
Thank you Very Much MUHAMMAD, your my angel in my shoulder, God bless you always…….
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…
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]
after reading all these comments I finally found what my issue was
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
If someone installed Symantec Endpoint Protection in your system, might you had the same trouble as me.
My root cause problem was Symantec Endpoint firewall protection was enabled.
Below are my solution steps.
1. Go to Symantec Endpoint Protection.
2. Open configuration windows.
3. Click at “Change Setting”
4. On section, Network Threat Protection, click at “Configure Settings”
5. and then change tab to “Microsoft Windows Networking”
6. On setting section, you will see “Share my files and printers with other the networks” as gray enable.
7. You have to disable and enable this checkbox, please unsure it shows as enable (not gray).
8. Click OK for saving.
Now, you can access to this PC right now.
Hope it is useful.
My hard drive crashed but luckily I have pictures saved on my iPhone and some on my iPod. I bought a new Mac, is there a way to transfer the pictures to the computer other than e-mailing them one at a time?
________________
[url=http://votenoconfidence.orgfree.com/VNCBB/viewtopic.php?f=2&t=90&p=278#p278]unlock iphone 3g[/url]
Work for me, thanks
We experienced this on a Windows 2003 R2 server configured in workgroup (!) mode. After Windows updates, shares on the server were no longer available, even from the server itself. Most of the patches were non-removable. We ended up having to place a call to Microsoft:
There is a internal Microsoft KB that had the same access issues to Shares on a workgroup after an update was run on the server.
To resolve this issue the hot fix KB968389 was removed from the Server. The Server is then rebooted. (Access to the Shares now work).
The KB968389 hot fix is reapplied to the server and the server is restarted. Access to the Shares still work.
please uninstall file and printer sharing
then install it.
it works
My symptoms:
1) Accessing \\server\ from remote machine yielded “No network provider accepted the given network path”. 2) Pinging “server” works.
3) Connection initiation (SYN) packets from remote machine to server are replied by reset (RST) packets like there was no service no that port
4) \\server works locally
My resolution (worked for me):
Disable and re-enable File and printer service on that particular network interface (if you have more than one)
not propaer sharing the fill or folder
not propaer sharing the fill or folder
I heard a lot of people said 90% of forex trader lose money. I wonder how long and roughtly how much the trader lose become they become the remaining 10% winners.
[url=http://forexrobot-review.info]best forex software[/url]
I need to get funds from UK and SBI bank branch (in which I have account) do not have forex facility (therefore do not have IBAN/BIC code). Can it be possible to get funds transferred to other branch (which has forex facility) and then transfer from one branch to another?
[url=http://forexrobot-review.info]best forex software[/url]
Hey guys! I bought the Forex Megadroid Automated System thingy, but I dont know how to configure it, does any here have Forex Megadroid, and can like explain to me a brief tutorial on how to configure and start trading with Forex Megadroid.
[url=http://forexrobot-review.info]best forex software[/url]
my problem is not solve
I tried all of the above and mine was down to the fact that port 135 was blocked by a corp firewall. Try a telnet on that port just to rule it out.
i cant saccssed
Simple solution:
Start-> Run-> ping -t hostname
(replace hostname with the machine name you want to access)
then
get the IP address of machine by PING.
Now
Start-> Run-> \\ip-address-of-machine\sharename
replace (ip-address-of-machine) with IP Address you obtained using PING.
If don’t works. email me.
I Have started with sfc /scannow.
But still am not able to work.
Hey, ok, I get it, I guess – but does this really work?
We renovate houses In Maryland,US.
Custom / Surface remodelings,
reasonable prices,license,
references,photos,free estimates,
also take houses to rehab:
http://www.renewhouse4u.com.
Mobile:410-978-7981.
Thanks.
I had the same problem – To solve it :
– make sure you are on the machine from which you want access to a network path ->
– goto services
– restart the ‘server’ service
– try accessing the network path
magic!
I had this issue with a domain controller I Virtualized. I went through all the following and foudn no solution. It turned out to be Symantec Endpoint, as it lost its drivers during the conversion. I simpley uninstalled Symantec Endpoint and rebooted and everything was working for me.
when i tried to open network any desktop its given msg me no network provider accepted the given network path.
solution is START- RUN-TYPE (sfc /scannow)
insert the operating system cd then problem was resloved.
Thanks a lot sir
regards
A MOHAN RAO
+919826061122
INDORE
INDIA
when i tried to open network any desktop its given msg me no network provider accepted the given network path.
solution is START- RUN-TYPE (sfc /scannow)
insert the operating system cd then problem was resloved.
Thanks a lot sir
regards
A MOHAN RAO
+919826061122
INDORE
INDIA
I had a similiar issue with users in a remote office unable to map a drive to a server at our head office. The funny thing was that they could access any other server with no problems. Turns out the problem had to do with a stale route that was not updating on our router. A simple reboot cleared out the cache and everything was back up to normal.
I had a similiar issue with users in a remote office unable to map a drive to a server at our head office. The funny thing was that they could access any other server and map a drive as usual. Turns out the problem had to do with a stale route that was not updating on our router. A simple reboot cleared out the cache and everything was back up to normal.
On a Windows 2003 sp2 server, I fixed it by installing KB968389 as in the article below. The odd thing is that they say that issue is caused by a corrupt install of KB968389 and are saying to reinstall, but I never had it installed in the first place…
http://blogs.technet.com/networking/archive/2009/10/20/errors-may-be-seen-when-attempting-to-access-shares-after-installation-of-the-updated-described-in-kb-968389.aspx
I solved this by disabling Network Threat Protection in Symantec (if you have it installed)
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
This one is very usefull for me. Thanks a lot Dude 🙂
Hello,
that problem occur because the WMI performance Adapter has been disabled. To fix that follow this simple steps.
1. All programs>Run> then type “services.msc” (without qoute)
2. Pop up window appear, get rid on the bottom part, you will notice “WMI Performance Adapter”
3. Double click, choose automatic, apply, click start button and then ok.
That’s it ..check if it is working.
Thanks!. ..
Hi All,
I was facing the same issue, the root cause of this issue is that two services in my remote server were disabled.
To resolve this issue I had to manually start the following services:
1) Server
2) Workstation
Hope this helps others…
Cheers
AJ
“Make sure client for microsoft networks did not get deleted from the properties of the network connection, that fixed it for me”
brilliant, it was so easy
just uninstall your network adapter in device manager…
reboot your computer in order for it to reinstall the previously uninstalled adapter.if you have IP address, you’ll have to configure it again
To resolve this issue, use the appropriate method:
Log on to the network using a valid user account. To do so, follow these steps:
Save and close any open work on your computer.
Click the Start button, then click Shut Down.
In the Shut Down Windows dialog box, click the “Close all programs and log on as a different user” option button.
Click the Yes button.
When you are prompted, log on to the network with a valid user name and password.
Correct the Frame Type setting in the properties for the IPX protocol.
I am trying to access from a workstation running Win 2003 Standard R2 (IP: 192.168.1.146) to an AD server running on Win 2003 Standard (IP: 192.168.1.100). The domain name of the AD server is spmadone.com. I’ve setup correctly the DNS in machine 192.168.1.146 to point to 192.168.1.100.
When I tried to ping from machine 192.168.1.146 using spmadone.com, i got back the error “Ping request could not find host spmadone.com”.
Can anyone help me? Thanks.
I use windows server 2003. i am on domain. my machine pops the error after about 30 seconds “No network provider accepted the given network path” and the net work services stop till i restart the machine and this is not the solution of this error. any one to help me in this regard with a competent solution please.
I had same the issue, resolved by disabling firewall in the Local Area Network properties advanced tab.
Thanks a Lot.
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
Thanks you very very much it perfectly work for me.
http://support.microsoft.com/kb/127933
Cause: This error message can occur when you run a program with a universal naming convention (UNC) name when you are not logged on to the network, or if you are using the wrong frame type for the IPX protocol
Solution: To resolve this issue, use the appropriate method:
Log on to the network using a valid user account. To do so, follow these steps:
Save and close any open work on your computer.
Click the Start button, then click Shut Down.
In the Shut Down Windows dialog box, click the “Close all programs and log on as a different user” option button.
Click the Yes button.
When you are prompted, log on to the network with a valid user name and password.
Correct the Frame Type setting in the properties for the IPX protocol.
In our case, the script we were running wasn’t running as a user with enough privileges to do what it was programmed to do.
I still get the error.. The solutions above don’t work for me 🙁
On Windows Server 2003 R2, this worked for me:
“Better Solution is demote it from the domain to Workgroup and then again promote to member server”
hi
If ur haveing the same problem the u can go to start—-run—services.msc–then start WORKSTATION,SERVER,SYSTEM BROWSER then u can able to access the system in the network.
if is ther any query pls ping me satishkpt@gmail.com
mobile:09985714525 any time any where my ip follows me………………..
After reviewing all the comments here. I found that Symantec Endpoint Protection automatically disables most of the network functionality on 2003 Server. Enabled all’smart’ filtering, alowed netbios protection and token ring traffic. Also allowed shares for each network and all network cards, as this setting was not consistent. Did not have this problem for Endpoint installed on Win XP.
I’ve enabled the WEBCLIENT service then it worked.
I had this issue in MS.SharePoint when I tried to open the document library in Windows Explorer from the Actions menu.
WINSOCK XP fix 1.2 fixed it for me. When I connect to VPN at work, I can ping the server but I cannot open them when I type the \\serverIP in the run command. Now its fixed.
To solve this problem I wasted almost 2 hours but finally solved.
1st – Installed all protocols in reference of NETBios on the network connection.
2nd – On the Internet Protocol (TCP/IP) click on “Advanced…” button and on the WINS tab verify if “Enable LMHOSTS lookup” is checked and right below selected “Default:” option.
Hope that it helps.
I had the same problem. To fix I just had to reboot the PC hosting the share and then run a “ipconfig /flushdns” on the client.
I was having this issue with accessing a SharePoint 3.0 Document Library using Explorer. I fixed it by enabling abd starting the ‘WebClient” service on my XP machine.
I’ve had this issue on a Windows 2003 Server, its not a name resolution error as the same error appears when you run \\localhost
The fix was to remove and reinstall a faulty MS Security Update KB968389
http://blogs.technet.com/b/networking/archive/2009/10/20/errors-may-be-seen-when-attempting-to-access-shares-after-installation-of-the-updated-described-in-kb-968389.aspx
I have problem for few weeks, I have enabled the TCP/IP NetBios Helper from services that the only thing resolve the problem for me
Enabling TCP/IP NetBios Helper from services resolved the problem for me..Thanks Nuo Yan
It’s really glad to read about the following topic which has enhanced my knowledge regarding topic and plus has given alot of ideas which I can think on.
So I would say thank you to the blog owner for providing this amazing information.
go to services.msc and start the computer browser service.
Yes, enabling TCP/IP NetBios Helper from services resolved the problem for me too.
Great!
i encounter a problem, i’m trying to search the computer name of my mates but the message prompted is “no network provider accepted the given network path”. What should i gonna do in order to fix this problem.
Running all the recommendations above didn’t resolve the issue.
I placed a call with MS Help Desk. Removing following windows patches resolved the issue on two of my Windows 2003 servers, seperate locations.
KB 971032,971657 and 968389
Indeed a very good read! Very informative post with pretty good insight on all aspects of the topic! Will keep visiting in future too!
Indeed a very good read! Very informative post with pretty good insight on all aspects of the topic! Will keep visiting in future too!
Activating TCP/IP NETBIOS helper service did the trick for me
Enabling TCP/IP NETBIOS made it work…. completely insane, not sure why it was even disabled. The joys of computers 🙂
if you try to connect to windows 7 machine by \\MachineIP\sharedFolder, you’ll get this error. You need to try to connect with \\MachineName\sharedFolder and that’s working.
After installing Microsoft Network Service my problem resolved. Thanks a ton
My problem was I could access the share from other computers on the LAN but not across my WAN. However, i could access shares on other computers on that LAN fine. I pinned it down to a windows firewall issue. File and Print Sharing was listed as an exception, but I discovered after editing that entry and hitting the change scope button that the scope was set to “My network (subnet) only”. I changed it to “Any computer” and presto my shares were accessible.
I’ve attempted to repair this “No network provider…” issue following many different procedures on the web (registry changes, group policy changes, etc.). In the end, none of them worked. So, I resorted to my typical problem solving practice of opening the Run box, typing CMD, and running CHKDSK C: /F (or /R). Worked like a charm. From now on, I will run CHKDSK before attempting anything else with these odd problems. Other solutions tend to waste a lot of time.
I just stumbled upon your blog after reading your blog posts wanted to say thanks.i highly appreciate the blogger for doing this effort.
http://www.cheapestusedcomputers.com
I Facing same problem and i solved by removing client for microsoft network from lan card properties and add again it and restart my computer solve my problem
This issue can be resolved by using..
service console
you just need to start “SERVER” & Workstation service
i was having same proplem
i made the TCP/IP netbios help enable and automatic
this solve issue
thanks for help
Dear i have solved the problem by the following method..
1. Check and make sure that you can ping to FQDN
2. Goto Lan Connection Propertese
3. Install Protocol Clients for Microsoft Windows
4. Click close and here you go..
Please reply me if this will help You….
Imran Bashir
System & NEtwork Administrator
MCP, JNCIA-EX, ER
+92333-4330176
+92322-8456509
Hi Nuo Yan, thanks a lot.
For me the tcp ip netbios helper service solution was the one. Somehow it got disabled, I enabled it and started the service. Afterwards it worked like a charm.
THE RESTART WORKED
I just searching this kind of things in search engines. My searching was ending here. Keep up your good work. I bookmarked it for general updates.
Had this same problem and followed every solution given, but none worked for me. Eventually I restarted the DC my server was a member of – fixed.
i cant stop this error “no network provider accepted the given network path” in windows 2003 server sp2 how to solve this error please help me
No network provider accepted the given network path” in windows server 2003
plz send me the solution
I started the “TCP/IP NetBIOS helper” service and my problem was fixed
My setup was simple peer to peer but after a MS update on Windows XP SP3 everything got messed up. The Winsock XP fix got the trick for me.
http://www.softpedia.com/get/System/OS-Enhancements/WinSock-XP-Fix.shtml
Tried all the above, nothing worked. Found the service called “Workstation” was set to automatic but was not started. Once I started the service it fixed it right away. Drove me nuts.
This was a setup with AD and two sites each with a 2003 R2 file server, at one site 32-bit, the other 64-bit.
File servers were synced via DFS. Workstations were a mix of WinXP, Win7, Win8. It has ran for a couple of years with zero issues.
Suddenly, perhaps after a Windows update, at one site workstations would during logon only connect to the remote site. Later DFS host could be switched to the local server but would fall back to the remote server.
Nuo Yan and RAUSHAN provided the solution.
On the offending server, network security, LAN Manager authentication level, must be set to:
Send LM & NTLM responses
Go to:
Administrative Tools,
Local Security Policy
Security Options
Change:
Network security: LAN Manager authentication level
to:
Send LM & NTLM responses
Press OK or Apply and reboot the server.
Starting the “NT LM Security Support Provider” service fixed it for me.
This works for me. Everything is fixed.
AVG Internet Security 2014 firewall had disabled file and printer sharing within the AVG gui.