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.


ADKM

862 posts

Ultimate Geek
+1 received by user: 37


#248777 9-Apr-2019 18:15
Send private message

Has anyone experience of a Win XP Network and could help me fix something?

 

When I click MyNetworkPlaces-Microsoft Windows Network-MSHOME there's normally a list of other computers than can be accessed.

 

But something has changed and now I get error MShome is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. The service has not been started.

 

I've spent about a week via Google looking for a solution, there's a lot of entries but nothing I could use to help.

 

Further info.. If one of the computer namess is typed into the Windows Address bar it appears under MSHOME and can be Explored, but that same error comes back when you click the MSHOME entry to close it

 

The mapped drives and other Network locations are all working normally, the problem seems only with MSHOME.

 

Now, not wanting to complicate matters, but may be related, there is a raspberry pi in the system and that would also normally see MSHOME under Windows Network (SMB). That has stopped working, too.

 

Thanks for any help, or even pointers on where else I might go/look.

 

 

 

 


Create new topic
raytaylor
4076 posts

Uber Geek
+1 received by user: 1296

Trusted

  #2214028 9-Apr-2019 23:46
Send private message

Windows system restore might work?





Ray Taylor

There is no place like localhost

Spreadsheet for Comparing Electricity Plans Here




nathan
5695 posts

Uber Geek
+1 received by user: 1630
Inactive user


  #2214049 10-Apr-2019 06:31
Send private message

what is the actual problem?

 

being not able to view/browse the "network neighboorhood" is more of a cosmetic issue when as you say, you can still connect/map drives etc to the remote machine


Andib
1395 posts

Uber Geek
+1 received by user: 974

ID Verified
Trusted

  #2214135 10-Apr-2019 09:25
Send private message

What OS are the other devices running? They may have updated to stop supporting SMB1.





<# 
       .DISCLAIMER
       Anything I post is my own and not the views of my past/present/future employer.
#>




ADKM

862 posts

Ultimate Geek
+1 received by user: 37


  #2214150 10-Apr-2019 09:51
Send private message

I have tried System Restore and the other Computers are running Win 10.
Without MSHome you can't Explore the other machines or connect to anything with the Pi. Aim to get things back how there were.
> updated to stop supporting SMB1.
Can I confirm this or find out whwt SMB 1 is ?
I had this same problem about 6 months ago and but I just cannot remember what fixed it.


1101
3141 posts

Uber Geek
+1 received by user: 1143


  #2214283 10-Apr-2019 10:50
Send private message

If you want good replies, you need to explain the issue EXACTLY , state what hardware & OS you have, what the EXACT issue is

 

Its all just guessing what your issue is

 

 

Is MSHome a workgroup or a PC name

 

You said XP network, are there any XP PC's

 

Static IP's ?

 

can you access the pc's share directly eg \\pcname\share , or \\192.160.1.15\sharename

 

----------------------

 

 

I'll guess that MSHome is the Workgroup name & you are trying to access PC's via 'network' in file explorer ???

 

Thats allways been flaky , with master browser issues etc etc etc

 

Give each PC that has shared files a static IP & access it directly eg \\pcname or \\192.168..x.x etc

 


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.