F5F Stay Refreshed Software Operating Systems Remote Desktop

Remote Desktop

Remote Desktop

T
TheSimple
Member
229
08-27-2016, 08:24 AM
#1
Your Windows 10 PC seems to be experiencing issues with remote access after a restart. It might help to check for software updates, run a system scan, or ensure network settings are correct. If problems persist, consider restarting in safe mode to isolate potential conflicts.
T
TheSimple
08-27-2016, 08:24 AM #1

Your Windows 10 PC seems to be experiencing issues with remote access after a restart. It might help to check for software updates, run a system scan, or ensure network settings are correct. If problems persist, consider restarting in safe mode to isolate potential conflicts.

K
kensteele
Member
114
08-27-2016, 12:55 PM
#2
Turn off remote access, apply, then turn it back on. This generally resolves the issue for me. Verify if your IP address remains unchanged. Once the DHCP lease expires, a restart initiates a fresh lease, occasionally resulting in a different address.
K
kensteele
08-27-2016, 12:55 PM #2

Turn off remote access, apply, then turn it back on. This generally resolves the issue for me. Verify if your IP address remains unchanged. Once the DHCP lease expires, a restart initiates a fresh lease, occasionally resulting in a different address.

M
Maria7300
Member
221
08-27-2016, 01:14 PM
#3
I rely on the netBIOS host name for RDP because consumer routers rarely provide stable IP addresses to identical devices.
M
Maria7300
08-27-2016, 01:14 PM #3

I rely on the netBIOS host name for RDP because consumer routers rarely provide stable IP addresses to identical devices.

K
kk900314
Junior Member
29
08-27-2016, 09:30 PM
#4
It functions adequately when connected to the same network. I frequently connect through a VPN, but NetBIOS resolution fails under that setup. That's why I favor using fixed IP addresses instead.
K
kk900314
08-27-2016, 09:30 PM #4

It functions adequately when connected to the same network. I frequently connect through a VPN, but NetBIOS resolution fails under that setup. That's why I favor using fixed IP addresses instead.

S
ScorpiorxX
Junior Member
10
08-28-2016, 03:30 AM
#5
It might be that the distant computer isn't configured to permit a link unless someone is authenticated.
S
ScorpiorxX
08-28-2016, 03:30 AM #5

It might be that the distant computer isn't configured to permit a link unless someone is authenticated.

P
Pyroytic
Member
56
08-28-2016, 10:13 AM
#6
It seems most folks prefer not to assign fixed IP addresses for everything. I gave up on OP because I had too many to remember, lol.
P
Pyroytic
08-28-2016, 10:13 AM #6

It seems most folks prefer not to assign fixed IP addresses for everything. I gave up on OP because I had too many to remember, lol.

U
USAirways
Member
157
09-14-2016, 09:23 PM
#7
I use IP addresses for my VM names, which means I don’t have to memorize them, lucky me!
U
USAirways
09-14-2016, 09:23 PM #7

I use IP addresses for my VM names, which means I don’t have to memorize them, lucky me!

C
Cupcake_Rose
Posting Freak
844
10-03-2016, 02:24 AM
#8
Good strategy, I began sharing basic IPs like 192.168.1.1 - 2 - 3, then moved to 10, 100, 101, followed by 50 and 250. Now I’m hitting 46, 48, 36 because I’m running out of options 😅
C
Cupcake_Rose
10-03-2016, 02:24 AM #8

Good strategy, I began sharing basic IPs like 192.168.1.1 - 2 - 3, then moved to 10, 100, 101, followed by 50 and 250. Now I’m hitting 46, 48, 36 because I’m running out of options 😅

G
Gladiador70
Senior Member
698
10-05-2016, 12:37 AM
#9
Thanks all!
G
Gladiador70
10-05-2016, 12:37 AM #9

Thanks all!