Posts: 18
Threads: 11
Joined: Sep 2020
Reputation:
0
Hello all,
I'm trying to RDP into my windows laptop via wifi
I have the user account setup in windows - the remote access turned on for that account - and a fixed IP address
I've installed Remmina - and setup the new connection - with the IP address
The windows laptop wifi has not been switched off manually - so as far as I can see it is running
However when I try to access the windows laptop in Remmina - I get the response "Unable to connect to RDP Server"
I suspect this is a simple problem - but my first time trying to do this.
Can anyone help walk me through this?
Sincere thanks!
Posts: 541
Threads: 20
Joined: May 2017
Reputation:
0
On Linux, I thinks it's "Samba" that lets people share network connection with a Windows computer.
Posts: 1,849
Threads: 21
Joined: Sep 2015
Reputation:
0
[member=37219]gotLL[/member]
If Win10 make sure the windows account, if not a local, is fully qualified.
[email protected] or what MS uses...
Also may want to check firewalls..
Test by turning off Windows FW and test, then a matter of allowing incoming....
LL4.8 UEFI 64 bit ASUS E402W - AMD E2 (Quad) 1.5Ghz - 4GB - AMD Mullins Radeon R2
LL5.8 UEFI 64 bit Test UEFI Kangaroo (Mobile Desktop) - Atom X5-Z8500 1.44Ghz - 2GB - Intel HD Graphics
LL4.8 64 bit HP 6005- AMD Phenom II X2 - 8GB - AMD/ATI RS880 (HD4200)
LL3.8 32 bit Dell Inspiron Mini - Atom N270 1.6Ghz - 1GB - Intel Mobile 945GSE Express -- Shelved
BACK LL5.8 64 bit Dell Optiplex 160 (Thin) - Atom 230 1.6Ghz - 4GB-SiS 771/671 PCIE VGA - Print Server
Running Linux Lite since LL2.2
Posts: 1,849
Threads: 21
Joined: Sep 2015
Reputation:
0
(10-31-2022, 05:39 AM)gotLL link Wrote: I'm wondering if my problem at this point is that they are not connected to the same network because one PC's wifi does not have the ability to connect to the other PC's wifi
Yes, they would need to be on the same network.
If connecting NIC to NIC via a cable - it'll need to be a cross over cable, not just any patch/cat5 cable... Router/switch or hub :54:
LL4.8 UEFI 64 bit ASUS E402W - AMD E2 (Quad) 1.5Ghz - 4GB - AMD Mullins Radeon R2
LL5.8 UEFI 64 bit Test UEFI Kangaroo (Mobile Desktop) - Atom X5-Z8500 1.44Ghz - 2GB - Intel HD Graphics
LL4.8 64 bit HP 6005- AMD Phenom II X2 - 8GB - AMD/ATI RS880 (HD4200)
LL3.8 32 bit Dell Inspiron Mini - Atom N270 1.6Ghz - 1GB - Intel Mobile 945GSE Express -- Shelved
BACK LL5.8 64 bit Dell Optiplex 160 (Thin) - Atom 230 1.6Ghz - 4GB-SiS 771/671 PCIE VGA - Print Server
Running Linux Lite since LL2.2
Posts: 1,511
Threads: 140
Joined: Mar 2016
Reputation:
0
Normally, if your Wifi connection is through a router the address range would be 192.168.etc.1-254, however if you are trying to use an
ad hoc wifi connection broadcast from Windows and not through a router you most likely won't be able to use that range so the static address you have set in Windows probably won't work if it is in that range. Windows
ad hoc Wifi usually broadcasts in the 169.254.etc.1-100 range. Also make sure port 3389 is allowing RDP through your Windows firewall.
https://answers.microsoft.com/en-us/wind...bf10ed2039
This is an old link but it explains how to find the the ad hoc wifi address your Windows system is broadcasting.
https://www.dbts-analytics.com/ll3w10hentwk.html
TC
All opinions expressed and all advice given by Trinidad Cruz on this forum are his responsibility alone and do not necessarily reflect the views or methods of the developers of Linux Lite. He is a citizen of the United States where it is acceptable to occasionally be uninformed and inept as long as you pay your taxes.
![[Image: dIwB1Lt.png]](https://imgur.com/dIwB1Lt.png)
