One of my colleagues can't use rdp connection to one server on spark network at all. It either takes long time to connect, or drops a few seconds after connection.
Does anyone else experience the same issue?
![]() ![]() |
You need to explain better with how it is set up.
Is this RDP over a VPN connection, or RDP directly to an IP address on the internet.
If it is RDP over the internet this is incredibly insecure and this practice should immediately be stopped. VPN is basically the only way to go.
Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)
Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.
Thanks, it is over vpn (l2tp).
michaelmurfy:
You need to explain better with how it is set up.
Is this RDP over a VPN connection, or RDP directly to an IP address on the internet.
If it is RDP over the internet this is incredibly insecure and this practice should immediately be stopped. VPN is basically the only way to go.
If the VPN is connected, sounds like there is a routing issue, are you able to ping or access anything else via the VPN?
CPU: AMD 5900x | RAM: GSKILL Trident Z Neo RGB F4-3600C16D-32GTZNC-32-GB | MB: Asus X570-E | GFX: EVGA FTW3 Ultra RTX 3080Ti| Monitor: LG 27GL850-B 2560x1440
Quic: https://account.quic.nz/refer/473833 R473833EQKIBX
Yes, ping the vpn gateway seems quite good, latency is about 30ms. NAS in the intranet also responds. I noticed that anydesk (the remote control app) took unusually long time to connect my colleague's and dropped quickly, while ms teams didn't. I am on vodafone.
mentalinc:
If the VPN is connected, sounds like there is a routing issue, are you able to ping or access anything else via the VPN?
I've seen this happen where the IP address range of the home network is the same as the IP address range of the network being VPN/RDP'd into. The routing does not work in that scenario. Change the IP range of the home network is a common way to resolve this.
“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams
Referral links to services I use, really like, and may be rewarded if you sign up:
PocketSmith for budgeting and personal finance management. A great Kiwi company.
Thanks, that's not the case in my situation.
Home ip is 192.168.1.x
VPN is 10.208.x.x
RDP are 10.208.x.x and 192.168.0.x
Dynamic:
I've seen this happen where the IP address range of the home network is the same as the IP address range of the network being VPN/RDP'd into. The routing does not work in that scenario. Change the IP range of the home network is a common way to resolve this.
![]() ![]() |