Authentication problems when not on local network
- From: Josh T <josht@xxxxxxxxxxxxxxxxx>
- Date: Wed, 20 Sep 2006 15:20:05 -0400
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:
- Re: Authentication problems when not on local network
- From: Bill Grant
- Re: Authentication problems when not on local network
- Prev by Date: Re: Computers no longer showing up in Network Neighberhood
- Next by Date: Re: Authentication problems when not on local network
- Previous by thread: Re: Computers no longer showing up in Network Neighberhood
- Next by thread: Re: Authentication problems when not on local network
- Index(es):
Relevant Pages
|
Loading
