Authentication problems when not on local network

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

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" <(E-Mail Removed)> wrote in message
news(E-Mail Removed) lid...
>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

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

I would suggest that you have a look at hardware profiles. Or third party
apps like netswitcher. www.netswitcher.com

"Josh T" <(E-Mail Removed)> wrote in message
news(E-Mail Removed) lid...
> 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
>