Rem. Dsktp. with Cisco VPN

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Hi,

We're having problems connecting a PC to a PC in another
domain via Cisco PIXs. We've determined that the PIX
configurations are good as we can connect to another
computer on that same remote domain but not the particular
one this user needs to. I went out to the remote site
today and the only thing I can see that might be a problem
is the lack of users in the list of authorized users for
Remote Desktop. We could log on occationally some time
back but have done so only a couple of times in the past
three months. When I tried to add the person's name on
our domain to the list of users on the remote PC in the
other domain it, of course, said I couldn't do that.

I saw a previous post from today mention the fact they
couldn't connect after upgrading to XP Pro SP2. I'm sure
the remote PC is SP2. The local PC on our end is running
Windows 2000 SP4 with Terminal Services added by the
person that originally set us up but, who has since moved
on to bigger and better things.

If anyone has any ideas about this please let us know.

Thank you.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Well, for anyone else's edification that may be
interested, we found the problem. It was in the PIX at
the remote site. Apparenly, from the Cisco guru that set
this all up, Cisco boxes have a tendency to
occationally "loose their minds" and once the settings on
the remote box were refreshed we've been able to access
the workstation from our end just fine. All settings had
appeared to be correct in both workstations and PIX boxes
but, for some reason, there was a hang up that blocked our
workstation's access to the other's desktop even though we
could connect to the remote location's W2K3 server.

Three months, one minor glitch, too much gasoline to
travel to the other site, thanks Cisco.

Dana

>-----Original Message-----
>Hi,
>
>We're having problems connecting a PC to a PC in another
>domain via Cisco PIXs. We've determined that the PIX
>configurations are good as we can connect to another
>computer on that same remote domain but not the
particular
>one this user needs to. I went out to the remote site
>today and the only thing I can see that might be a
problem
>is the lack of users in the list of authorized users for
>Remote Desktop. We could log on occationally some time
>back but have done so only a couple of times in the past
>three months. When I tried to add the person's name on
>our domain to the list of users on the remote PC in the
>other domain it, of course, said I couldn't do that.
>
>I saw a previous post from today mention the fact they
>couldn't connect after upgrading to XP Pro SP2. I'm sure
>the remote PC is SP2. The local PC on our end is running
>Windows 2000 SP4 with Terminal Services added by the
>person that originally set us up but, who has since moved
>on to bigger and better things.
>
>If anyone has any ideas about this please let us know.
>
>Thank you.
>.
>