Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


linw

2893 posts

Uber Geek
+1 received by user: 1205


#175522 2-Jul-2015 14:51
Send private message

I have googled long and hard, and spent much time trying to fix this problem, to no avail

I am asking whether some clever person can point me to some diagnostic tools to try to get to the basic problem. Win diags say all is OK (surprise!).

The issue is with one of my three win 10 comps (all are on build 10159). The other two can't access the problem one's shares using Explorer's network discovery or by using \\compname.

\\ipnumber works fine. Ping compname is fine. My 8.1 notebook can access the shares fine. 

The error I get is 'Windows can't access \\compname' - error id is 80070035. This error has been a nuisance for many years and no one seems to have a definitive answer as to why it occurs. It is the error you get trying to access shares on a comp in sleep mode. Actually, there have been many 'answers' but none that work for all and certainly not for me.

It's like a DNS error but for only this one comp! My Android phone (app Fing) has no trouble seeing all devices with their ip no. and name.

No 3rd party AV - just Defender.

Just tried two locally, only connected by switch - same result. Tried with firewall off - no go. 

Like I said, any diagnostics I can try?



Create new topic
raytaylor
4076 posts

Uber Geek
+1 received by user: 1296

Trusted

  #1337518 6-Jul-2015 00:01
Send private message

You say its like a dns problem.
Can you ping the computer using its name instead of ip address?




Ray Taylor

There is no place like localhost

Spreadsheet for Comparing Electricity Plans Here




linw

2893 posts

Uber Geek
+1 received by user: 1205


  #1337584 6-Jul-2015 09:17
Send private message

Yes, I mentioned above that pinging the computername is fine. Of course, this is using ICMP protocol.

Tried using Nirsoft utility, NetResView, and it can't see any of the offending win 10 comp's shares if run from another win 10 comp. However, the win 8.1 can see and access all the offender's shares! No idea what subtle difference there could be for this to only affect other win 10 comps. 

There is obviously something different with one of my win 10's but I just can't see what it might be. It has been upgraded from win 7 to 8 to 8.1 then several win 10 previews so something has got lost in the wash. I guess a clean install would fix it. Maybe!! 

Never mind, I will keep at it for a while longer as I hate being beaten by a computer/network.

Thanks.

Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.