F5F Stay Refreshed Software Operating Systems Issue with connecting to remote desktop on Windows Technical difficulties during remote access setup

Issue with connecting to remote desktop on Windows Technical difficulties during remote access setup

Issue with connecting to remote desktop on Windows Technical difficulties during remote access setup

S
Streiyn
Posting Freak
Find
768
06-11-2023, 08:37 AM
#1
You're facing a common issue when trying to use RDP across different networks. The problem might stem from how your MacBook connects to the dorm Wi-Fi versus your home network. Since the dorm connection uses a different IP configuration, the PC name might not match what the remote client expects. Try using the exact local IP address you found and ensure it's correctly entered in the RDP settings. If the issue persists, check if the remote desktop service is running on the server side and verify firewall rules that could block the connection.
Reply
Reply
S
Streiyn
06-11-2023, 08:37 AM #1

You're facing a common issue when trying to use RDP across different networks. The problem might stem from how your MacBook connects to the dorm Wi-Fi versus your home network. Since the dorm connection uses a different IP configuration, the PC name might not match what the remote client expects. Try using the exact local IP address you found and ensure it's correctly entered in the RDP settings. If the issue persists, check if the remote desktop service is running on the server side and verify firewall rules that could block the connection.

Reply
Reply
D
dakru012
Junior Member
Find
40
06-18-2023, 01:43 PM
#2
Typically, college wireless or wired networks lack ports for hosting servers, connecting remotely, or transferring files. For remote desktop access, consider using TeamViewer and adding the device to your allowed connections.
Reply
Reply
D
dakru012
06-18-2023, 01:43 PM #2

Typically, college wireless or wired networks lack ports for hosting servers, connecting remotely, or transferring files. For remote desktop access, consider using TeamViewer and adding the device to your allowed connections.

Reply
Reply
O
OceanBear
Member
Find
103
06-19-2023, 07:46 PM
#3
Ports need not be opened just because both devices are connected to the same LAN, as access depends on specific configurations and requirements.
Reply
Reply
O
OceanBear
06-19-2023, 07:46 PM #3

Ports need not be opened just because both devices are connected to the same LAN, as access depends on specific configurations and requirements.

Reply
Reply
E
electrodude44
Member
Find
143
06-22-2023, 10:47 PM
#4
Windows RDP uses ports 3389 for TCP and 3389 for UDP traffic. Blocking these ports on local devices stops unauthorized or illegal content from spreading across the network. Typically, schools restrict RDP access to faculty computers with fixed IP addresses, ensuring better data protection.
Reply
Reply
E
electrodude44
06-22-2023, 10:47 PM #4

Windows RDP uses ports 3389 for TCP and 3389 for UDP traffic. Blocking these ports on local devices stops unauthorized or illegal content from spreading across the network. Typically, schools restrict RDP access to faculty computers with fixed IP addresses, ensuring better data protection.

Reply
Reply
K
Killa_Dx
Senior Member
Find
645
06-23-2023, 08:15 PM
#5
A dedicated IT team would block all devices on a common Wi-Fi area. This prevents any single device from reaching another and restricts access solely to the main router. The issue isn't about ports, unless the network isn't properly segmented, and it's unrelated to the Windows firewall setting if it's set to "Public."
Reply
Reply
K
Killa_Dx
06-23-2023, 08:15 PM #5

A dedicated IT team would block all devices on a common Wi-Fi area. This prevents any single device from reaching another and restricts access solely to the main router. The issue isn't about ports, unless the network isn't properly segmented, and it's unrelated to the Windows firewall setting if it's set to "Public."

Reply
Reply