RE: Vista Network Location Awareness and DUN
- From: Remy <Remy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 9 Oct 2008 04:43:00 -0700
Lots of messages without replies, seems like this isn't a particularly good
resource..
:(
"Remy" wrote:
I have a client who is about to deploy Vista to its business and one of its.
legacy desktop apps is a client dialler which uses DUN to connect to server
services. The application works but NLA kicks in upon connection. The users
of the application can only select the PUBLIC profile and what we would like
is to bypass this prompt in the first place since it can only lead to
confusion. I have had a look at the Firewall Policy and can't see anything
there which would allow us to say "whenever this DUN connection is made" or
"whenever a remote interface is connected" apply the public profile without
prompt.
Given that the profile being assigned is the most restrictive I was hoping
there would be a way to bypass the NLA prompt?
All thoughts gratefully received.
Remy
- Follow-Ups:
- Re: Vista Network Location Awareness and DUN
- From: Zaphod Beeblebrox
- Re: Vista Network Location Awareness and DUN
- References:
- Vista Network Location Awareness and DUN
- From: Remy
- Vista Network Location Awareness and DUN
- Prev by Date: Re: Remote registry request access denied
- Next by Date: Re: Vista Network Location Awareness and DUN
- Previous by thread: Vista Network Location Awareness and DUN
- Next by thread: Re: Vista Network Location Awareness and DUN
- Index(es):
Relevant Pages
|