Windows NT cannot connect vista to vista.

  • Thread starter Thread starter breBill
  • Start date Start date
B

breBill

I'm not sure if this is the right place to ask, so please let me know.

We cannot connect from one vista machine to another vista machine using
remote desktop connection. When we try using a domain user account, we ge
the error "No authority could be contacted for authentication." I have
searched quite a bit in vain. It would be helpful if anyone can shine some
light on this problem.

These are windows vista enterprise and windows vista ultimate computers
added to our domain. We can connect to the machines using local accounts. I
tried adding the domain user to the administrators account, but that does not
help.

I'm not sure what the next troubleshooting step would be, so please suggest
your thoughts.

Thank you,
--------------------
Bill Cochran
 
Usually, this error means that you cannot access a DC (Domain Controller)
from your client machine.

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"breBill" <breBill@discussions.microsoft.com> wrote in message
news:FFA1BBB6-A7FF-4456-A024-F567A75A1A0B@microsoft.com...
> I'm not sure if this is the right place to ask, so please let me know.
>
> We cannot connect from one vista machine to another vista machine using
> remote desktop connection. When we try using a domain user account, we ge
> the error "No authority could be contacted for authentication." I have
> searched quite a bit in vain. It would be helpful if anyone can shine
> some
> light on this problem.
>
> These are windows vista enterprise and windows vista ultimate computers
> added to our domain. We can connect to the machines using local accounts.
> I
> tried adding the domain user to the administrators account, but that does
> not
> help.
>
> I'm not sure what the next troubleshooting step would be, so please
> suggest
> your thoughts.
>
> Thank you,
> --------------------
> Bill Cochran
 
I agree, but we can sign on to the domain on each of the vista machines. In
fact, we use these machines for developing software. I found that I can get
a remote desktop connection if i add 'enablecredsspsupport:i:0' to the .rdp
file. This makes the inital authentication prompt go away, the connection is
established and then I can sign in. In some cases we still get an error
saying something about Network Authentication being needed prior to making a
connection. It's odd this new error is hit or miss, but we haven't
researched it much. I'm looking into CredSSP for further information. If
you have any further thoughts, I'd be happy to hear them. Thank you for the
response.
--
--------------------
Bill Cochran


"Sergey Kuzin[MSFT]" wrote:

> Usually, this error means that you cannot access a DC (Domain Controller)
> from your client machine.
>
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "breBill" <breBill@discussions.microsoft.com> wrote in message
> news:FFA1BBB6-A7FF-4456-A024-F567A75A1A0B@microsoft.com...
> > I'm not sure if this is the right place to ask, so please let me know.
> >
> > We cannot connect from one vista machine to another vista machine using
> > remote desktop connection. When we try using a domain user account, we ge
> > the error "No authority could be contacted for authentication." I have
> > searched quite a bit in vain. It would be helpful if anyone can shine
> > some
> > light on this problem.
> >
> > These are windows vista enterprise and windows vista ultimate computers
> > added to our domain. We can connect to the machines using local accounts.
> > I
> > tried adding the domain user to the administrators account, but that does
> > not
> > help.
> >
> > I'm not sure what the next troubleshooting step would be, so please
> > suggest
> > your thoughts.
> >
> > Thank you,
> > --------------------
> > Bill Cochran
>
>
 
That's not the recommended way to solve the issue.

I think that you'll have to use the syntax "MyDomain\MyUserName"
when trying to connect. Leaving out the "MyDomain" part can cause
the rdp client to try to log you on with a local user account.

Check this page:
Vista Remote Desktop Connection Authentication FAQ
http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-
connection-authentication-faq.aspx

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?YnJlQmlsbA==?= <breBill@discussions.microsoft.com> wrote
on 31 jul 2007 in microsoft.public.windows.terminal_services:

> I agree, but we can sign on to the domain on each of the vista
> machines. In fact, we use these machines for developing
> software. I found that I can get a remote desktop connection if
> i add 'enablecredsspsupport:i:0' to the .rdp file. This makes
> the inital authentication prompt go away, the connection is
> established and then I can sign in. In some cases we still get
> an error saying something about Network Authentication being
> needed prior to making a connection. It's odd this new error is
> hit or miss, but we haven't researched it much. I'm looking
> into CredSSP for further information. If you have any further
> thoughts, I'd be happy to hear them. Thank you for the
> response.
 
i do use domain\user for the userid. i actually tried all the different ways
of specifying/not specifying the userid...no combination get's rid of the
error.

based on Mr. Kuzin's post before, how can the connection to the domain
controller from the remote desktop connection software be tested/verified?
--
--------------------
Bill Cochran


"Vera Noest [MVP]" wrote:

> That's not the recommended way to solve the issue.
>
> I think that you'll have to use the syntax "MyDomain\MyUserName"
> when trying to connect. Leaving out the "MyDomain" part can cause
> the rdp client to try to log you on with a local user account.
>
> Check this page:
> Vista Remote Desktop Connection Authentication FAQ
> http://blogs.msdn.com/ts/archive/2007/01/22/vista-remote-desktop-
> connection-authentication-faq.aspx
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> =?Utf-8?B?YnJlQmlsbA==?= <breBill@discussions.microsoft.com> wrote
> on 31 jul 2007 in microsoft.public.windows.terminal_services:
>
> > I agree, but we can sign on to the domain on each of the vista
> > machines. In fact, we use these machines for developing
> > software. I found that I can get a remote desktop connection if
> > i add 'enablecredsspsupport:i:0' to the .rdp file. This makes
> > the inital authentication prompt go away, the connection is
> > established and then I can sign in. In some cases we still get
> > an error saying something about Network Authentication being
> > needed prior to making a connection. It's odd this new error is
> > hit or miss, but we haven't researched it much. I'm looking
> > into CredSSP for further information. If you have any further
> > thoughts, I'd be happy to hear them. Thank you for the
> > response.
>
 
Enable auditing on both clients and check the EventLogs.
If there's a problem contacting a DC, you will see an error or
warning there.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?YnJlQmlsbA==?= <breBill@discussions.microsoft.com> wrote
on 01 aug 2007 in microsoft.public.windows.terminal_services:

> i do use domain\user for the userid. i actually tried all the
> different ways of specifying/not specifying the userid...no
> combination get's rid of the error.
>
> based on Mr. Kuzin's post before, how can the connection to the
> domain controller from the remote desktop connection software be
> tested/verified?
 
Back
Top