- My Forums
- Tiger Rant
- LSU Recruiting
- SEC Rant
- Saints Talk
- Pelicans Talk
- More Sports Board
- Fantasy Sports
- Golf Board
- Soccer Board
- O-T Lounge
- Tech Board
- Home/Garden Board
- Outdoor Board
- Health/Fitness Board
- Movie/TV Board
- Book Board
- Music Board
- Political Talk
- Money Talk
- Fark Board
- Gaming Board
- Travel Board
- Food/Drink Board
- Ticket Exchange
- TD Help Board
Customize My Forums- View All Forums
- Show Left Links
- Topic Sort Options
- Trending Topics
- Recent Topics
- Active Topics
Started By
Message
Remote Log-In on Win 10
Posted on 10/4/16 at 9:53 am
Posted on 10/4/16 at 9:53 am
I'm having trouble logging into my computer remotely in a SBS 2008 server. The tech guy is telling me this is due to an anniversary update that automatically installed on my computer.
Anyone run into this problem and know how to fix it? He's supposed to put together some steps so that he says have worked for others, but doesn't sound 100% confident that it will work for me(or everyone).
Have any of you admins run into and found a serviceable solution?
Anyone run into this problem and know how to fix it? He's supposed to put together some steps so that he says have worked for others, but doesn't sound 100% confident that it will work for me(or everyone).
Have any of you admins run into and found a serviceable solution?
Posted on 10/4/16 at 9:56 am to southernelite
Is it telling you it can't establish a connection or it can't authenticate?
Typically when I have authentication issues I've been able to get it to work by adding "localaccount\" before the user name.
Typically when I have authentication issues I've been able to get it to work by adding "localaccount\" before the user name.
Posted on 10/4/16 at 10:13 am to junkfunky
This is the error I get.
Eta: Sorry, I need to edit right quick.
This post was edited on 10/4/16 at 10:14 am
Posted on 10/4/16 at 11:03 am to southernelite
From a Technet artical
quote:
For this error message, it is the problem of the workstation Terminal Services. We rectify the problem by editing the following registry key on workstation and restart the machine.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters
Under the Parameters registry subkey, right-click each of the following values, click Delete, and then click Yes to confirm the deletion:
Certificate X509
Certificate X509
Certificate ID
Posted on 10/4/16 at 11:07 am to southernelite
after looking around a little bit (dealing with windows 7 vs 10) it looks like it's due to an update dealing with your RDP updates. But it looks like you're trying to initiate it from a website instead of just using a remote desktop session? I've never really done anything with that...anyway, I'd start with going in to your computer and rolling back the latest set of automatic updates.
go to programs and features, and find the installed updates section and try and roll them back...or you could have a system restore type rollback you could do to the before the updates were installed if it created one for you. Could be worth a shot.
go to programs and features, and find the installed updates section and try and roll them back...or you could have a system restore type rollback you could do to the before the updates were installed if it created one for you. Could be worth a shot.
Posted on 10/4/16 at 11:35 am to Doldil
I'd prefer to go through the desktop, as I have to use IE for its compatibility settings.
Is this something i can just do, or do I need him to set me to use the desktop remote?
Is this something i can just do, or do I need him to set me to use the desktop remote?
Posted on 10/4/16 at 11:40 am to southernelite
is the server you're trying to remote in to on the network you're using, or do you use the website because you're offsite?
If it's on the network you're currently on, then you should just be able to launch remote desktop connection (hit start and type remote desktop connection) and then type the server name in to the box and try to logon. It will either work or not. I imagine if you're having to go through the website that it may not be quite that simple.
I do find it odd that you're getting these errors from a 10 connecting to an older version of server. I've had issues with Remote Desktop protocol being too old because I'm connecting from an old shitty thin client to a newer server and the RDP security was simply too old to allow it to connect to the newer server, but never the other way around.
I'd still look in to the possibility of un-installing your latest updates to see if that clears something up.
If it's on the network you're currently on, then you should just be able to launch remote desktop connection (hit start and type remote desktop connection) and then type the server name in to the box and try to logon. It will either work or not. I imagine if you're having to go through the website that it may not be quite that simple.
I do find it odd that you're getting these errors from a 10 connecting to an older version of server. I've had issues with Remote Desktop protocol being too old because I'm connecting from an old shitty thin client to a newer server and the RDP security was simply too old to allow it to connect to the newer server, but never the other way around.
I'd still look in to the possibility of un-installing your latest updates to see if that clears something up.
This post was edited on 10/4/16 at 11:41 am
Posted on 10/4/16 at 11:47 am to Doldil
Oh, yeah, I'm trying to connect offsite.
Posted on 10/6/16 at 1:05 pm to Doldil
Just an update, I was able to use the remote desktop login and access the RDS gateway through that. Seems a preferable method as I saved the setting and can just click an icon and be good to go.
Posted on 10/6/16 at 1:11 pm to southernelite
quote:
I'm having trouble logging into my computer remotely in a SBS 2008 server. The tech guy is telling me this is due to an anniversary update that automatically installed on my computer.
The anniversary update made it impossible for me to surf the web. It would take minutes for page to load or it wouldn't load at all. So, I had to get rid of it and now my computer is working flawlessly.
So, it doesn't surprise me you're having issues.
Popular
Back to top
Follow TigerDroppings for LSU Football News