No option to choose domain or "this computer" (no "log on to" field)when RDP (Remote Desktop) via Cisco VPN

  • Thread starter Thread starter Ruok
  • Start date Start date
R

Ruok

Guest
No option to choose domain or "this computer" (no "log on to" field)when RDP (Remote Desktop) via Cisco VPN

Hi,

I have a setup in which users sometimes VPN to a network, and then RDP
to a server. Several users log in ok to the terminal server, but for
two users Remote Desktop does not show the field with the domain
selection (Log on to), so they cannot be authenticated (VPN works ok -
they connect without any issues). And of course when they log in from
local LAN (not via VPN), everything is ok.

Using domain\username or usern...@domain.com does not help.
Adding various DNS suffixes to VPN connection properties does not
help.

This is a Cisco VPN, and RDP to Windows 2000 server, but I had this
situation before with MS VPN and RDP to Windows 2003 server (both
being
terminal servers).

Cisco VPN is configured by importing a setup file, so it's the same
for everyone.

I will try to experiment with various versions of Remote Desktop and
its settings again, but any help would be appreciated as I could not
find any other articles about it. Also, I do not have access to that
computer very often.

Cheers

Kamil
 
Re: No option to choose domain or "this computer" (no "log on to" field) when RDP (Remote Desktop) via Cisco VPN

Re: No option to choose domain or "this computer" (no "log on to" field) when RDP (Remote Desktop) via Cisco VPN

Weird, if it works for some it should work for all. You sure there hosts
file is setup correctly? Are you sure they are pointing to th ecorrect
server? Have you tried connecting through IP instead of DNS?

--
Jeff Pitsch
Microsoft MVP - Terminal Services

"Ruok" <KamilWawrzyszko@gmail.com> wrote in message
news:417c52cd-f917-4513-9bbe-600651acf10b@y38g2000hsy.googlegroups.com...
> Hi,
>
> I have a setup in which users sometimes VPN to a network, and then RDP
> to a server. Several users log in ok to the terminal server, but for
> two users Remote Desktop does not show the field with the domain
> selection (Log on to), so they cannot be authenticated (VPN works ok -
> they connect without any issues). And of course when they log in from
> local LAN (not via VPN), everything is ok.
>
> Using domain\username or usern...@domain.com does not help.
> Adding various DNS suffixes to VPN connection properties does not
> help.
>
> This is a Cisco VPN, and RDP to Windows 2000 server, but I had this
> situation before with MS VPN and RDP to Windows 2003 server (both
> being
> terminal servers).
>
> Cisco VPN is configured by importing a setup file, so it's the same
> for everyone.
>
> I will try to experiment with various versions of Remote Desktop and
> its settings again, but any help would be appreciated as I could not
> find any other articles about it. Also, I do not have access to that
> computer very often.
>
> Cheers
>
> Kamil
 
Re: No option to choose domain or "this computer" (no "log on to"field) when RDP (Remote Desktop) via Cisco VPN

Re: No option to choose domain or "this computer" (no "log on to"field) when RDP (Remote Desktop) via Cisco VPN

I have tried many things, including IP addresses. The problem is not
in connectivity, but in credentials not being accepted. I'll do some
testing today with other versions of Remote Desktop.

Kamil
 
Re: No option to choose domain or "this computer" (no "log on to"field) when RDP (Remote Desktop) via Cisco VPN

Re: No option to choose domain or "this computer" (no "log on to"field) when RDP (Remote Desktop) via Cisco VPN

We could not resolve it using any combination of username / domain, or
using differnet versions of Remote Desktop and settings within it, DNS
names or IP's. It actually maybe reated to mobile operator (Vodafone)
as it later turned out to be working with T-Mobile, but on the other
hand, I could establish VPN/RDP connections with Vodafone before on
other networks. Also, some of those things were tested by my customer,
so I could not verify that.

I don't think we have conclusions here.
 
Back
Top