Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Win7 Ultimate 64 cannot log onto shared folders on WHS 2011 and WinXP has no problem RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    When I try to access the shared folders in Win7 it tries to log in using a "domain" name the same as my Win7 computer name and my user name ("Z68/Eric").  The logon fails.

    When I try to access the shared folders in WinXP I am able to write a new file into the shared folders.

    WHS is completely up to date as is Win7 Ultimate.

    The connector software fails to find the server and so cannot install on the Win7 machine.

    I have a WHS Ver 1 machine that is not powered on during all this testing.  I removed the V1 connector from the Win7 machine but still cannot install the new connector.

    I had the WHS and Win7 machines in a Homegroup with no ability to log on, removed the Homegroup on both machines and still cannot log on.  Now I don't even see the shared folders in Windows Explorer on the Win7 machine,  They were visible at the root when in a homegroup but are not visible at all now.

    I did assure that the WHS and my Win7 and WinXP machines are all in workgroup "MSHOME" but that didn't help. "Logon failure: unknown user name or bad password"

    The WHS is a new build and I am testing. Works with WinXP but not with Win7.  I need some new ideas. Thanks.

    Eric Robert Lewis, Ph.D.



    • Edited by erlewis Tuesday, October 2, 2012 5:33 AM edit
    Tuesday, October 2, 2012 5:30 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    The next day I removed both the server and the Win 7 machine from the homegroup.  The Win7 machine still came up with a logon screen domain (machine name)\user and it would not accept a password.  This is the clue:  Why does this logon screen pop up?  Why does this screen refer to a "domain" when my machines all use workgroups?

    Then the next day after that and after a few reboots.  I added the Win7 machine to the home group again. This time I was able to access the shared folders.  So there is some sort of bug related to Windows7 WHS2011 Homegroup - FYI Microsoft!  Apparently adding a homegroup and removing a homegroup and adding it again resets some sort of link that signals secure access is approved.

    However, the connector software was still not able to install.  This time the connector did appear to locate the WHS and begin an installation that fails repeatedly.

    I saw a number of other threads related to the connector-Win7 install issues but they are mostly from 2011.  I didn't track just exactly what was the fix that worked.  Is this still an outstanding problem others are having?  Certainly there must be a writeup of the standard work-arounds by now if it is not fixed.  Thing is, the connector was a very recent download and search as I have, I didn't even find a connector disk in the WHS OEM pack.

    The dates and times appeared to be pretty close and the time zones also.  I have an atomic clock sitting on my desk under my monitor as a reference.

    All the machines use standard Microsoft virus, spy, firewall, except the WinXP machine that still uses Symantec AV.  But of course the WinXP machine is the one with no particular problems (didn't test the connector though).

    Eric Robert Lewis, Ph.D.

    Wednesday, October 3, 2012 6:39 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Eric,

    check, if time, date and time zone on the server are matching with the same settings on the client.

    Other than that, name resolution may be a problem (any DNS Suffixes in your IP configuration on the client?), also a 3rd party security suite on the client may interfer.

    Best greetings from Germany
    Olaf

    Wednesday, October 3, 2012 5:58 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    The next day I removed both the server and the Win 7 machine from the homegroup.  The Win7 machine still came up with a logon screen domain (machine name)\user and it would not accept a password.  This is the clue:  Why does this logon screen pop up?  Why does this screen refer to a "domain" when my machines all use workgroups?

    Then the next day after that and after a few reboots.  I added the Win7 machine to the home group again. This time I was able to access the shared folders.  So there is some sort of bug related to Windows7 WHS2011 Homegroup - FYI Microsoft!  Apparently adding a homegroup and removing a homegroup and adding it again resets some sort of link that signals secure access is approved.

    However, the connector software was still not able to install.  This time the connector did appear to locate the WHS and begin an installation that fails repeatedly.

    I saw a number of other threads related to the connector-Win7 install issues but they are mostly from 2011.  I didn't track just exactly what was the fix that worked.  Is this still an outstanding problem others are having?  Certainly there must be a writeup of the standard work-arounds by now if it is not fixed.  Thing is, the connector was a very recent download and search as I have, I didn't even find a connector disk in the WHS OEM pack.

    The dates and times appeared to be pretty close and the time zones also.  I have an atomic clock sitting on my desk under my monitor as a reference.

    All the machines use standard Microsoft virus, spy, firewall, except the WinXP machine that still uses Symantec AV.  But of course the WinXP machine is the one with no particular problems (didn't test the connector though).

    Eric Robert Lewis, Ph.D.

    Wednesday, October 3, 2012 6:39 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Eric,

    is your WHS already completely patched? (Some patches took also care of various Connector installation issues.) So without exact errors (event log or messages)  helping you in detail is a bit difficult. 

    If a login for the server is asking for machine name, the name of the server needs to be entered.

    Best greetings from Germany
    Olaf

    Wednesday, October 3, 2012 7:40 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    The server and Win7 are completely up-to-date as far as Windows Update is concerned.  I don't know as a fact that all WHS updates are promulgated via Windows Update but that has been my experience with my WHS ver 1 server.

    The login screen is asking for the name of the server and I do supply that name.

    It is the reference to me as the person trying to login where the domain appears.  My Win7 machine is named "Z68"  My login is "Eric".  The login screen supplies "Z68\Eric" as the name trying to login.

    However, once I reset the Homegroup as described above the login screen does not even appear.  Now I access the shared folders with no explicit login required. 

    Eric Robert Lewis, Ph.D.

    Wednesday, October 3, 2012 10:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    The client PC always defaults to its own name, unless its a domain member. If the computer name is part of the authorization, server treats that as a different account than its own local user with the same name.

    In my opinion this Homegroup construction is not optimal in a mixed client/server environment, so I never use it.

    Did you install the connector from server (http://yourservername/connect)?

    Best greetings from Germany
    Olaf

    Thursday, October 4, 2012 8:24 PM
    Moderator