Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WHS 32bit - Cannot access "Shared Folders on Server" from desktop, Windows cannot access \\ServerName\ RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have just installed WHS 32 bit,  with a 32bit client desktop and a 64bit client laptop. Everything works fine for the desktop client.

    For the laptop, I downloaded the connector software from the server (so a connection does exist between them), and the connector installation places a link on the desktop: "Shared Folders on Server"

    Clicking on the link, I get:
    \\ServerName is not accessible. You might not have permission to use this network resource. Contact the admin of this server etc.The specified network provider name is invalid.

    If I look in my network places, the "ServerName" is not present.
    For the desktop client, in Network,  I can see the "Servername", and the "Servername Windows media connect" icons

    If I try Run> \\ServerName\, I get: windows cannot access \\Servername\ 

    If try the same command on my desktop, I get a windows security window, and a screen asking me to enter my network password

    I have looked at countless threads on this, tried changing security permissions, ensured the username and logon are the same etc etc.

    I have configured backups, and the WHS has no  problem seeing the laptop and setting that up.
    Yet, for some ??? reason, the laptop is not allowing a connection to the server, and I cannot  fathom what to do next 

    Sunday, April 5, 2015 3:02 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Well, maybe NetBios name resolution needs to be enabled on the client to work properly (to enable in the TCP/IP Properties in the Advanced dialog).

    Did you add an entry to the hosts file or lmhosts file in the past, pointing to an outdated IP address?

    You may also check the FAQ How to Troubleshoot Network Connection Problems with Windows Home Server for some details to verify.

    What happens if you click Start/Run (hotkey Windows+R) and enter \\servername\sharename (using an existing share on the server as direct target)?

    Best greetings from Germany
    Olaf

    Monday, May 4, 2015 1:42 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Would work direct connection to a share \\Servername\Sharename via Start/Run?

    Following reasons are a few of those which may block access to shared folders:

    • Mismatch in user name and password (those must exist on both machines and be identical on both client and server, a renamed account has internally still its old username)
    • time, date, time zone mismatch
    • network connection security set to Public
    • 3rd party security software blocking communication
    • name resolution fails and directs to a different system than expected

    Best greetings from Germany
    Olaf

    Tuesday, April 7, 2015 1:34 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thank you, Olaf, for taking the time and trouble to reply.

    I have checked through the items you mentioned and none of them seems to be causing the issue.

    I then downloaded the Windows Home Server Toolkit v1.1 (64-Bit) and ran the diagnostics.
    [Note: get it from: http://www.microsoft.com/en-gb/download/confirmation.aspx?id=22821]

    The toolkit diagnostics message:
    "The version of the Connector software does not match the version of Windows Home Server. Make sure you are installing the correct version of the Connector software."

    Further details are the provided of:
    "On your home computer, delete the %ProgramFiles%\Windows Home Server folder if it exists. Then install the Connector software from the Software shared folder on your home server, rather than from the CD. (Perhaps you have an old CD.) [o to Start, type in run, then paste in  \\YourServerName\Software\ Home Server Connector Software, and then run Setup.exe"

    Which I did and, sadly, it did  not work. When I ran the diagnostics again, it gave the exact same error message

    This whole process is like wading through a big vat of treacle, and finding you have just gone around in a circle. Boy o boy is it frustrating!

    I think the issue is something  to with win7’s security policies, and I still have no idea how to fix it

    Tuesday, April 28, 2015 10:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    One other item: With my other PC, which is a win 7 32 bit desktop, it is working perfectly for shared folders and backups (the laptop is failing on the backups as well - yet another issue to sort out...)

    In windows explorer, the Network "folder" [just below the Computer "folder" listing the drives], for the working system it shows the "servername" as a listed network computer, as well as in Media devices as a "Servername" Windows Media Connect. and Other devices as "servername"

    For the laptop with the issue, it does not show it as a listed network computer - but it does show it as a media and other device
    That is the problem - it is not there as  network computer - and maybe that is why things are failing?

    If I go to the shared folders on the laptop and right click on properties, then I get:
    "Problem with shortcut. The name '\\servername' specified in the target box is not valid. Make sure the path and file name are correct"

    That is why it is not working - for the desktop machine all the properties are exactly the same and it works.

    The only connection difference between the machines is: the desktop is using an Ethernet connection to the router, as is the home server, the laptop is wireless - maybe that is why WHS is not installing correctly on the laptop...???

    I am reaching here....

    Does anyone know how to solve my problem while I still have teeth and hair? 

    Tuesday, April 28, 2015 10:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well, maybe NetBios name resolution needs to be enabled on the client to work properly (to enable in the TCP/IP Properties in the Advanced dialog).

    Did you add an entry to the hosts file or lmhosts file in the past, pointing to an outdated IP address?

    You may also check the FAQ How to Troubleshoot Network Connection Problems with Windows Home Server for some details to verify.

    What happens if you click Start/Run (hotkey Windows+R) and enter \\servername\sharename (using an existing share on the server as direct target)?

    Best greetings from Germany
    Olaf

    Monday, May 4, 2015 1:42 PM
    Moderator