Re: Active Directory call for contractors VPNing into our network
- From: "Chad Hooper" <chadh@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 28 May 2008 17:17:00 +0100
When the users VPN in, the credentials will only give them the ability to connect via the VPN, and not any access to your network. When they attempt to access a network resource, they will then be prompted for credentials again.
I believe the easiest cure would be to have them attempt to access one of your servers (preferably the one with the application on) after VPNing in, and when prompted for credentials, enter the user account details for your network in the format DOMAIN\Username. Tick the remember password box, and they should then have no issues accessing this server.
The proper method (if possible) would be to establish a trust relationship between the two ADs, but this may not be feasible in your environment.
Hope that helps.
Chad Hooper
MCSE (NT,2000,2003)
"Chad" <memyselfandirene@xxxxxxxxxxx> wrote in message news:kqednbHFQP14_KDVnZ2dnUVZ_uCdnZ2d@xxxxxxxxxxxxxx
We have a .NET program that works fine for everyone that logs onto Windows using a Windows domain account. However there are some contractors that are signing onto Windows using their company's account ID that are getting a "server not found" error when attempting to perform the call our company's AD .
Though they are signing onto Windows using the contracting company's account credentials, they are later use VPN software to get into our network. The user who is having the problem does in fact has adomain account with my company.
When the user accesses other company resources, he is presented with a Windows dialog box where he has to each time enter his company credentials.
Is there a way to identify what the credentials are for my company rather than his? Can he also talk to our AD? If not, I guess I can move the call to a web service as long as I can identify his company account first.
.
- References:
- Prev by Date: Re: Licenses
- Next by Date: Re: Device or User CAL needed?
- Previous by thread: Active Directory call for contractors VPNing into our network
- Next by thread: Re: Cannot Create Users (and many other issues)...
- Index(es):
Relevant Pages
|