BTW: a RDP connection attempt also fails with the message "An internal error has occurred" with Error code: 0x4 and Extended error code: 0x0!

Let's start with the basics.

In w11, is:
1) SMB 1 available & enabled?
2) Is Net framework 2.0 & 3.5 available & enabled?
3) After a failed install, are you using a program like Revo to remove all traces of the attempted install & restarting before the next install attempt?

Refer here for more initial arrow pointing http://www.mediasmartserver.net/forums/viewtopic.php?f=5&t=14639

There are other things to check, but the above are the most common failure points.

_________________
Hi All, Thanks to everyone for your continued effort to keep the MSS & WHS alive. Haven't registered yet? Please do so the moderators know your here!

ex49x/v1 (toyin w/Vail)
VGA
Q8200s w/two 30mm cooling fans
4gb Ram
Rear Casecover Cooling Mod

I had the same problem when upgrading to WIN11. I activated SMB v1 but that didnt fix it. I also activated TLS 1.x and that didnt fix it. The protocol mismatch still occurs even though I download the WHSConnector install from my HP server. The error apparently means there is a mismatch between the installed client and what the WHS server uses but I downloaded it so cant be that.
I have tried everything and no success. I did notice though if I installed the WHSConnector SW on a WIN10 version that didnt have it and the same problem occurred so its not just WIN11. However, if you had installed WHSConnector SW on a pre WIN10 like WIN7 and then did an upgrade to WIN10 it worked. Not sure if that helps someone. I vaguely recall having this problem years ago but cant remember what was done to fix it.
Having said that there is a cludge. If you install the WHSConnector SW but when it says it wont connect just leave the installed at that prompt. You will see the HP MediaSmart folder is created and the Home Server Console will work. Once you click this and the console starts you will be able to log in. So this problem is just with the installer. As long as you dont answer the failed installed with Cancel and let it sit there you can use the Home Server Console icon in the folder. Once you answer Cancel the Installer backs out everything and the icon although there says the app isnt installed.
Now a further thing you can do is to kill the installer once you get the cant connect msg. If you do this the uninstall cant run and it seems to work normally. I havent rebooted yet my WIN11 PC. I did close the Home Server Console and reconnected fine. So once I reboot I will see if it still seems installed. I will update when that outcome.
To comment on the above. Yes to .NET 3 installed. Yes REVO used to remove. SMB1 installed.

Marmour,

So your saying you got your connector working with your w11 client, if you just leave the installer warning fail window open, then log into the console, then kill the installer thru task manager?

Could you detail the kludge a bit?

_________________
Hi All, Thanks to everyone for your continued effort to keep the MSS & WHS alive. Haven't registered yet? Please do so the moderators know your here!

ex49x/v1 (toyin w/Vail)
VGA
Q8200s w/two 30mm cooling fans
4gb Ram
Rear Casecover Cooling Mod

Wow marmour- that is a huge breakthrough! I have the console up on the laptop now as you described but the pc is greyed out. I can see the backups of my past and current pcs but when I try and open one I get a "cannot connect to backup service on the server" message. Can you open backups in this state? I've just left the failed installer "operation cannot be completed" open on the desktop. thanks everyone for your efforts!

Hi makeitwork: My PCs shows as greyed out to. I dont have any backups though. I did try to enable backups and try doing one but nothing happens. So I guess that piece is not working yet. I wanted to use the console so I could shutdown, check the disks/status etc. As well the drive maps also work. I guess if the backups interface use the same transport layer as the installer then I guess it may have the same issue. I did go through an XML I found, in the installer folder on the server, and found the error message. I read previously someone looking at the certs. It may be that the cert being used on the server and on the PC is not the same and thats the problem causing the error. I saw through the diagnostic kit when I ran it than even though it said that there was a protocol mismatch it was ok however it seems the installer doesnt accept that. I saw in a thread here that someone tried to add/change certs used. I am wondering if there is something in the cert store that is missing and that is causing the issue. As I mention I enabled TLS 1.x. I think its a cert mismatch possibly by having Edge as the only browser maybe certs used by IE in the past are what is needed here.
Re Lionstreet. Yes. Run the installer once u get the cant connect to server msg. Leave it. Go to the HP Mediasmart Folder/Icon open it. Launch Home Server Console. It will connect properly. Note. If u answer Cancel to the cant connect msg the uninstall will run and the Home Server Console app is uninstalled. If u try to launch it from the HP Mediasmart folder/icon it will say app not installed. So u can rerun the WHSconnector sw as often as u want leaving it at the error and u can use the Home Server Console. Now what I tried was once that error was present, cant connect to server, I used task mgr to find the installer app running and killed the task. Once I did that the uninstaller didnt run and u can then launch the home server console.
Update - I rebooted my PC and the Home Server. After a couple of miscues, an erroneous cant find homeserverconsole.exe not sure if it was cause I tried to cancel it as my VPN was running. It works fine. So when u get the error msg about not being able to connect. Go to task mgr and kill the task running the installer. I am not sure if the backups piece is run after that connect piece is successful but possible. Someone cud maybe look into the certs and if thats the mismatch

Hi,
I have not switched to Windows 11 because of the issue discussed here. I still use Windows 10 so that I can use my old faithful WHS. Recently I had to rebuild the WHS because I had a few disk errors, and then I tried the connector software that has always worked in the past. HOWEVER, there must have been an upgrade to Windows 10 that is now preventing me from connecting to my WHS. As described by a few members, my Administrator password is not being accepted. Does anyone know what changed since Christmas 2022 to stop me connecting to my WHS? I wonder if some new policies (see secpol.msc) have been introduced?
Thanks,
Gordon

Hi Gordon,

Respectfully this is off topic and the folks who might be able to help you won't see this.
Suggest you do a quick search to see if other have the same issue... and if not then post your question as a new topic.

Kind Regards

@gordon@burlison.ca

Yes, please post your need in a new thread. I'm sure someone will help you find the reference you are looking for since this sounds like a simple fix.

_________________
Hi All, Thanks to everyone for your continued effort to keep the MSS & WHS alive. Haven't registered yet? Please do so the moderators know your here!

ex49x/v1 (toyin w/Vail)
VGA
Q8200s w/two 30mm cooling fans
4gb Ram
Rear Casecover Cooling Mod

There are a few topics on this issue of the whs connector not installing recently.
What I can say is I am using win 10 64x on two different desktops and it works flawless, always has.
One is win 10 pro and the other is win 10 home

What has been mentioned is, make sure smb1 is installed and yes it needs to be.
I will add my other settings
I have changed my settings to private network not public.
And in the same settings page I have enabled network discovery and file/printer sharing for all

_________________
EX-490
WHS v1
VGA/PS2 Keyboard/PS2 Mouse/Serial debug board
Q9450s CPU
Stock Ram
ESATA Sansdigital Towerraid TR5M-B
Popcorn C-200
Popcorn A-200
Dune HD Connect
Rasberry PI OSMC(KODI)
ReadyNAS RN316
Amazon FireStick
Amazon ECHO
AnyDvD
MyMovies