Jump to content

Just moved into college and have been trying to use Microsoft RDP to control my Windows PC from my MacBook. I was able to do this before in my home network on wifi.

However, it gives me an error saying to change the name of the PC to the IP address. I found the local IPv4 address and put it in the field, try to connect, and it fails saying that the PC isn't connected or whatever.


Is it different since I'm at a dorm wifi connection? How can I remedy this? All the other Remote Desktop connection apps really suck and I prefer Window's built in one...

Link to comment
https://linustechtips.com/topic/824053-windows-remote-desktop-problem/
Share on other sites

Link to post
Share on other sites

4 minutes ago, Quinquangular said:

Just moved into college and have been trying to use Microsoft RDP to control my Windows PC from my MacBook. I was able to do this before in my home network on wifi.

However, it gives me an error saying to change the name of the PC to the IP address. I found the local IPv4 address and put it in the field, try to connect, and it fails saying that the PC isn't connected or whatever.


Is it different since I'm at a dorm wifi connection? How can I remedy this? All the other Remote Desktop connection apps really suck and I prefer Window's built in one...

In most cases, college wireless or wired networks will not have ports open that allow you to host a web server, RDP connection, or FTP connection. If you really need to RDP into your desktop, I would suggest that you use TeamViewer and add the computer to your always allow connections list in your account.

Make sure to quote me or use @PorkishPig to notify me that you replied!

 

 

Desktop

CPU - Ryzen 9 3900X | Cooler - Noctua NH-D15 | Motherboard - ASUS TUF X570-PLUS RAM - Corsair Vengeance LPX DDR4-3200 32GB Case - Meshify C

GPU - RTX 3080 FE PSU - Straight Power 11 850W Platinum Storage - 980 PRO 1TB, 960 EVO 500GB, S31 1TB, MX500 500GB | OS - Windows 11 Pro

 

Homelab

CPU - Core i5-11400 | Cooler - Noctua NH-U12S | Motherboard - ASRock Z590M-ITX RAM - G.Skill Ripjaws V DDR4-3600 32GB (2x16)  | Case - Node 304

PSU - EVGA B3 650W | Storage - 860 EVO 256GB, Sabrent Rocket 4.0 1TB, WD Red 4TB (x6 in RAIDZ1 w/ LSI 9207-8i) | OS - TrueNAS Scale (Debian)

Link to post
Share on other sites

1 minute ago, Homeless_Pineapple said:

In most cases, college wireless or wired networks will not have ports open that allow you to host a web server, RDP connection, or FTP connection. If you really need to RDP into your desktop, I would suggest that you use TeamViewer and add the computer to your always allow connections list in your account.

Are ports required to be opened even though it's a LAN connection since both laptops are on the same network?

Link to post
Share on other sites

Just now, Quinquangular said:

Are ports required to be opened even though it's a LAN connection since both laptops are on the same network?

Windows RDP relies on ports 3389 for TCP or 3389 for UDP connections. Keeping this ports closed to computers on a local network helps prevent unwanted or illegal content distribution on campus to other computers. In most cases, schools will only allow RDP access to secure computers of faculty with static IP addresses, where they can guarantee data security.

Make sure to quote me or use @PorkishPig to notify me that you replied!

 

 

Desktop

CPU - Ryzen 9 3900X | Cooler - Noctua NH-D15 | Motherboard - ASUS TUF X570-PLUS RAM - Corsair Vengeance LPX DDR4-3200 32GB Case - Meshify C

GPU - RTX 3080 FE PSU - Straight Power 11 850W Platinum Storage - 980 PRO 1TB, 960 EVO 500GB, S31 1TB, MX500 500GB | OS - Windows 11 Pro

 

Homelab

CPU - Core i5-11400 | Cooler - Noctua NH-U12S | Motherboard - ASRock Z590M-ITX RAM - G.Skill Ripjaws V DDR4-3600 32GB (2x16)  | Case - Node 304

PSU - EVGA B3 650W | Storage - 860 EVO 256GB, Sabrent Rocket 4.0 1TB, WD Red 4TB (x6 in RAIDZ1 w/ LSI 9207-8i) | OS - TrueNAS Scale (Debian)

Link to post
Share on other sites

Any IT Dept worth their salt would isolate all hosts on a shared wireless LAN.  That stops one host communicating with another and only allows access to the default gateway.  

 

It's got nothing to do with ports, unless the wireless network is not isolated, and  the software firewall on your PC (Windows firewall) has switched to "Public" which would stop RDP.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×