Randy,
Connecting to your computer over your VPN connection sounds tricky.
You'd potentially have a different IP address with every new VPN session.
I do know that all VPN connections will appear to be on addresses from
subnet 10.228.x.x. When you are trying to connect to your home
computer, your destination will be a 10.228.x.x address.
I've learned that there is another list at UF dedicated to the VPN.
It's not very active, but the UF VPN masters do monitor it.
The list name is VPN-L and I believe you can subscribe using the
standard list commands (see http://lists.ufl.edu).
Dan Stoner
Network Administrator
Florida Museum of Natural History
University of Florida
(352)392-1721 ext. 233
Randy Switt wrote:
> Ok, I have been attempting to setup a remote desktop session between my
> campus office computer (as client) and my home office computer (as server)
> so that I can retrieve information from time to time that I forget. I've
> successfully forwarded tcp port 3389 on my home router and I've actually
> managed to setup a working session while the Cisco campus VPN connection is
> OFF.
>
> However, I typically leave the VPN session (with the /campus option) running
> on my home computer. When a VPN session is active I can't seem to setup an
> RDP session. I tried setting up a session using my home computer's VPN IP
> number rather than my router's public address and that didn't work (my
> packets wouldn't go off campus, they would bounce between 128.227.252.101
> and 128.227.166.113 until the TTL ran out). Anybody know exactly what the
> VPN session is doing to block the RDP session? Is it blocking the port or
> does it more to do with where the packets are going? If the VPN with the
> /campus option is active, does that mean that all packets originating from
> campus but not going through the VPN are discarded/blocked? Is there any
> way to establish an RDP session while the Campus VPN is active?
>
>
> --
> Randy Switt
> Network and Systems Administrator
> Environmental Engineering Sciences
> University of Florida
> [log in to unmask]
>
|