Answered by:
Bad Password on WHS Connector (PP2) and Win 7 RC x64

Question
-
So I have 2 fresh installs of Windows 7 RC x64. I've been trying to get the WHS Connector to install for the last few days with no luck.
One machine is a desktop, the other is a laptop.
I connect to the WHS page (port 55000) and download the connector software.
The installer loads (the agreement shows for Power Pack 1?), runs fine, but when I get to the password screen it says my password is incorrect.
I've disabled the firewall on both sides (although I didn't think I needed to), have changed the password numerous times (the password hint link shows my new password hint every time).
I can log into the console, and RDP with my password, so I know it's correct.
Any help is appreciated.Sunday, May 3, 2009 3:32 PM
Answers
-
I've been having the same problem connecting to WHS with the Win 7 RC, both 64 and 32 bit installs. Been driving me crazy! However, I think I found the solve:
The LAN Manager authentication level has no default value. If you set this to 'Send NTLM response only' it will accept the password and connect to WHS.
Run secpol.msc
Drill down through Local Policies | Security Options.
Find Network Security: LAN Manager authentication level.
Set this Send NTLM response only.
- Edited by Dan Parkinson Sunday, May 17, 2009 5:54 AM
- Proposed as answer by kariya21Moderator Sunday, May 17, 2009 6:39 PM
- Marked as answer by kariya21Moderator Monday, May 18, 2009 10:58 PM
Sunday, May 17, 2009 5:54 AM
All replies
-
So I have 2 fresh installs of Windows 7 RC x64. I've been trying to get the WHS Connector to install for the last few days with no luck.
One machine is a desktop, the other is a laptop.
I connect to the WHS page (port 55000) and download the connector software.
The installer loads (the agreement shows for Power Pack 1?), runs fine, but when I get to the password screen it says my password is incorrect.
I've disabled the firewall on both sides (although I didn't think I needed to), have changed the password numerous times (the password hint link shows my new password hint every time).
I can log into the console, and RDP with my password, so I know it's correct.
Any help is appreciated.
Are you getting the same error from both clients? Are you trying to install the software as an administrator? Do you have any other software in common on both clients?Sunday, May 3, 2009 4:25 PMModerator -
I am installing the connector as an admin on both clients. I also tried copying the WHS Connector folder from my Software folder to a thumb drive and that didn't install either.
Both Windows 7 installs are clean, with the laptop only having Symantec AnitVirus Corp 10.2 and XP Mode, while the desktop only has the SAV 10.2 and Office 2007.
On the laptop, WHS Connector was the first piece of software I tried to install, since I wanted access to my Software share where all my software is. I had to copy my AV program to thumb drive so that my laptop wasn't running without any.
Same exact error from both clients.Sunday, May 3, 2009 4:30 PM -
Hi,
please check the event log on the server.
Especially interesting are COM and ASP errors, also informational messages from RDPDD.DLL, which mention, that it failed to load. The first two could be caused by misconfigured IIS, the later by issues with an NVidia graphics driver on the server.
Eventually also the Windows Firewall on the server is not configured properly, you can try to temporary stop the firewall service locally on the server.
Did the configuration also fail without the virus scanner installed (since Symantec security software has been mentioned in other threads as a potential cause for errors with the connector software)?
Best greetings from Germany
OlafSunday, May 3, 2009 5:13 PMModerator -
I only have one instance of the below error.
Event Type: Error
Event Source: ASP.NET 2.0.50727.0
Event Category: Setup
Event ID: 1024
Date: 4/24/2009
Time: 7:15:55 PM
User: N/A
Computer: WOOT
Description:
Failed while restarting W3SVC. Error code: 0x8007041bFor more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------------------------------------------------
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 4/25/2009
Time: 7:55:28 AM
User: NT AUTHORITY\NETWORK SERVICE
Computer: WOOT
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{BA126AD1-2166-11D1-B1D0-00805FC1270E}
to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-------------------------------------------------
It does not have any NVidia hardware in it at all.
Yes it still failed without Symantec installed. That was the first thing I tried to do on my laptop was install the Connecter and then get to my shares, where my Symantec installlation folders are.Sunday, May 3, 2009 6:21 PM -
Hi,
that one error happened after a reboot?
Did you install anything else using Internet Information Services like SharePoint services on your WHS?
You can try to search the registry on the server for the CLSID to figure out, to which component the error is pointing.
If this is something in relation to WHS, you could adjust the permissions for that component as requested in Control Panel/Administrative Tools/Component Services and grant the Network Service account the local activation permission on the server. (I had a similar experience on one machine after installing Powerpack 1.)
Best greetings from Germany
OlafSunday, May 3, 2009 6:53 PMModerator -
No, no IIS related programs, but I am using a Add-In that allows streaming of Videos and Music. I'll try uninstalling. Edit: Didn't solve the problem.
When searching the registry for that CLSID it comes up with entries for Network Connection Manager Class.
What object do I need to edit permissions on in Component Services, netman?- Edited by Mikael Doyle Sunday, May 3, 2009 8:55 PM
Sunday, May 3, 2009 8:06 PM -
What object do I need to edit permissions on in Component Services, netman?
yes, netman is right.
Also be aware, that sometimes changes may only reflect themself in proper action after rebooting server and/or client.
Best greetings from Germany
OlafSunday, May 3, 2009 9:04 PMModerator -
That didn't fix it.
Sunday, May 3, 2009 9:20 PM -
Did you check the security log of the server?
Best greetings from Germany
OlafSunday, May 3, 2009 10:34 PMModerator -
What am I looking for in the security log? Everything I have says succesful audit.Monday, May 4, 2009 4:46 AM
-
Try to filter for failures. (Successfull audits too often overflood the log.)
Best greetings from Germany
OlafMonday, May 4, 2009 7:26 AMModerator -
I only have succesful audits.Tuesday, May 5, 2009 1:11 AM
-
If you click Start/Run on the server desktop, type services.msc, click OK and sort the services by Startup type - is there any service of those set to autostart not started (besides Performance Logs and Alerts)?
Best greetings from Germany
OlafTuesday, May 5, 2009 8:46 AMModerator -
Nope.
I should note that the Vista machine that had the console already installed is fine. It can access all shares, and it backs up fine.Thursday, May 7, 2009 1:15 AM -
Nope.
I should note that the Vista machine that had the console already installed is fine. It can access all shares, and it backs up fine.
Hi,
Please submit a bug on Connect and include client and server CABs. The x64 version of Windows 7 should work. I'm running it on 2 machines.
Thanks.
Lara Jones [MSFT] | Program Manager
Community Support and Beta | Windows Home Server Team
Windows Home Server Team Blog
Connect Windows Home Server
Windows Home ServerThursday, May 7, 2009 6:14 PMModerator -
Friday, May 8, 2009 12:43 AM
-
I havent heard from anyone. How long does it usually take before you get a response back?Saturday, May 9, 2009 12:30 AM
-
I havent heard from anyone. How long does it usually take before you get a response back?
Hi,
If we need information from you we will contact you after the bug has been triaged and that usually takes between 24 to 72 hours depending when the bug was submitted i.e. holidays/weekends. If we do not need additional information, we will forward the bug to a developer for review. Once we here back from the developer, we pass on the information to you.
Thank you
Lara Jones [MSFT] | Program Manager
Community Support and Beta | Windows Home Server Team
Windows Home Server Team Blog
Connect Windows Home Server
Windows Home ServerSaturday, May 9, 2009 1:03 AMModerator -
I just wanted to add that I too am having the same problem. At first I thought it was the x64 version that I installed by accident, I installed the 32 bit and still the same thing. Im coming from the Win7 beta with no problems at all. I have no add ins installed on the server, and no spyware, firewall or antivirus installed on the Win7 RC machine.Saturday, May 9, 2009 7:20 PM
-
Yeah I kind of figured it was either a problem with PP2 and the RC or PP2 and Win 7 period. It ran fine on the beta, and it just so happens that PP2 and the RC came out at almost the same time.
Hopefully we get a fix. I miss all my music that is sitting on my WHS and i'm not able to hear it.Sunday, May 10, 2009 3:37 AM -
Any news about this as of yet? I'm having the same issues with this and its driving me mad.
Tuesday, May 12, 2009 8:09 PM -
Any news about this as of yet? I'm having the same issues with this and its driving me mad.
This has been assigned to a developer; however, please keep in mind that Windows 7 is not a released product and as such, there may bugs associated with certain builds.
Lara Jones [MSFT] | Program Manager
Community Support and Beta | Windows Home Server Team
Windows Home Server Team Blog
Connect Windows Home Server
Windows Home ServerTuesday, May 12, 2009 8:17 PMModerator -
Ok one thing I just noticed.
The installer creates a directory in Program Files (x86), not in my Program Files folder like it should, since there is a 64 bit client, am I correct?
I moved the 32 bit .msi out of the install directory and ran setup again. It still created the WHS folder in my 32 bit folder.
Don't know if that could be part of the issue, or this is even an issue, just doesn't seem right to me.Wednesday, May 13, 2009 12:23 AM -
Hi,
I overlooked a part in one of your former postings:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {BA126AD1-2166-11D1-B1D0-00805FC1270E}
To solve this:
- Open regedit on your server and search, what is there behind that CLSID (in registry editor press F3 and paste that above key). Find it and open the key to check, what is behind that. On my WHs it represents the Network Connection Manager Class, so it should be for you as well.
- Open Control Panel/Administrative Tools/Component Services.
- Navigate to Component Services/Computers/My Computer/DCOM Config, right click netman and select Properties.
- On the Security tab click the Edit button for Launch and Activation Permissions.
- Add Network Service and check the box Allow for Local Launch and Local Activation.
- Click OK to confirm and close the windows.
- After finishing configuration, try again to access the server.
OlafWednesday, May 13, 2009 6:23 AMModerator -
Nope, that didnt work either. What bothers me, is that I cant even browse the server through network. I could see if the connector software and backups didnt work, but just browsing?Wednesday, May 13, 2009 3:10 PM
-
Nope, that didnt work either. What bothers me, is that I cant even browse the server through network. I could see if the connector software and backups didnt work, but just browsing?
Have you tried these steps in the FAQ to fix the problems with the shares? You might also try creating a new user on the Windows 7 machine and then creating a new user account in the Windows Home Server console and see if this repros. If it does not, then there is something wrong with your specific account.
Lara Jones [MSFT] | Program Manager
Community Support and Beta | Windows Home Server Team
Windows Home Server Team Blog
Connect Windows Home Server
Windows Home ServerWednesday, May 13, 2009 3:26 PMModerator -
Nope, that didnt work either. What bothers me, is that I cant even browse the server through network. I could see if the connector software and backups didnt work, but just browsing?
Have you tried these steps in the FAQ to fix the problems with the shares? You might also try creating a new user on the Windows 7 machine and then creating a new user account in the Windows Home Server console and see if this repros. If it does not, then there is something wrong with your specific account.
Lara Jones [MSFT] | Program Manager
Community Support and Beta | Windows Home Server Team
Windows Home Server Team Blog
Connect Windows Home Server
Windows Home Server
I read through the FAQ, I dont think that is the issue, because trying to logon as Admin stills gives incorrect password.
I also tried to create a new user both on the server and the win 7 machine, and the same thing comes up telling that the password is incorrect.Wednesday, May 13, 2009 5:37 PM -
I read through the FAQ, I dont think that is the issue, because trying to logon as Admin stills gives incorrect password.
I also tried to create a new user both on the server and the win 7 machine, and the same thing comes up telling that the password is incorrect.
What are the regional settings on the Windows 7 machine verses the regional settings on the server? Do the keyboard layouts match?
Lara Jones [MSFT] | Program Manager
Community Support and Beta | Windows Home Server Team
Windows Home Server Team Blog
Connect Windows Home Server
Windows Home ServerWednesday, May 13, 2009 5:42 PMModerator -
Im not really sure, although I am using the onscreen keyboard as this is a living room/HTPC. Im just using a wireless mouse. As far as entering the password, I am copying it from a text document that I have on the desktop I have also been entering it via the onscreen keyboard. So I can verify that the password is indeed correct.Wednesday, May 13, 2009 5:59 PM
-
I can tell you that my regional settings on both of my 7 machines and my Home Server match.
I agree with stidrvr. This is NOT only client issue. We cannot connect to anything except Remote Desktop on our Home Servers.
Fully qualifying any user account, new or old, matching on client and server or not matching, and the administrator will not open ANY connection to the WHS.Thursday, May 14, 2009 1:12 AM -
Mike, Are you using an existing install of WHS? Since I have an extra harddrive to put my files on, I'm thinking of doing a server reinstall just to rule that out. My backups can be deleted as I plan to upgrade the laptop to Win7 anyway. Even though this probally isn't the issue I guess it could be worth a shot.Thursday, May 14, 2009 2:14 AM
-
Yeah i'm using an existing WHS install.
I was just thinking that I have a spare hard drive for my laptop and I was going to try and install the 32 bit version of 7 RC to see if the problem lies in the 64 bit version.
Although, I could ask what version you are running first, heh.
My WHS re-install would be a little more tideous, although I don't mind trying.
If you also had a existing install, did you ever try to connect to your WHS pre-PP2 with the 7 RC?
I know I never did.- Edited by Mikael Doyle Thursday, May 14, 2009 2:37 AM
Thursday, May 14, 2009 2:34 AM -
I'm using the 32bit version. When downloaded the ISOs the renamed them incorrectly and actually installed the 64bit by accident thinking that it was the 32bit. When I saw this I thought that this may be the cause, so I reinstalled using the 32bit version only to have the same thing happen. So short story long..... I am using 32bit. I can fit everything on my spare 1tb harddrive, so maybe tonight when I get home from work I will give that a try. I will definately make sure to try before PP2 is installed.Thursday, May 14, 2009 2:49 AM
-
I'm using the 32bit version. When downloaded the ISOs I renamed them incorrectly and actually installed the 64bit by accident thinking that it was the 32bit. When I saw this I thought that this may be the cause, so I reinstalled using the 32bit version only to have the same thing happen. So short story long..... I am using 32bit. I can fit everything on my spare 1tb harddrive, so maybe tonight when I get home from work I will give that a try. I will definately make sure to try before PP2 is installed.Thursday, May 14, 2009 2:58 AM
-
Did you ever use the Beta of 7?
Interesting. BTW, you shouldn't have to re-install WHS on a new drive. You can boot from CD and there is an option to use an existing install. It just remembers all your backups, shares and whatever data you have in them without deleting. I've done it once, works great.
I'll probably get started re-installing WHS here in a few on a new drive to try it out myself.Thursday, May 14, 2009 3:10 AM -
Another thing. What software do you have on your computer?
Office 2007
Firefox
NCP Client (3rd party vpn for Cisco x64)
Symantec Corporate 10.2
XP Mode
uTorrent
Adobe Reader
My laptop has all the same software except for Firefox, uTorrent and NCP Client.
Are you running XP Mode?Thursday, May 14, 2009 4:13 AM -
Well. I just got done re-installing my WHS. No go. All I did was install my NIC driver and try to connect to a share on my WHS and all passwords on all the new user accounts I set up failed.Thursday, May 14, 2009 4:25 AM
-
Hmm perfect timing for me I guess. I just got home.
I was using the Win 7 Beta and it worked perfectly. The only reason that I wanted to install RC was because of the .dll issue with the DVD decoder in the Beta. I want to strictly use the computer as a Media Center computer and nothing I tried, VLC, K-Lite etc. works for playing VOB rips of dvd's through the network with Media Center after the experation of the .dll's. I found instructions on how to redo the .dll's but counldnt understand.
I think we're at the mercy of the Bug experts.
The only thing that I had installed on the Win 7 Beta was AnyDVD.
As for now, I have nothing extra installed. Not even drivers!- Edited by stidrvr Thursday, May 14, 2009 4:47 AM
Thursday, May 14, 2009 4:45 AM -
Damn. Well thanks for letting me know you don't have anything on that 7 install. Now I don't have to kill my XP VM.
I am extremely curious as to why this is happening though. I might install some of the builds between 7000 and 7100 and see if any of those give this issue.
And the most unfortunate thing about this: It looks like 7 is going to go RTM in the next 3-6 months which means we (probably) wont see a fix until then.Thursday, May 14, 2009 4:58 AM -
Yeah, thats the way its looking.
I unfortunately dont have any other builds except the Public Beta. Although its seems as though the logon box to other computers is different in RC the it was in Public Beta. Im wondering if its something in there that was broken between the two builds.
Whats really odd is that some people have no problems.
Out of curiosity what hardware are you using?
Im using a GIGABYTE GA-E7AUM-DS2H on board Video, Audio, LAN
Im wondering is this is hardware related... possibly?Thursday, May 14, 2009 5:20 AM -
Maybe. I'm using a Intel DQ35 board with on board video, audio, and lan.
Eh. After looking up your board I would say they are absolutely nothing alike.- Edited by Mikael Doyle Thursday, May 14, 2009 5:26 AM
Thursday, May 14, 2009 5:23 AM -
grrrr...
Well it was worth a short.Thursday, May 14, 2009 5:44 AM -
Wait. I just thought of something. Both of our boards have integrated RAID Controllers.Thursday, May 14, 2009 5:49 AM
-
Good point, although I think yours is Intel, and mine is, well, I have no idea. I couldnt find that out. But didnt you install on 2 systems? Are these 2 systems the same?
I have another system that I could install on but its ancient, AMD XP2000 but it has onboard IDE RAID, and the power supply needs a little jump start to get going :)
I guess I could try it on the laptop, but I guess I dont know what that would prove.Thursday, May 14, 2009 6:18 AM -
I've now tried it on 2 different WHS installs, but both with the same hardware. I have another board without RAID I could try this on. Probably be tomorrow after work though.Thursday, May 14, 2009 6:37 AM
-
In my on going attempt to try and figure out what is wrong with this. I came across this screen. Maybe this can help shed light on where the permissions don't match between 7 RC and WHS.
I get this error when doing a Troubleshoting Wizard for Network Shares. I use \\woot when asked what share to connect to.
http://img200.imageshack.us/my.php?image=capturehoc.jpg- Edited by Mikael Doyle Saturday, May 16, 2009 7:33 PM
Saturday, May 16, 2009 6:35 PM -
I've been having the same problem connecting to WHS with the Win 7 RC, both 64 and 32 bit installs. Been driving me crazy! However, I think I found the solve:
The LAN Manager authentication level has no default value. If you set this to 'Send NTLM response only' it will accept the password and connect to WHS.
Run secpol.msc
Drill down through Local Policies | Security Options.
Find Network Security: LAN Manager authentication level.
Set this Send NTLM response only.
- Edited by Dan Parkinson Sunday, May 17, 2009 5:54 AM
- Proposed as answer by kariya21Moderator Sunday, May 17, 2009 6:39 PM
- Marked as answer by kariya21Moderator Monday, May 18, 2009 10:58 PM
Sunday, May 17, 2009 5:54 AM -
Dan, that workaround finally lets me connect to server shares.
The Connector software also has finally installed.
Thank you Dan!!Sunday, May 17, 2009 2:27 PM -
I've been having the same problem connecting to WHS with the Win 7 RC, both 64 and 32 bit installs. Been driving me crazy! However, I think I found the solve:
The LAN Manager authentication level has no default value. If you set this to 'Send NTLM response only' it will accept the password and connect to WHS.
Run secpol.msc
Drill down through Local Policies | Security Options.
Find Network Security: LAN Manager authentication level.
Set this Send NTLM response only.
Dan, you are a genius!!! Thank You So much, it now owrks for me too.Monday, May 18, 2009 4:14 PM -
Was this done at the Win 7 RC machines or on the WHS?Tuesday, June 23, 2009 2:02 AM
-
I did all of that but I am still unable to install connector.
Problem started when I had a MB failure on one of the clients. Replaced the MB and installed new HD's and restored to new Unit (Windows 7 RC).
Unable to install the connector after this restore on a new Vista 32 Unit.
When back to the W7RC unit and was unable to connect to the console.
I then went to my other W7RC computer with like results.
RDT works fine on all 6 of my computers.
I have reset the passwords on all computers including the WHS for all WHS users. All of the latest updates are on all affected compters.
Note: I also looked at the information on edit of the registory BUT I will not go there. Reason; I would not know how to do it. I am not a computer repair person; I just take a lot of photos and share with my friends.
If it works, work on it until it is broke.- Proposed as answer by cazeclosed25 Friday, July 10, 2009 12:17 PM
Saturday, July 4, 2009 5:51 PM -
Make sure that the dates on all computers match as well as time and zone. been having same problem for quit some time now and thats all it was. router was set for central cpus eastern. and for some reason the date on 7100.1700 seems to install exactly one week slow. its always somthing stupid. ____ ive plugged away for days and read till my eyes hurt. However this mountian is mine now LOL.
- Proposed as answer by Fastphoto Wednesday, August 19, 2009 6:43 PM
Friday, July 10, 2009 12:23 PM -
Make sure that the dates on all computers match as well as time and zone. been having same problem for quit some time now and thats all it was. router was set for central cpus eastern. and for some reason the date on 7100.1700 seems to install exactly one week slow. its always somthing stupid. ____ ive plugged away for days and read till my eyes hurt. However this mountian is mine now LOL.
Sorry but I clicked on the wrong "Vote" as answer. However I have corrected the problem by giving the Guest account permission to make changes. All 6 of my computers are backing up whenever they are booted up. Thanks for all of the tips but I received the correct answer from Tom out in Washington state. Some time ago, I was his bull in the china closet when we put together the Whiist Website Construction project. He will attest to my computer knowledge.
If it works, work on it until it is broke.Wednesday, August 19, 2009 6:53 PM -
Hi,I started having this password problem when I installed windows 7 last night (10/22/09).
Until yesterday, on my desktop I was using windows 7 release candidate (64-bit), and Vista Ultimate (32-bit) on my laptop, and had no problems connecting to WHS. On both machines, I did the "clean install" method and wiped the existing system for a fresh install.
I checked the security setting on WHS as mentioned above. It was already correct.
I confirmed that all computers and my router are synchronized with the same NTP server, and have the correct time.
Details
Desktop and Laptop running windows 7 home premium 64 bit and nothing else (I tried this even before I installed anti-virus)
home server running version 5.2 sp2 (always kept up-to-date)
Symptoms:
Remote desktop works fine
File sharing - did not ask for a password on the desktop computer, but did ask on the laptop
WHS connector - fails at the password prompt. Tells me the password is incorrect. I do not have caps lock turned on, and as I mentioned above, I can log in to WHS using remote desktop (with the same password, so I know it's right).
Thanks!Friday, October 23, 2009 9:29 AM -
Not a good idea, to attach your question to an already solved thread instead of opening a new question (maybe with a reference to the thread).
Please check the event log of the server for errors and warnings (especially COM or DCOM may become interesting).
Did you try to install the Connector software from http://yourservername:55000?
Best greetings from Germany
Olaf- Proposed as answer by Imalone Friday, October 23, 2009 4:29 PM
Friday, October 23, 2009 10:00 AMModerator -
ok all try this:
On HS go to "Administrative Tools", "Component Services"
Go to "Computers", right click on "My Computer", "Properties", "COM Security", go to "Launch and Activation Permissions" and click on "Edit Default" button
Add the local HS IUSR_xxxx id with "Remote Activation" rights
This should now fix the "incorrect Password" prompts everytime you try to install the Connector software.Friday, October 23, 2009 4:36 PM -
I eventually fixed the problem by reinstalling WHS and not installing the power pack 3 beta. I think the PP3 beta may have been the issue, it was designed for Windows 7 RC1 not RTM, which i've been discovering are fairly different versions. A lot of hacks/tweaks/apps that worked fine with RC1 do not work well yet with RTM. I'm waiting for the official PP3 to come out before installing it again.Thursday, October 29, 2009 4:06 PM
-
I am having the same problem, but secpol.asc doesn't exist on the home premium version, right? And it makes sense that since this is a home server, it should work with the home guest OS.Friday, October 30, 2009 2:39 AM
-
I may have found my problem, got looking more closely at my server, and the system time was way off...like 2004. Changed it and rebooted and it works now :) I think that was causing the certificate to not look valid?
- Proposed as answer by Kandamangalam Friday, November 6, 2009 7:57 PM
Friday, October 30, 2009 3:03 AM -
I finally fixed the problem by seting the Home Server system date right.
I had the same problem as it was explained here. Installed Windows 7 Ultimate and unable to connect Home Server even though I can remote in. I know my password is correct and the connector keep complaining about the password. Tried many trick but nothing works until setting the Home Server Clock (Sysrtem Date) right.
I noticed that my home server clock was showing some March of 2007. I set it to current date and came back to Windows 7 and it connected fine.
Thanks "miahshodan" for you solution.
(I still don’t understand why Home Server Clock is off the track. Is it running backwards or something???)Friday, November 6, 2009 8:05 PM -
I finally fixed the problem by seting the Home Server system date right.
I had the same problem as it was explained here. Installed Windows 7 Ultimate and unable to connect Home Server even though I can remote in. I know my password is correct and the connector keep complaining about the password. Tried many trick but nothing works until setting the Home Server Clock (Sysrtem Date) right.
I noticed that my home server clock was showing some March of 2007. I set it to current date and came back to Windows 7 and it connected fine.
Thanks "miahshodan" for you solution.
(I still don’t understand why Home Server Clock is off the track. Is it running backwards or something???)
Chances are your CMOS battery on your server mobo is dying.Saturday, November 7, 2009 12:02 AMModerator -
I am still having the same problem but my system time is the same on all my computers. I have posted my issue on Connect but there still is no reply. The "Workaround" states to use secpol.msc to change some values but the Home Premium version of Win 7 does not have secpol.msc installed.
I am becoming more discontented with WHS each day. I have problems everyday on this server ranging from indexing issues, to corrupted files, to connection problems, not to mention various fault bucket problems having no descriptions.
I just tried the solution provided above by Iamlone with no success.Saturday, November 7, 2009 12:49 AM -
For all you Home Premium users, try this, it worked for me.
Open regedit and go to
HKLM > SYSTEM > CurrentControlSet > Control > Lsa
Right click the Lsa directory, and add a new DWORD with LmCompatibilityLevel as the name and a value of 0Wednesday, December 16, 2009 2:51 PM -
Just tried your suggestion Mikael. Did not work for me. Same as always, I can remote into the server, I can see the website across the internet, I can map drives to WHS, I can stream music to my xbox from WHS, I just cannot use the connector.
In addition, with the last connector update, I lost the ability to connect using XP which worked fine previously.Thursday, December 17, 2009 1:00 AM -
That's it. I've had enough. If I wanted to do endless tweaking for no gain I thought it would be a Linux product not a Microsoft product.
All I wanted was something easy to setup and run without issue. I think that the amount of time I've tried to get this thing to stay working over the past year and a half is definitely not worth it. I wish to have my computers work for me not the other way around.
I've built computers for many years, and not since Windows 3.1 have I encountered more problems with an OS than WHS.
P.S. I have a copy of Windows Home Server for sale if anyone is interested; I will certainly not be using it.Thursday, December 17, 2009 3:19 AM -
Thank you cazeclosed25!!! The mountain is mine also. New years is here and when I lost my date / time in BIOS after a HTPC crash yesterday I reset Windows 7 Home Premium x64 HTPC to 1/5/2009 in BIOS instead of 2010...duh... 5 hours, 1 deleted admin account, some learning about permissions and groups, and 2 bare metal restores from Home Server later I go to bed very tired. Poking briefly on the web today I read your post about the date and viola - all is well again in the world!!! And sorry, I too clicked on the wrong answer for vote. Client system time synch with server was the ticket.Thursday, January 7, 2010 3:45 AM
-
So here is something I discovered.
I am running Windows 7 Ultimate and a WHS. I had to recover the server due to some work I was doing on my network.
So I also run a CISCO VPN client to connect to my WAN at work. I spent a day and a half trying to get my WHS connected after I recovered it. What I found was that if my VPN was connected I would get a server not found error when installing the WHS connector. When my CISCO VPN client was disconnected it all worked fine.
May not help anyone but there is definately an interaction there.
CAW- Proposed as answer by sgtgibson72 Sunday, March 21, 2010 11:32 PM
Sunday, January 31, 2010 4:39 AM -
I just found out i had to go into secpool.msc.turn on the ntlm then it started to work
Sunday, March 21, 2010 11:34 PM -
I had the same problem.
My fix was to "re-enable" the Administator account in WHS.
I'm so used to disabling the default Admin account, I didn't think that would have caused this problem.
Hope this helps someone.
Friday, March 26, 2010 8:22 AM -
FYI, The date issue was also my problem. I had a date 3 of 2007 on the server and it also caused the server to not update properly. Fixed the date, updated the server and restarted everything. Not it works perfectly on Laptop running XP and PC running windows 7 64bit. Thanks!Saturday, March 27, 2010 7:03 PM
-
Finally a solution, this has been driving me nutz for weeks. I bought a new Samsung 900 series PC during the MS Retail store 25% off sale and haven't been able to get connected to my windows home server via the connector software, while RDP, and everything else worked fine. With this simple fix I'm connected, backed up and everything is working. Thank You Dan!Wednesday, January 18, 2012 5:23 AM