Re: Authentication problems when not on local network
- From: "Bill Grant" <not.available@online>
- Date: Fri, 22 Sep 2006 16:36:55 +1000
I would suggest that you have a look at hardware profiles. Or third party
apps like netswitcher. www.netswitcher.com
"Josh T" <josht@xxxxxxxxxxxxxxxxx> wrote in message
news:pan.2006.09.21.11.03.17.659334@xxxxxxxxxxxxxxxxxxxx
On Thu, 21 Sep 2006 09:06:54 +1000, Bill Grant wrote:
You cannot be logged into more than one domain. If you are logged
into
mydomain.local, you can only access resources in another domain if a
trust
relation exists between the domains. If company.com trusted
mydomain.local,
it would accept your credentials and allow access.
The thing is, there is no other domain - company.com is purely a DNS
domain, not a Windows domain. The laptop is logged in with a cached
mydomain.local Windows account, just like it would be if not connected to
any network.
Thanks,
Josh
.
- References:
- Authentication problems when not on local network
- From: Josh T
- Re: Authentication problems when not on local network
- From: Bill Grant
- Re: Authentication problems when not on local network
- From: Josh T
- Authentication problems when not on local network
- Prev by Date: Re: DHCP
- Next by Date: Re: Unable to add a Client Computer to Windows Small Business Serv
- Previous by thread: Re: Authentication problems when not on local network
- Next by thread: DHCP Classless Static Routes
- Index(es):
Relevant Pages
|