T
Todd Hobdey
Brief rundown on the topology: Forest root domain and child domain at the
corporate office and a grandchild domain with a single controller at remote
location 1; DNS is hosted for the entire company from the corporate office;
each remote location is on a different IP subnet. The user in question
normally is at remote location 1, where his user and computer accounts are.
The other day he went to remote location 2 and plugged in his laptop,
changed his IP configuration to match that subnet, and logged on. Checking
the %logonserver% variable shows his home domain controller, so apparently
he isn't logged on with cached credentials, but when he tries to access
resources from remote location 1 he gets "Logon Failure: The target account
name is incorrect". In both locations he uses the corporate DNS servers and
when he's back at his home location everything works just fine. Remote
location 2 users don't have a domain controller and work in a workgroup
fashion; he can access them just fine of course.
I set up a test machine here at corporate in an attempt to replicate the
issue and I can access their resources just fine.
Any thoughts why this would work at one location but not another?
corporate office and a grandchild domain with a single controller at remote
location 1; DNS is hosted for the entire company from the corporate office;
each remote location is on a different IP subnet. The user in question
normally is at remote location 1, where his user and computer accounts are.
The other day he went to remote location 2 and plugged in his laptop,
changed his IP configuration to match that subnet, and logged on. Checking
the %logonserver% variable shows his home domain controller, so apparently
he isn't logged on with cached credentials, but when he tries to access
resources from remote location 1 he gets "Logon Failure: The target account
name is incorrect". In both locations he uses the corporate DNS servers and
when he's back at his home location everything works just fine. Remote
location 2 users don't have a domain controller and work in a workgroup
fashion; he can access them just fine of course.
I set up a test machine here at corporate in an attempt to replicate the
issue and I can access their resources just fine.
Any thoughts why this would work at one location but not another?