Unable to Remote Desktop (RDP) to VPN Host
-
- Posts: 17
- Joined: Tue Jan 28, 2014 12:49 am
Unable to Remote Desktop (RDP) to VPN Host
I have six machines on my home network and I have SoftEther Server running on one of them so that I can VPN into my home network from work and log into any of my home machines using Remote Desktop (RDP).
This works great for all machines except the machine SoftEther Server is running on. I can RDP into one of machines and then RDP from that machine to the VPN host, but cannot RDP directly into the VPN host machine. I have tried using the hostname, FQDN and IP but it will not connect from outside. Any help? Thanks.
This works great for all machines except the machine SoftEther Server is running on. I can RDP into one of machines and then RDP from that machine to the VPN host, but cannot RDP directly into the VPN host machine. I have tried using the hostname, FQDN and IP but it will not connect from outside. Any help? Thanks.
-
- Posts: 153
- Joined: Fri Oct 11, 2013 4:00 pm
Re: Unable to Remote Desktop (RDP) to VPN Host
Can you ping the machine ? Did you not use SecureNat and create a local bridge to you're hub ?
-
- Posts: 17
- Joined: Tue Jan 28, 2014 12:49 am
Re: Unable to Remote Desktop (RDP) to VPN Host
No, I did not use SecureNAT as I had a hard time understanding the setup and purpose of it. I'll look into setting that up. Thank you for the info.
-
- Posts: 17
- Joined: Tue Jan 28, 2014 12:49 am
Re: Unable to Remote Desktop (RDP) to VPN Host
Well, it's really strange. I can RD into the VPN host machine using my laptop and a VZW hotspot connection, but I can't using my work PC. I don't think it's got anything to do with network connections because I can hit every other machine on my network when VPN is connected. Do I need to use SecureNAT?
Also...I cannot ping the machine using the hostname, IP or FQDN. However, I can perform an nslookup on the hostname and it finds the proper IP and vice versa.
Also...I cannot ping the machine using the hostname, IP or FQDN. However, I can perform an nslookup on the hostname and it finds the proper IP and vice versa.
-
- Posts: 5
- Joined: Fri Jul 18, 2014 3:15 pm
Re: Unable to Remote Desktop (RDP) to VPN Host
Same problem here, unless I cannot RDP to any machine in the LAN I'm connecting to. Any help?
-
- Posts: 370
- Joined: Fri Oct 18, 2013 8:15 am
Re: Unable to Remote Desktop (RDP) to VPN Host
dav wrote:
> Same problem here, unless I cannot RDP to any machine in the LAN I'm
> connecting to. Any help?
http://www.vpnusers.com/viewtopic.php?f=7&t=2790
> Same problem here, unless I cannot RDP to any machine in the LAN I'm
> connecting to. Any help?
http://www.vpnusers.com/viewtopic.php?f=7&t=2790
-
- Posts: 5
- Joined: Fri Jul 18, 2014 3:15 pm
Re: Unable to Remote Desktop (RDP) to VPN Host
Ok then...
1. Operating system name and the type of CPU-bits
SO: Windows Server 2008 Standard 64bits
CPU: Intel i3-2100
2. The result of "ifconfig –a" (UNIX) or "ipconfig /all" (Windows)
C:\Users\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : BAS
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connectio
n
Physical Address. . . . . . . . . : 34-40-B5-87-E8-C5
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d88e:80e:b3d4:a56a%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.30.29(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.30.1
DHCPv6 IAID . . . . . . . . . . . : 238305461
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-0F-1E-95-34-40-B5-87-E8-C5
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-F8-CE
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fc67:939c:1b1e:3ff6%17(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 218628135
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-0F-1E-95-34-40-B5-87-E8-C5
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 8:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{98E9E995-60D0-47F1-83E4-C049EFFF5
B57}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 15:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{A58496DA-64F1-413A-A9FB-A21F2290A
865}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
3. The result of "uname –a" (UNIX) or "systeminfo" (Windows)
Host Name: BAS
OS Name: Microsoft® Windows Server® 2008 Standard
OS Version: 6.0.6002 Service Pack 2 Build 6002
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Server
OS Build Type: Multiprocessor Free
Registered Owner: Windows User
Registered Organization:
Product ID: 55041-291-7479071-76546
Original Install Date: 16/10/2012, 10:52:28
System Boot Time: 22/07/2014, 20:07:42
System Manufacturer: IBM
System Model: IBM System X3100 M4 -[2582AC1]-
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 42 Stepping 7 GenuineIn
el ~1600 Mhz
BIOS Version: IBM Corp. -[JQE150AUS-1.02]-, 27/06/2012
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: es-ar;Spanish (Argentina)
Input Locale: N/A
Time Zone: (GMT-03:00) Buenos Aires
Total Physical Memory: 4.083 MB
Available Physical Memory: 1.511 MB
Page File: Max Size: 8.404 MB
Page File: Available: 4.932 MB
Page File: In Use: 3.472 MB
Page File Location(s): C:\pagefile.sys
Domain: TRIMIX
Logon Server: \\BAS
Hotfix(s): 7 Hotfix(s) Installed.
[01]: {47740627-D81D-4A45-A215-03B075A18EC7}
[02]: {A8E86480-A9C1-4414-8AA2-B05A485C82F0}
[03]: {4AFF0FEB-1A23-48FE-9FBA-BEC37EECE0EE}
[04]: {511481D6-EE5F-4884-AF68-43E0183F8FB9}
[05]: {65AFCB03-3111-47E2-B1ED-198D6B0BC96E}
[06]: KB955430
[07]: KB968930
Network Card(s): 2 NIC(s) Installed.
[01]: Intel(R) 82574L Gigabit Network Connection
Connection Name: Local Area Connection
DHCP Enabled: No
IP address(es)
[01]: 192.168.30.29
[02]: fe80::d88e:80e:b3d4:a56a
[02]: VirtualBox Host-Only Ethernet Adapter
Connection Name: VirtualBox Host-Only Network
DHCP Enabled: No
IP address(es)
[01]: 192.168.56.1
[02]: fe80::fc67:939c:1b1e:3ff6
4. The build number of SoftEther VPN
v4.09.9451
5. Which SoftEther VPN component are you using?
SoftEther VPN Server
6. Whether or not there is a NAT or Firewall between your VPN server and the Internet.
(If there is a NAT or Firewall, you should open a TCP port for the VPN listener.)
Just a loadbalancing router doing NAT with 4 WANs from differents ISPs. SoftEther is listening on port 5555, which is forwarded by the router to the PC running the VPN Server (192.168.30.29).
7. Are you using SecureNAT?
No.
8. Your current vpn_server.config or vpn_bridge.config file should be attached on the post.
Already attached.
Thanks in advance.
1. Operating system name and the type of CPU-bits
SO: Windows Server 2008 Standard 64bits
CPU: Intel i3-2100
2. The result of "ifconfig –a" (UNIX) or "ipconfig /all" (Windows)
C:\Users\Administrator>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : BAS
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connectio
n
Physical Address. . . . . . . . . : 34-40-B5-87-E8-C5
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d88e:80e:b3d4:a56a%10(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.30.29(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.30.1
DHCPv6 IAID . . . . . . . . . . . : 238305461
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-0F-1E-95-34-40-B5-87-E8-C5
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-00-F8-CE
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fc67:939c:1b1e:3ff6%17(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.56.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 218628135
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-0F-1E-95-34-40-B5-87-E8-C5
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 8:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{98E9E995-60D0-47F1-83E4-C049EFFF5
B57}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 02-00-54-55-4E-01
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 15:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : isatap.{A58496DA-64F1-413A-A9FB-A21F2290A
865}
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
3. The result of "uname –a" (UNIX) or "systeminfo" (Windows)
Host Name: BAS
OS Name: Microsoft® Windows Server® 2008 Standard
OS Version: 6.0.6002 Service Pack 2 Build 6002
OS Manufacturer: Microsoft Corporation
OS Configuration: Standalone Server
OS Build Type: Multiprocessor Free
Registered Owner: Windows User
Registered Organization:
Product ID: 55041-291-7479071-76546
Original Install Date: 16/10/2012, 10:52:28
System Boot Time: 22/07/2014, 20:07:42
System Manufacturer: IBM
System Model: IBM System X3100 M4 -[2582AC1]-
System Type: x64-based PC
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 42 Stepping 7 GenuineIn
el ~1600 Mhz
BIOS Version: IBM Corp. -[JQE150AUS-1.02]-, 27/06/2012
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: es-ar;Spanish (Argentina)
Input Locale: N/A
Time Zone: (GMT-03:00) Buenos Aires
Total Physical Memory: 4.083 MB
Available Physical Memory: 1.511 MB
Page File: Max Size: 8.404 MB
Page File: Available: 4.932 MB
Page File: In Use: 3.472 MB
Page File Location(s): C:\pagefile.sys
Domain: TRIMIX
Logon Server: \\BAS
Hotfix(s): 7 Hotfix(s) Installed.
[01]: {47740627-D81D-4A45-A215-03B075A18EC7}
[02]: {A8E86480-A9C1-4414-8AA2-B05A485C82F0}
[03]: {4AFF0FEB-1A23-48FE-9FBA-BEC37EECE0EE}
[04]: {511481D6-EE5F-4884-AF68-43E0183F8FB9}
[05]: {65AFCB03-3111-47E2-B1ED-198D6B0BC96E}
[06]: KB955430
[07]: KB968930
Network Card(s): 2 NIC(s) Installed.
[01]: Intel(R) 82574L Gigabit Network Connection
Connection Name: Local Area Connection
DHCP Enabled: No
IP address(es)
[01]: 192.168.30.29
[02]: fe80::d88e:80e:b3d4:a56a
[02]: VirtualBox Host-Only Ethernet Adapter
Connection Name: VirtualBox Host-Only Network
DHCP Enabled: No
IP address(es)
[01]: 192.168.56.1
[02]: fe80::fc67:939c:1b1e:3ff6
4. The build number of SoftEther VPN
v4.09.9451
5. Which SoftEther VPN component are you using?
SoftEther VPN Server
6. Whether or not there is a NAT or Firewall between your VPN server and the Internet.
(If there is a NAT or Firewall, you should open a TCP port for the VPN listener.)
Just a loadbalancing router doing NAT with 4 WANs from differents ISPs. SoftEther is listening on port 5555, which is forwarded by the router to the PC running the VPN Server (192.168.30.29).
7. Are you using SecureNAT?
No.
8. Your current vpn_server.config or vpn_bridge.config file should be attached on the post.
Already attached.
Thanks in advance.
You do not have the required permissions to view the files attached to this post.
-
- Posts: 2458
- Joined: Mon Feb 24, 2014 11:03 am
Re: Unable to Remote Desktop (RDP) to VPN Host
Do you use hardware offloading on NIC?
Please try to turn off hardware offloading and reboot the machine.
Please check localbridge manual. http://www.softether.org/4-docs/1-manua ... in_Windows
Please try to turn off hardware offloading and reboot the machine.
Please check localbridge manual. http://www.softether.org/4-docs/1-manua ... in_Windows
-
- Posts: 1
- Joined: Tue Apr 02, 2019 9:44 pm
Re: Unable to Remote Desktop (RDP) to VPN Host
Hello
The problem for RDP and VNC and others application, that you cant use the same netword card for VPN server and remote desktop the same machine.
Best regards
The problem for RDP and VNC and others application, that you cant use the same netword card for VPN server and remote desktop the same machine.
Best regards
-
- Posts: 5
- Joined: Wed Apr 17, 2019 9:24 am
Re: Unable to Remote Desktop (RDP) to VPN Host
Also cant use the same netword card for VPN server and remote desktop at the same machine!