Re: Authentication problems when not on local network
- From: "Bill Grant" <not.available@online>
- Date: Thu, 21 Sep 2006 09:06:54 +1000
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.
"Josh T" <josht@xxxxxxxxxxxxxxxxx> wrote in message
news:pan.2006.09.20.19.20.04.837040@xxxxxxxxxxxxxxxxxxxx
I have a laptop running Windows XP SP2 joined to a Windows 2000 Server AD
Domain. The AD Domain is local to my site and uses "mydomain.local" for
DNS. My site has its own subnet (ex: 192.168.1.0/24). We have a Windows
2000 member server sharing files the laptop's user uses.
What I want to do is be able to connect the laptop to other subnets at my
company (other sites and VPN) and be able to access my file server.
There is no company wide AD or Windows domain - other sites may or may not
have their own local stuff. When connected at other sites the
laptop gets company DNS servers and "company.com" DNS via DHCP.
When I try to connect to the file server via IP address (as the local name
isn't resolvable without the local DNS) it works but I've prompted for a
username and password. It will not accept the laptop user's username and
password - I get the following popup:
"Logon unsuccessful: The User name you typed is the same as the user name
you logged in with. That user name has already been tried. A domain
controller cannot be found to verify that user name."
It does work if a try I different username - but the user needs to be able
to access his files with his own username.
Does anyone know how to make this work?
Thanks for any help,
Josh
.
- Follow-Ups:
- References:
- Authentication problems when not on local network
- From: Josh T
- Authentication problems when not on local network
- Prev by Date: Authentication problems when not on local network
- Next by Date: Re: Computers no longer showing up in Network Neighberhood
- Previous by thread: Authentication problems when not on local network
- Next by thread: Re: Authentication problems when not on local network
- Index(es):
Relevant Pages
|