02-01-2007 09:48 AM - edited 02-21-2020 02:50 PM
I've been trying for a couple of weeks to establish remote desktop over a vpn with no success. I am able to establish a connection to the vpn but once connected, I am unable to connect by remote desktop.
Building configuration...
Building configuration...
: Saved
:
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
clock timezone EST -5
clock summer-time EDT recurring
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol pptp 1723
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list 101 permit ip 10.1.1.0 255.255.255.0 10.1.2.0 255.255.255.0
pager lines 24
logging on
mtu outside 1500
mtu inside 1500
ip address outside x.x.x.x 255.255.255.0
ip address inside 10.1.1.1 255.255.255.0
ip verify reverse-path interface outside
ip verify reverse-path interface inside
ip audit info action alarm
ip audit attack action alarm drop
ip local pool ippool 10.1.1.3-10.1.1.254
pdm location 10.1.1.32 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 x.x.x.x 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 10.1.1.32 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
tftp-server inside 10.1.1.32 c:\cisco
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set myset esp-des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap interface outside
isakmp enable outside
isakmp identity address
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup vpn address-pool ippool
vpngroup vpn dns-server 10.1.1.2
vpngroup vpn wins-server 10.1.1.2
vpngroup vpn split-tunnel 1021
vpngroup vpn idle-time 1800
vpngroup vpn password ****
vpngroup vpn idle-time 1800
telnet 10.1.1.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
management-access inside
console timeout 0
dhcpd auto_config outside
terminal width 80
Solved! Go to Solution.
02-02-2007 09:03 AM
Here is what I have.Do I want to change the ip of the machine I am trying to establish rdp to 192.168.2.x 255.255.255.0?
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
clock timezone EST -5
clock summer-time EDT recurring
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol pptp 1723
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list 101 permit ip 10.1.1.0 255.255.255.0 192.168.2.0 255.255.255.0
pager lines 24
logging on
mtu outside 1500
mtu inside 1500
ip address outside x.x.x.x 255.255.255.0
ip address inside 10.1.1.1 255.255.255.0
ip verify reverse-path interface outside
ip verify reverse-path interface inside
ip audit info action alarm
ip audit attack action alarm drop
ip local pool 10.1.2.32-10.1.2.62 255.255.255.0
ip local pool ippool 10.1.2.32-10.1.2.60
ip local pool vpnpool 192.168.2.125-192.168.2.150
pdm location 1.2.3.5 255.255.255.255 inside
pdm location 10.1.1.32 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list 101
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 x.x.x.x 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
http server enable
http 192.168.1.0 255.255.255.0 inside
http 192.168.2.0 255.255.255.0 inside
http 10.1.1.32 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
tftp-server inside 10.1.1.32 c:\cisco
floodguard enable
sysopt connection permit-ipsec
crypto ipsec transform-set myset esp-des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set myset
crypto map mymap 10 ipsec-isakmp dynamic dynmap
crypto map mymap interface outside
isakmp enable outside
isakmp identity address
isakmp nat-traversal 20
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption des
isakmp policy 10 hash md5
isakmp policy 10 group 2
isakmp policy 10 lifetime 86400
vpngroup vpn3000 address-pool vpnpool
vpngroup vpn3000 dns-server 10.1.1.2
vpngroup vpn3000 wins-server 10.1.1.2
vpngroup vpn3000 split-tunnel 101
vpngroup vpn3000 idle-time 1800
vpngroup vpn3000 password XXXXXXX
vpngroup vpn3000 idle-time 1800
telnet 10.1.1.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
management-access inside
console timeout 0
dhcpd auto_config outside
terminal width 80
02-02-2007 09:21 AM
You are trying to rdp from vpn client to inside client correct?
Your vpn client will get 192.168.2.x address. Client on inside you are rdp to will still be 10.x.x.x.
02-02-2007 10:29 AM
When I established the connection I received 192.168.2.125 as my ip. Once connected, I tried to establish a remote connection to 10.1.1.2 with no luck.
The ip I'm trying to connect to is 10.1.1.2 subnet of 255.255.255.0, gateway of 10.1.1.1, public dns servers
I also noticed that I am receiving no default gateway with the vpn connection. Could this be the problem?
I am able to connect to \\10.1.1.2 and access files.
02-02-2007 10:35 AM
Not getting a default gateway on vpn is normal.
02-02-2007 10:42 AM
Any idea why I can access \\10.1.1.2 but not establish rdp to the same address?
02-02-2007 10:45 AM
So the vpn works?
Windows firewall maybe? Can you rdp to 10.1.1.2 from the inside?
02-02-2007 11:01 AM
It is working. Thanks for all of your assistance. I've checked on both the client and the server and both are set to allow rdp
02-02-2007 11:51 AM
The vpn and access to \\10.1.1.2 are working. RDP to 10.1.1.2 still isn't.
02-02-2007 12:15 PM
Can you rdp when you are on the inside, not on the vpn?
02-05-2007 07:29 AM
Nope.
02-05-2007 07:39 AM
So the rdp connection not working has nothing to do with the vpn.
Make sure rdp is enabled on server and that no firwall between you and server is blocking tcp 3389.
02-05-2007 07:47 AM
I tried with the firewall set to allow rdp and then with no firewall with no luck. Are there any settings on the PIX I would need to enable?
02-05-2007 07:53 AM
If you are on inside coming from 10.1.1.x and attempting to hit 10.1.1.2, the traffic would not be hitting the firwall.
02-08-2007 04:52 PM
Okay - When I am at work I can launch the vpn client, receive a 192.168.2.x address, and connect to \\10.1.1.2
When I am at home, I can launch the vpn, receive a 192.168.2.x address and I am unable to connect to \\10.1.1.2 I even changed all of my internal router settings at home to match those at work. (both hand out 192.168.1.x addresses) I am completely stumped. If I couldn't connect to the vpn at home I would think there was a setting which needed to be changed. But, everything is the same.
02-08-2007 05:09 PM
What kind of device are you going through at home?
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: